Monitus Audit Custom Reports

Not sure if your Google Analytics is set up correctly? Here is an easy way to check:

Click on this link to install a custom report into your Google Analytics.

Once you have applied it in your account you should see the following tabs at the top of the report:

In general terms you will want to see data in each tab. More specifically:

  • Sources. Are you seeing transactions next to your campaigns? If not, check that e-commerce tracking is enabled in Google Analytics and that the monitus code has been properly installed. Next, look for your own domain. You should not see it, but self-referrals from your own domain indicate an implementation issue. Remember that with our service, our code has to be on every page, including mobile subdomains.
  • Site Search. If you see terms, that’s great. If not, it could be that the tracking code is missing from the site search results page and/or that Google Analytics has not been configured to track site search terms.
  • Event tracking. This is a really cool feature. As part of Monitus tracking, we can automatically send events for Checkout Errors and Checkout Messages. If you don’t see these, please enable them in your Monitus account in Your Account > Tools Settings > Analyze.
  • Goals. Goals have to be set up manually in Google Analytics. I recommend setting up a goal for a Sale and a separate goal for “add to cart”. If you don’t see any goals we’d be happy to add them.
  • Mobile. I just threw that in because mobile is hot, right? Seriously though, what’s the proportion of mobile traffic your site gets? If it’s significant amount you have to pay attention. If you don’t have a separate mobile site and the conversion rates are much different, start thinking about how you can improve things. If you are using a 3rd party tool or subdomain for mobile traffic you’ll want to make sure that you see some traffic data and conversions. If you see self-referrals check that the mobile subdomain is properly tagged with our code, not the standard Google Analytics code.

We are happy to help if you feel your setup could be better, but please note that some things may require paid consulting time.

New Cart Recovery Email platform

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

 

Monitus Data Quality Degraded

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

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