GTM Not Loading on Certain Pages

  • For security reasons, your GTM container will not be permitted on any page where a user enters any sort of PII (ie. credit card information or social security number). We trust you - but it’s extremely easy to grant GTM access to 3rd parties, who would then have access to those pages and the ability to collect confidential information. These pages are
    • /trade-in/contact
    • /checkout/customer
    • /pre-approve/contact
  • If you only use GTM, we have a solution to remedy. Please provide us with the GA4 Measurement ID you are using in GTM that we can plug in on our side, so that we can start sending you hits happening on these pages. More information here

Digital Retailing Events not appearing in GTM

  • If you use GTM, you must import the Digital Retailing GTM container (found here). If you do not import this container, you won’t be able to see any Digital Retailing events or pageviews. The easiest way to see if the container is running is to look in GA for events or pages that start with ‘R-’. If you don’t see anything matching this, then you will need to upload the container. 
  • Make sure to upload and publish both the Digital Retailing Pageview and Event tags to get a complete view as to what is happening on the Express Store. We have run into multiple situations where dealers only published the pageview tag, and not the event one, so they had no idea what their customers were clicking on or how they were interacting within the Express Store. 

Digital Retailing Pages Double-firing in GTM

  • If you’re using GTM, you should only have Digital Retailing configured to use your GTM container(s), not your GA4 Measurement ID.
  • Here’s how it works: You tell the Digital Retailing platform to load your GTM container(s) on the Express Store (that’s all we need to know). You then go into your GTM and configure it to send all events and pageviews into your Google Analytics account. You don’t want to tell Digital Retailing to fire into both, this will otherwise result in double counting.

If you merge the Digital Retailing container with your own existing GTM container, you must evaluate any tags that fire on ‘all pages’ and make them more specific so they only fire on your Dealer Website. If this critical step isn’t taken, you will cause the Express Store pages to double-fire. 

These are the most common implementation problems we see, how to diagnose them, and what needs to be done to fix them:

Issue: Dealer's GA is not receiving pageviews or events.

  • Diagnosis: All Digital Retailing Pageviews start with /R- and all Roadster event category and actions begin with R-
  • Problem: The UA code was entered into the Digital Retailing configuration incorrectly OR entered incorrectly in the dealers GTM container.
  • Fix: Identify the dealer with the outage and input the correct UA code. 

Issue: Dealer's GA is only receiving Digital Retailing pageviews but not events.

  • Diagnosis: All Digital Retailing Pageviews and Events start with 'R-' a
  • Problem: The Dealer is using GTM and only uploaded part the Digital Retailing standard container
  • Fix: Follow the steps GTM Integration instructions found here.

Issue: Dealer's GA is seeing double-counting on pageview

  • Problem: Dealer is using both GTM and our native GA integration > GTM points to the same GA ID also entered into the Digital Retailing configuration, causing double-counting.
  • Fix: Ask your Digital Retailing representative to remove the UA code from Digital Retailing Admin but keep the GTM container installed.