Tealium Learning Center

This article describes how to configure and use the Google Analytics 4 Measurement Protocol Connector. In this article: Overview The Google Analytics Measurement Protocol for Google Analytics 4 allows developers to make HTTP requests that send events directly to Google Analytics servers. This helps developers measure how users interact with their business from any HTTP-enabled environment, which makes it easy to measure interactions that happen server-to-server. Tealium EventStream acts as a conduit to enable Google Analytics 4 tracking. It ties together support for Mobile, Internet of Things, and Offline Event and pageview tracking by: Tracking both web and app applications. Tying online to offline behavior. Measuring interactions both client-side and server-side. Sending events that happen outside standard user interaction, such as offline conversations. Tealium supports the following actions with the Google Analytics 4 Measurement Protocol Connector: Send PageView Event Send Event Send Firebase Event For additional configuration details for the tag, visit the Google Analytics 4 (GA4) Tag Setup Guide. Considerations The Google Analytics Measurement Protocol for Google Analytics 4 connector is not a complete replacement for the client-side tag solution. Limitations If any session or user data is needed, the client-side tag is required. The user_id key requires both client-side and Measurement Protocol events to include the user_id . Session data is not supported by the current iteration of the GA4 Measurement Protocol API. The tag is required to get the automatic Google Analytics session data. When you have the tag enabled, the session_start event or first_start is also sent. Does not support  utm parameters. Does not contain geographic data and the user agent. Authentication The Measurement Protocol API uses a measurement ID and API secret that are included in the URL as query parameters. https://google-analytics.com/mp/collect?measurement_id=G-1234567890&api_secret=xxxxxxxxxx Configuration To configure the connector, enter the API Secret and either the Measurement ID or Firebase ID for the data stream. Response/Debugging The Measurement Protocol always returns a 2xx status code if the HTTP request was received. The Measurement Protocol does not return an error code if the payload data was malformed, or if the data in the payload was incorrect or was not processed by Google Analytics. Google supplies a separate endpoint for validating events: https://google-analytics.com/debug/mp/collect? The Tealium Measurement Protocol connector uses this endpoint during Trace, which displays the validation process of the event data. Recommendations and configuration details To mitigate issues around the noted limitations and fully cover all data requirements, implement the Google Analytics 4 tag in Tealium iQ. Set the tag to load on all pages, with Send Page View set to false . In addition, add the Google Analytics Cookie Matching Service tag so that the Google clientId is automatically added as a utag_main__ga cookie value. All required events outside of Google’s automatically-collected events can then be configured in the Google Analytics connector in Tealium EventStream. The Google Analytics 4 tag automatically triggers a purchase event when order_id is present through the E-commerce extension mappings. If you have the E-commerce extension enabled and wish to track purchases through EventStream, configure a Set Data Values extension scoped to Google Analytics 4 to clear the _corder attribute. Because Tealium can support a client-side implementation to better address web-client integrations, as well as supporting mobile and offline events through Tealium’s EventStream, Tealium can integrate with both solutions and create a combined approach. For more information for configuration of a client-side tag, read the Google Analytics 4 (GA4) Tag Setup Guide. Prerequisites Product Required Google Analytics 4 account ✓ Tealium EventStream / AudienceStream ✓ Tealium iQ Optional, but preferred Authentication Value Description Location API Secret (Required) An API Secret generated in the Google Analytics UI. To create a new secret, navigate to: Admin > Data Streams > choose your stream > Measurement Protocol > Additional Settings > Measurement Protocol API secrets. Measurement ID (Optional) The measurement ID associated with a stream. In the Google Analytics UI, navigate to: Admin > Data Streams > choose your stream > Measurement ID > Create. Firebase App ID (Optional) The identifier for a Firebase app. In the Firebase console, navigate to: Project Settings > General > Your Apps > App ID. API Version: Beta Body Parameters Parameter Description Client ID (Required) A unique identifier for a client. Measurement ID Override Measurement ID. For example, the identifier for a Data Stream. Firebase App ID Override (Required) The identifier for a Firebase app. This setting overrides Firebase App ID used in the configuration section. User ID A unique identifier for a user. If you include user_id in your Google Analytics 4 Measurement Protocol events, you must also include it in the client-side events. Timestamp Micros A Unix timestamp (in microseconds) for the time to associate with the event. Set this to record events that happened in the past. This value can be overridden through the user_property or event timestamps. Events can be backdated up to 3 calendar days based on the property's timezone. Non Personalized Ads Set this to true to indicate these events are not used for personalized ads. Event Parameters Parameter Description Page Title The title of the page. Page Location (Required) The full URL to the page. User Properties User properties describe segments of the user base, such as language preference or geographic location. You can configure these into the section "Templates." Item ID Either Item ID or Item Name is required. Item Name Either Item ID or Item Name is required. Affiliation A product affiliation to designate a supplying company or physical store location. Event-level and item-level affiliation parameters are independent. Coupon The coupon name or code associated with the item. Event-level and item-level coupon parameters are independent. Currency The currency, in 3-letter ISO 4217 format. If set, event-level currency is ignored. Multiple currencies in an event are not supported, so all entries will contain the same currency value. Discount (number) The monetary discount value associated with the item. Index (number) The index or position of the item in the list. Item Brand The brand of the item. Item Category The category of the item. If used as part of a category hierarchy or taxonomy, then this is the first category. Item Category 2 The second category hierarchy or additional taxonomy for the item. Item Category 3 The third category hierarchy or additional taxonomy for the item. Item Category 4 The fourth category hierarchy or additional taxonomy for the item. Item Category 5 The fifth category hierarchy or additional taxonomy for the item. Item List ID The ID of the list in which the item was presented to the user. If set, event-level item_list_id is ignored. If not set, event-level item_list_id is used (if present). Item List Name The name of the list in which the item was presented to the user. If set, event-level item_list_name is ignored. If not set, event-level item_list_name is used (if present). Item Variant The item variant or unique code or description for additional item details or options. Location ID The location associated with the item. It's recommended to use the Google Place ID that corresponds to the associated item. A custom location ID can also be used. If set, event-level location_id is ignored. If not set, event-level location_id is used (if present). Price (number) The monetary price of the item, in units of the specified currency parameter. Quantity (number) Item quantity. Template Variables Provide template variables as data input for templates. For more information, read Template Variables Guide. Name nested template variables with the dot notation (For example: items.name ). Nested template variables are typically built from data layer list attributes. Templates Provide templates to be referenced in User Properties. For more information, read Templates Guide. Templates are injected by name with double curly braces into supported fields (for example: {{SomeTemplateName}} ). Send PageView Event Overview This action is used to pass website page view events to Google Analytics. Body Parameters Parameter Description Client ID (Required) A unique identifier for a client. This identifier must use the Client ID set by the Google Analytics 4 tag. For more information, read the Google Analytics 4 (GA4) Tag Setup Guide. Measurement ID Override Measurement ID. For example, the identifier for a Data Stream. Firebase App ID Override (Required) The identifier for a Firebase app. This setting overrides Firebase App ID used in the configuration section. User ID A unique identifier for a user. If you include user_id in your Google Analytics 4 Measurement Protocol events, you must also include it in the client-side events. Timestamp Micros A Unix timestamp (in microseconds) for the time to associate with the event. Set this to record events that happened in the past. This value can be overridden via user_property or event timestamps. Events can be backdated up to 3 calendar days based on the property’s timezone. Non Personalized Ads Set this to true to indicate these events are not used for personalized ads. Event Parameters Parameter Description Page Title The title of the page. Page Location (Required) The full URL to the page. Additional parameters can be passed, but they are not required to allow tracking of the page view event. Google Payload As shown in the following example payload, the events.name value is page_view , and required parameters are page_location and client_id : { "events": [ { "name": "page_view", "params": { "page_location": "http://demosite.com/ecomm/category.html", ...other mapped params... } } ], "client_id": "017f6ae7e7a40014b19d17739b3d05079002707100fb8" } Send Event Overview This action is used to send a non-pageview event to Google Analytics. You can select the event type from a  list of Google-defined events (for more information, read Measurement Protocol (Google Analytics 4) Events). In addition, you can select a Custom Event and then map the custom event value to “Custom Event Type”. Body Parameters Parameter Description Client ID (Required) A unique identifier for a client. The Client ID set by the Google Analytics 4 tag. The Cookie Matching Tag is the preferred implementation method. Measurement ID Override Measurement ID. For example, the identifier for a Data Stream. Firebase App ID Override The identifier for a Firebase app. This is a required field, and this setting overrides Firebase App ID used in the configuration section. User ID A unique identifier for a user. If you include user_id in your Google Analytics 4 Measurement Protocol events, you must also include it in the client-side events. Timestamp Micros A Unix timestamp (in microseconds) for the time to associate with the event. Set this to record events that happened in the past. This value can be overridden via user_property or event timestamps. Events can be backdated up to 3 calendar days based on the property's timezone Non Personalized Ads Set this to true to indicate these events are not used for personalized ads. Event and Event Parameters In addition to the general event parameters listed previously, each event type accepts additional parameters. The following table lists required and optional parameters for each event type: Event Type Description Event-Specific Parameters Add Payment Information When a user has submitted their payment information. Event Parameters: Currency (Required) Value (Required) Item Parameters: Item ID (Required) Item Name (Required) Add Shipping Information When a user has submitted their shipping information. Event Parameters: Currency (Required) Value (Required) Coupon (optional) Shipping Tier (optional) Item Parameters: Item ID (Required) Item Name (Required) Add to Wishlist When an item was added to a wishlist. Use this event to identify popular gift items in your app. Event Parameters: Currency (Required) Value (Required) Item Parameters: Item ID (Required) Item Name (Required) Begin Checkout When a user has begun a checkout. Event Parameters: Currency (Required) Value (Required) Coupon (optional) Item Parameters: Item ID (Required) Item Name (Required) Earn Virtual Currency When a user has been awarded virtual currency. Log this event with spend_virtual_currency to better understand your virtual economy. Event Parameters: Virtual Currency Name (optional) - The name of the virtual currency. Value (optional) - The value of the virtual currency. Generate Lead When a lead has been generated. Use this event to better understand the efficacy of your re-engagement campaigns. Event Parameters: Currency (Required) Value (Required) Join Group When a user joins a group, such as a guild, team, or family. Use this event to analyze how popular certain groups or social features are. Event Parameter: Group ID (optional) - The ID of the group. Level Up When a player has leveled up. Use this event to measure the level distribution of your user base and identify levels that are difficult to complete. Event Parameters: Level (optional) - The level of the character. Character (optional) - The character that leveled up. Login When a user has logged in. Event Parameter: Method (optional) - method used to log in. Post Score When a user posts a score. Use this event to understand how users are performing in your game and correlate high scores with audiences or behaviors. Event Parameters: score (Required) - score to post. level (optional) - level of the character. character (optional) - the character that leveled up. Purchase When one or more items have been purchased by a user. Event Parameters: Transaction ID (Required) Value (Required) Currency (Required) Item Parameters: Item ID (Required) Item Name (Required) Refund When a user was issued a refund. Event Parameters: Transaction_id (Required) Value (Required) Currency (Required) Item Parameters: Item ID (Required) Item Name (Required) Remove from Cart When a user removed an item from a cart. Event Parameters: Currency (Required) Value (Required) Item Parameters: Item ID (Required) Item Name (Required) Search When a user performed a search. Use this event to help identify the most popular content in your app. Event Parameter: Search Term (Required) Select Content When a user selected some content of a certain type. Use this event to identify popular content and categories of content in your app. Event Parameter: Content Type (optional) Item ID (optional) Select Item When a user selected an item from a list. Event Parameter: Item ID (Required) Item Name (Required) Select Promotion When a user selected a promotion from a list. Event Parameters: Creative Name (optional) Creative Slot (optional) Location ID (optional) Promotion ID (optional) Promotion Name (optional) Item Parameters: Item ID (Required) Item Name (Required) Share When a user shared content. Event Parameters: Method (optional) Content Type (optional) Item ID (optional) Sign up When a user signs up for an account. Use this event to understand the different behaviors of logged in and logged out users. Event Parameter: Method (optional) Spend Virtual Currency When a user purchased virtual goods. Use this event to identify the most popular virtual goods. Event Parameters: Value (Required) Virtual Currency Name (Required) Tutorial Begin When a user started the on-boarding process. Use this in a funnel with tutorial_complete to measure how many users complete the tutorial. There are no required parameters for this event. Tutorial Complete When a user completed your on-boarding process. Use this in a funnel with tutorial_begin to measure how many users complete the tutorial. There are no required parameters for this event. Unlock Achievement When a user unlocked an achievement. Use this event to better understand how users experience your game. Event Parameter: Achievement ID (Required) View Cart When a user viewed their cart. Event Parameters: Currency (Required) Value (Required) Item Parameters: Item ID (Required) Item Name (Required) View Item When a user viewed specific content. Use this event to identify the most popular viewed items. Event Parameters: Currency (Required) Value (Required) Item Parameters: Item ID (Required) Item Name (Required) View Item List When a user viewed a list of items of a certain category. Event Parameters: Item List ID (Required) Item Name (Required) Item Parameters: Item ID (Required) Item Name (Required) View Promotion When a user viewed a promotion from a list. Event Parameters: creative name (optional) Creative Slot (optional) Location ID (optional) Promotion ID (optional) Promotion Name (optional) Item Parameters: Item ID (Required) Item Name (Required) View Search Results When a user has been presented with search results Event Parameter: Search Term (optional) Custom Event Use this event to support custom events not defined by Google’s pre-set events. There are no required parameters for this event. To view a full list of supported events, read  Measurement Protocol (Google Analytics 4) events. Send Firebase Event Overview This action is used to send a Firebase event to Google Analytics. The configuration is the same as Send Event, but you also need to supply an App Instance ID. This connector action event type is primarily used to track Mobile Application data for passing to Firebase for analytics. Parameters Description App Instance ID (Required) Uniquely identifies a specific installation of a Firebase app. This value needs to be retrieved through the Firebase SDK. Firebase App ID Override The identifier for a Firebase app. This is a required field, and this setting overrides Firebase App ID used in the configuration section. User ID (Optional) A unique identifier for a user. Timestamp Micros (Optional) A Unix timestamp (in microseconds) for the time to associate with the event. Non Personalized Ads (Optional) Set this to true to indicate these events are not used for personalized ads. Event Parameters This action supports the same general event parameters as the Send Event action, and it also supports the same event-specific parameters. User Properties User properties describe segments of your user base, such as language preference or geographic location. Analytics automatically logs some user properties. If you want to collect additional properties, you can set up to 25 additional user properties per project. Read [GA4] Custom dimensions and metrics and Firebase Custom user properties to learn how to set and register user properties. Related Documentation Google Analytics 4 Measurement Protocol Google Analytics 4 Event Measurement Protocol Events Google Analytics 4 Client-side Tag Configuration ... View more

