Author Archives: MacPrawn

New Cart Recovery Email platform

Posted on

To access your email platform please login in to your Monitus account. In the Your Tools > Cart Recovery menu click on the Email platform link.

email-platform

This will bring you to the email platform. Click on Campaigns to find the Cart Recovery campaign. It is in Draft mode when we first create it for you. Click on Edit to review all the settings and, if desired, make any edits.

We recommend that you send yourself a test message before enabling or re-enabling the campaign after you made any edits:

Very Important: When you edit the trigger, it goes into Draft mode and emails will not be sent. You must active the trigger by clicking on the Activate or Reactivate button in the top right corner:

reactivate

 

When your trigger is active, you’ll find it in the Campaigns > Triggered tab:

campaigns_ct_active

 

Upgrade to v4.0

Posted on

To upgrade a store’s installation to the new v4 one liner:

  • Install the new code: Remove all traces of the old installation code: the static header file, and the monitus_init snippet. Replace with the new instructions, in the merchant’s .monitus.net account.
  • Clean up: Remove any usage of the old "pqTracker" variable, and make sure the merchant’s .monitus.net account is upgraded to use only one GA tracker.
  • Adjust custom code:
    • Use the new callback method instead of the legacy "monitus_ga_callback", or the even older still "monitus_ga_init", "monitus_customize_ga_tracker", and "monitus_final_callback"
    • Transform all MUI function calls into jMUI equivalent function calls. NOTE: consult the jMUI documentation for the updates parameter list and format! jMUI is jQuery-based, which changes the way you pass object or selectors to functions. If for some reason you must keep using the old MUI library, please make sure to load it before the new monitus one-liner; our code will then automatically load a translation library that transforms MUI calls to jMUI equivalents. Note however that this is not as efficient (extra file to load, extra code to run) so moving to the new jMUI call should be the end goal here.

Monitus Data Quality Degraded

Posted on

In an effort to provide greater compatibility with 3rd party scripts, the new code introduced a bug that resulted in degraded data quality. We noticed the error on 03/06/2013 and fixed it immediately. The issue was hard to spot because of the delays incurred by all the different caching mechanisms in place to make the .monitus.net code load quickly on your store.
—
Please accept our sincere apologies
Jean and Michael.

Monitus Data issue

Posted on

In an effort to prepare for higher traffic volumes during the holiday season we added another load balancer to our setup on 11/12/2012. Unfortunately that new load balancer required a different configuration than we were used to from our hosting provider. As a result, the new load balancer was not working properly and resulted in some pageviews and transactions not being logged either in Monitus or Google Analytics. We noticed the error the following day 11/13/2012 and were able to fix the issue. The issue was hard to spot because there was no obvious error on the front-end and visitors to sites running our code would not have seen an error or slowness in the browser.

—

Please accept our sincere apologies

Michael