Google Analytics dynamic remarketing lists and demographic data

Interested in managing dynamic remarking lists or get demographic data in Google Analytics?

In order to get this to work the dc.js library instead of ga.js has to be loaded on your site. Fortunately, it’s an easy change. Please edit your current monitus tag as follows.

This is what your current tag should look like this:

<script type=”text/javascript”>var monitus=monitus||{};; </script><script type=”text/javascript” src=””></script>

Note that is just an example, you will have a specific id that should not be changed. You just have to add one line as shown in bold in this code:

<script type=”text/javascript”>var monitus=monitus||{};; monitus.ga_url = ‘//’;</script><script type=”text/javascript” src=””></script>

Just publish the store editor and you’ll be done.

Then follow the Google Analytics instructions to enable demographic reports. In the last step, hit Skip Validation.

Magic Cart

We are pleased to announce our newest cart recovery feature, called Magic Cart.

It’s a known fact that we live in a multi-device world where customers start shopping on one device and continue on another. According to a recent study by Google as many as 67% of shoppers start on one device and continue to another. Furthermore, smartphones are the most common starting point for sequential activities and in particular shopping.

Yet, when it comes to buying online, many people still prefer placing orders on their desktop or tablet. One of the main reasons for that is the difficulty entering shipping and payment info on a small screen. Some people are also not as comfortable entering credit card information on a mobile device. This is reflected in conversion rates that are typically much lower for mobile devices than for desktops.

How can we help customers pick up on a new device where they left on one device? If a customer places an item into the cart on a smartphone, how can she continue the checkout process on her desktop without having to find the items and add them to the cart again?

That’s the problem the Magic Cart solves. At its core, the magic cart allows customers to send their cart by email. On the cart page there is a customizable button that prompts customers for an email address. The email that is then sent contains a link to the cart page.

But that’s not all. At Monitus we know a thing or two about tracking, so here’s the really cool feature. The carts are in fact synced across devices. So if you update any items in the cart on one device it will automatically be reflected on the other device. Magic!

Your customers will love the magic cart because it makes it easier for them to buy from you using multiple devices. You, the retailer, will love it because it’s easy to implement and helps drive conversions. It’s a win win for everyone.

magic cart conversions

I invite you to take a look at a two-minute video:

If you have a significant amount of mobile traffic you should consider the magic cart approach.

There is a $149 implementation charge for active Monitus Tools customers using our paid cart recovery service. This charge covers the provisioning of the email platform and implementing the button on your checkout to match your css. The Magic Cart can only implemented on a Yahoo! Store checkout page. If you use a 3rd party mobile solution that uses a different checkout, the Magic Cart cannot be implemented. In general, we recommend to all our clients that they use a responsive version of the Yahoo! Store checkout.

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.

Javascript Monitus Object Settings

Here are the different settings you can use to customize the monitus code on a store’s pages:

  • int – required The store ID assigned by Monitus
  • monitus.health_check bool This stores participates in our daily stats for speed and health graphs. Mainly beta stores for now.
  • monitus.allow_frames bool Allow our code to run if it is called form within an iframe?
  • monitus.tools_off string Comma-delimited list of tool IDs to turn off (bypass)
  • monitus.callback function The callback used by our code at different point in its execution. See the documentation here
  • monitus.ga_mode number Load Classic GA and/or Universal Analytics? 0-none; 1-GA only; 2-UA only; 3-GA and UA
  • monitus.ga_url string – url The url to use for the GA javascript library.
  • monitus.ga_page string The page name to send to GA.