Learn about the new features and fixes released in April 2022. Tealium iQ Tag Management Fixed an issue with duplication of items in the Admin menu when switching profiles or versions. Updated the profile switcher to list entries in alphabetical order. Client-Side Tags New marketplace tag: Epsilon Partner Sync Web Service. New marketplace tag: Rokt. Fixed an issue with the Google Analytics Tag failing when it checks configuration attributes, but tries to use non-existent attributes. Fixed an issue with the Google Analytics 4 tag where the event_callback parameter fails to map properly. Fixed an issue with the Tealium Collect Tag that caused a 400 error when switching from the default endpoint to the HTTP API endpoint while changing to a non-default (Global) region. Tealium EventStream and Tealium AudienceStream Fixed an issue in the assigned actions tab where deactivated connectors and actions were improperly appearing as active. Fixed an issue in the data sources interface to properly obscure passwords and other credentials. Fixed an issue in the event feed interface with invalid dates. Fixed an issue with attribute enrichments to ensure that only users with permissions to use IP addresses can include Client IP in rules. Updated the connectors interface to improve scrolling, collapsed views, and expanded views. Updated the event feed interface to allow duplication of event feeds. Updated the manage rules tool with a new search box. Updated the visitor lookup tool with a new keyword search box. Updated the visitor lookup tool to include a JSON viewer.  Tealium Predict ML Released significant improvements in the workflows to create, train, and deploy models. (Learn more) Server-Side Connectors New/Cool Stuff New marketplace connector: Amazon Advertising DSP. New marketplace connector: Doceree. New marketplace connector: Epsilon Event API. Fixes Updated the Google Ads API connector to version 10. (Learn more) Updated the TikTok connector to include Access Token, App ID and Secret in its configuration. (Learn more) Fixed an issue with the Firebase Cloud Messaging connector where a 200 HTTP response that contains error messages would fail to parse properly. ... View more

