Unless you are very comfortable with how our integration works and fully understand the implications of using both our turnkey integration and GTM, we recommend using one or the other. If you use both and don't have things setup a specific way, you run the risk of double counting.

This is what the integration settings look like on our side:

  1. If you opt in to using our native GA integration, we will input your GA ID into the red highlighted field, and you would automatically begin getting data from us. If this field remains empty, you will not receive data from us. 
  2. If you opt in to using GTM, then we would input your GTM Container ID into the orange highlighted field. When we add a GTM Container, all we are doing is giving it permission to load on the Express Store, thus giving you the flexibility to add whatever you'd like on your side. We do not manage or control your GTM Containers, and until you import the Roadster preconfigured tagging found here, GTM will not send data into GA.

This is an example of what it looks like if you are configured using both:

In this example, we are sending data directly into UA-112623011-2. We are also loading the GTM-KC5QFSD container on the Express Store.

There is nothing preventing you from using both integration methods at the same time, but if you do, you must make sure that the GA ID you set in GTM does not match the GA ID we are sending data into

If the Tracking IDs are the same in GTM and what we have set on our side, you are going to be receiving data from us, as well as yourself. This means that every single event that fires on the site will be collected twice in Google Analytics, which is going to artificially inflate the values you see, and will also impact key metrics.