Start for free
Within your TAGGRS container, locate the container ID and copy it.
Visit the GTM template gallery to find the TAGGRS tags you need. Choose the access method you prefer:
If you choose the live version, follow the instructions sent to you via email. If you prefer to use the JSON file, instead, follow the steps outlined below.
Now that the tag file has been downloaded, you can start uploading the tag on Google Tag Manager. Go to your web container. Within your workspace, click to 'Templates' and click 'New' under tag templates.
Then click on the 3 dots at the top right and click Import.
Make sure the downloaded zip file is extracted, you do this by opening the file.
Once this is done you can upload the file to Google Tag Manager. As shown in the example below you only need to upload 'template.tpl'. Then click 'Save' and the TAGGRS tracking tag - client side is uploaded and ready to use!
Before setting up TAGGRS Tracking Tags, we need to create a trigger. This trigger will ensure that all events are taken and forwarded to TAGGRS, giving you the most insight into the actual data difference. We differentiate between several events including:
Go to the client container in Google Tag Manager. Within your workspace, go to Triggers, then click New.
Give the trigger a name such as GA4 - All events and choose Custom event as the trigger type under Trigger configuration.
Under event name, enter .*. Then check ' Use matching regular expression'.Under 'This trigger is triggered for', select 'All custom events' . Then save the trigger.
Now that we have created the trigger, we are going to create and set up the TAGGRS Tracking Tag. Go to the web container in Google Tag Manager. Within your workspace, go to 'Tags' and then click 'New'.
Click on 'Tag configuration'. Then under 'Custom', click the client-side tracking tag of TAGGRS.
Under 'Container Identifier', enter the Container ID you copied from your container in the TAGGRS dashboard. Then click on the 'plus' at 'Event name' and select 'Event'.
We want to measure the data on all pages and events to properly show the difference in data. As a trigger, choose the GA4 All events trigger you just created. Then give the tag a name and click Save.
All events in the data layer are now integrated. If you want to track additional events, such as form submissions, you need to create a specific tracking tag for this. Then choose the desired event as the trigger for this tag.
The events are now passed client side to TAGGRS. To measure the difference in data we need to start doing the same for the server side. This works the same way as the client side tag.
Go to the server container in Google Tag Manager. Within your workspace, go to "Tags," then click "New.
Like the client side tracking tag, the server side tracking tag must be downloaded from GitHub and uploaded to Google Tag Manager. To do this, follow the same steps as the client side tracking tag, but now download the server side tracking tag.
Once it is uploaded on Google Tag Manager, we can start installing the tag. Click on 'Tag configuration.' Then under 'Custom', click on TAGGRS ' server-side tracking tag.
As with the client side tracking tag, enter the container ID under 'Container Identifier'. Then select 'Event Name' under 'Event name'.
Next, we're going to set the trigger. Not using consent mode? Choose "GA4 Client" as the trigger.
Do you use consent mode? Then add the trigger GA4 Client + Analytics storage. This way you will comply with the consent rules and avoid large data differences within the TAGGRS dashboard.
Then give the tag a name and click 'Save'. Don't see 'GA4 Client' listed? Check out this blog to create a GA4 tag with associated trigger in the server container. Once set up, the trigger will appear.
Successful? Nice going! Now go to your container within TAGGRS. The effects of Server Side Tagging are now measured per event, top!
We use the info for statistics for our TAGGRS Server Side Analytics. So for Consent Mode V2 you can use statistics as Consent State for our tracking tags.
There may be a delay of up to 48 hours before changes are fully processed and displayed correctly on the dashboard.
