TrafficStars tag

The TrafficStars tag by Stape allows you to track conversions and manage Click IDs from your server Google Tag Manager (sGTM) container using TrafficStars' server-to-server (S2S) postbacks. With this tag, you can store TrafficStars Click IDs during page views and send conversion postbacks to help maintain accurate attribution without relying solely on browser-based tracking.

• The tag automatically extracts Click IDs from landing page URLs and stores them in a first-party cookie for later use in conversion tracking.
• It supports conversion tracking with Goal IDs and API keys, as well as additional parameters such as conversion value, price, lead code, and duplicate conversions.
• An optional cookie syncing feature can use browser-side pixels to synchronize TrafficStars cookies when no valid Click ID is available, while the optimistic response mode can reduce tag execution latency.

Please ensure that you already have Google Tag Manager web and server containers, as well as a configured server container and custom domain in Stape. Please follow these guides if you don’t have any of those:

• How to create a server container in Google Tag Manager 
• How to create a server container in Stape 
• How to add a custom domain in Stape 

1. Configure sending data to the server GTM container. The most popular options for sending data to sGTM are Google Analytics 4 and Data Tag/Data Client. For more information, read the Send data to server container article.

2. Add the TrafficStars tag template in the server GTM container by importing it from the Template gallery:

• Search for the TrafficStars tag by Stape in the Google Tag Manager Tag Template gallery.
• Click Add to workspace.

3. Create the TrafficStars tag:

• Go to the Tags menu → click New.

• Click Tag Configuration → select TrafficStars.

4. Configure the TrafficStars tag: 

• Event Type - select whether you wish the tag to pass Page View or Conversion events.

• Tag Execution Consent Settings - choose if you wish for the tag to wait for marketing consent from the user before firing.
• Advanced Settings (Additional Tag Metadata) - specify additional tag metadata to be included in the event data when the tag is fired.

5. Add the Trigger for the tag, give it a descriptive name, and click Save.

You can test the configurations in Google Tag Manager. Click on Preview, trigger the event on your website with actions like viewing a page or completing a transaction, and check whether the tag has fired.

Find out more about debugging and monitoring server-side tracking configuration in our guide.