This article describes how to set up the Epsilon Partner Sync Web Service Tag tag in your Tealium iQ Tag Management account. Epsilon is the leader in outcome-based marketing with a rich, 50-year heritage in helping marketers anticipate, activate, and prove measurable business outcomes. In this article: Tag Configuration First, go to the tag marketplace and add the Epsilon Partner Sync Web Service Tag tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Advertiser Identifier: dtm_cid Secondary Advertiser Identifier: dtm_cmagic Page Visit Form ID: dtm_fid Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Tag Configuration Variable Description Advertiser Identifier (dtm_cid) [String] Secondary Advertiser Identifier (dtm_cmagic) [String] Page Visit Form ID (dtm_fid) [String] User ID (dtm_cookie_id) [String] dtm_token_s [String] dtmc_tcf_string [String] ... View more

This article describes how to set up the Doceree connector. Doceree is a global network of physician-only platforms for programmatic marketing of targeted ads for physicians. The Doceree Connector allows users to manage Doceree audiences and users. In this article: Connector Actions Action Name AudienceStream EventStream Add User NPI ✓ ✗ Remove User NPI ✓ ✗ Configure Settings Navigate to the Connector Marketplace and add a new connector. For general instructions on how to add a connector, see the About Connectors article. After adding the connector, configure the following settings: Username Required: Username for your Doceree account. Password Required: Password for your Doceree account. Click Done when you are finished configuring the connector. Action Settings — Parameters and Options Click Continue to configure the connector actions. Enter in a name for the action and then select the action type from the drop-down menu. The following section describes how to set up parameters and options for each action. Action — Add User NPI Batch Limits This action uses batched requests to support high-volume data transfers to the vendor. Requests are queued until one of the following thresholds is met: Max number of requests: 1000 Max time since oldest request: 10 minutes Max size of requests: 1 MB Parameters Parameter Description Account The Doceree account associated with this audience. Audience ID The audience that you want to add the user to. NPI The unique identifier (NPI) for the user. Action — Remove User NPI Parameters Parameter Description Account The Doceree account associated with this audience. Audience ID The audience that you want to remove the user from. NPI The unique identifier (NPI) for the user. ... View more

