We've been getting a lot of questions about the upcoming analytics changes happening on February 1, so we wanted to clarify what is changing, and what updates you'll need to make on your side. Reminder: These changes ONLY apply to those currently using GTM, and will NOT affect anything you're doing on the main site - this only pertains to the Express Store. If you are not using GTM, you will not be affected, nor will you have to make any changes on your side.

Update: 

In an effort to continue making these changes as simple and seamless as possible, we have updated all GTM triggers to be compatible with the current event names as well as the new event names going live on February 1st. If you'd like, you can import the latest JSON file into GTM and publish these updates without any impact to tracking. Tags will continue to fire as is, and when the event name switch happens on the 1st, they will continue to fire due to triggers supporting both names. Most recent JSON file can be found here.

Existing Setup: 

On the Express Store, we fire three individual events which ultimately populate Google Analytics with data, the events are as followed:

  1. R-pageview (not changing)
  2. businessEvent
  3. virtualPageview

These events are the firing triggers for the Roadster tags in GTM (from the JSON file that you must import into your container if you want to use GTM).

How does this work?

  1. When 'R-pageview' or 'virtual-pageview' fires on the site, it is going to fire the 'Roadster GA Pageview' tag, because those are the firing triggers.

  1. When 'businessEvent' fires on the site, it is going to fire the 'Roadster GA Event' tag, because that is the firing trigger.

New Setup / What You Need to Change:

We are not changing anything in your GTM container, nor will these changes affect anything you are doing on the main site - this is strictly for the Express Store. We are simply updating the event names that we fire on the Express Store, as highlighted above.

On February 1st, at a minimum, you will need to update these two tag triggers.

  1. Roadster Dialog/Overlay
    • Update event name 'virtualPageview' to be 'R-pageview-virtual'
  2. Roadster Event
    • Update event name 'businessEvent' to be 'R-event'

You might have noticed all of the new 'non-interactive' tags that we have included in the latest JSON file as well - each of these tag triggers will need to be updated also because they are looking at 'businessEvent'. If you have any additional tags or pixels using triggers firing off of Roadster events, be sure to update those accordingly. 

What Happens If You Don't Make These Changes?

If you do not make these changes, Roadster tags will stop firing because they will still be configured to fire off of the old event names, which will no longer be on the site. 

  • Example. If you do not update the Roadster Event trigger, and we change the site side 'businessEvent' to 'R-event', that tag will not fire because the site is no longer firing an event called 'businessEvent'.