Data Enricher

Benefits

Prerequisites

• TAGGRS account
• Server-side GTM container set up and integrated with TAGGRS

Configuration

Activate the Data Enricher Tool

1. In your TAGGRS dashboard, select your Product.
2. Go to Features → Enrichment.
3. Enable the tool for your container or property.

Configure Data Enrichment fields

TAGGRS can automatically append the following data to each event:

• X-GEO-Country: Visitor’s country
• X-Device-Browser, X-Device-Browser-Version, and X-Device-Mobile: Browser name and version by device (desktop, mobile, or tablet)
• X-Device-Os, X-Device-Engine, and X-Device-Engine-Version: further details about the user's operating system and its engine
• X-Device-Bot: Detects bot taffic

Integrate with Analytics Platforms

1. Ensure your GTM server container is configured to forward enriched events to GA4 or other analytics endpoints.

2. Map the new enrichment fields to custom dimensions or parameters in your analytics platform.

Test and validate

Use GTM Preview mode and analytics platform diagnostics to verify enriched data is being received as expected.

Real-world application example

By checking the options in the Data Enricher Tool, companies can enrich their analytics. This means they better understand how different user groups interact with their site, leading to more informed decision-making and an improved user experience.

Set up Google Signals server-side

Setting up Google Signals via TAGGRS Enrichment Tool allows you to enhance your analytics capabilities, including cross-device reporting, audience creation, and remarketing features. Here is how configure Google Signals in a TAGGRS product.

Enable the Data Enricher Tool

‍1. Enable the Enrichment feature in your TAGGRS product. This step ensures your container collects the necessary geographic data for Google Signals to function.
2. Open your GTM Server-Side Container.
3. Go to the Variables → New Variable → Request Header as the type.
4. Set the header name to: x-GEO-Country. This variable captures the user's geographic region based on their request header.

Create a Request Header variable

1. Open your GTM Server-Side Container.
2. Go to the Variables → New Variable → Request Header as the type.
3. Set the header name to: x-GEO-Country. This variable captures the user's geographic region based on their request header.

Create a Visitor Region variable

1. Still in the Variables section, create another variable.
2. Name this variable Visitor Region.
3. Assign the value of the previously created x-GEO-Country variable.
This variable will map geographic data to Google Analytics for regional settings.

Configure the GA4 Client

1. Navigate to Clients in the GTM Server-Side Container menu.
2. Open the GA4 Client.
3. Enable the option Default gtag.js paths for specific IDs: input the GA4 Measurement ID of the Google Analytics property where Google Signals is enabled.
4. Check the box for Enable region-specific settings: assign the Visitor Region variable to this field.
This configuration links regional data to your Google Analytics property, enabling region-specific tracking.

Save and test

1. Click Save to apply all changes in your GTM container.
2. Activate Preview Mode to test the configuration.
3. Verify that Google Signals is correctly collecting geographic data in your Google Analytics reports. Testing ensures that the setup is working as expected before deploying it live.

Once your configuration is live, Google Signals will provide enhanced analytics insights, including cross-device behavior and audience data. This setup is server-side, ensuring better control over data privacy and regional compliance.