This article describes how to set up the Rokt tag in your Tealium iQ Tag Management account. Immediately add profit with third-party offers from well-known advertisers on your confirmation page through Rokt Ecommerce. You can also optimize campaign performance for Rokt Ads by integrating conversion attribution through Tealium. For more information about Rokt's suite of SDKs and APIs, please read the Rokt Integration Guides. In this article: Tag Tips Use mapping to override the standard config values and trigger events. Tag Configuration First, go to the tag marketplace and add the Rokt tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Rokt Account ID: Your Rokt account ID. Two-step Email: Send email address only on positive engagement. Use Sandbox: Send events to sandbox account for testing. Load Rules Load Rules determine when and where to load an instance of the Rokt tag on your site. Create a Load Rule to load the Rokt tag on your conversion page. Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Standard Variable Description Email (email) First Name (firstname) Last Name (lastname) Mobile Number (mobile) Zip or Postal Code (zipcode) Country (country) Language (language) Use Sandbox (sandbox) E-Commerce Variable Attribute Description Confirmation Number (confirmationref) This variable overrides the _corder variable. Amount (amount) This variable overrides the _ctotal variable. Currency (currency) This variable overrides the _ccurrency variable. Payment Type (paymenttype)   ccbin (ccbin)   List of Item Prices (price) [Array] This array overrides the_cprice variable. List of Item Quantites  (quantity) [Array] This array overrides the_cquan variable List of Item Major Categories  (majorcat) [Array] This array overrides the_ccat variable List of Item Major Category IDs (majorcatid) [Array] List of Item Minor Categories  (minorcat) [Array] This array overrides the _ccat2 variable List of Item Minor Category IDs  (minorcatid) [Array] List of Product Names  (productname) [Array] This array overrides the_cprodname variable. List of Item SKUs (sku) [Array] This array overrides the_csku variable. ... View more

This article describes how to set up the Schema App tag in your Tealium iQ Tag Management account. Schema App is an organic search catalyst, designed to help digital marketers increase organic search performance, productivity and profitably by quickly and easily integrating schema markup across their web portfolio. Schema App is the world's leading platform for adopting and maintaining Schema Markup at scale without writing, copying, or pasting code. Just enter the information from your page, click save, and you are done. Stay on the forefront of organic search with Schema App. In this article: Tag Tips Account ID and API Key can be found in the application under the menu Integrations > JavaScript page. Tag Configuration First, go to the tag marketplace and add the Schema App tag (Learn more about how to add a tag). After adding the tag, configure the following settings: Account ID: Your Schema App Account ID API Key: Your Schema App API Key Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings. The available categories are: Standard Variable Description Account ID (account_id) API Key (api_key) Base URL/API Endpoint (base_url) ... View more