Tealium Learning Center

This is a guide to validating client-side tags that have been implemented in Tealium iQ. It will cover several methods to ensure that tags are loading and that data is being sent. Validation of data received by the vendor should be coordinated with your vendor representative. In this article: Table of Contents Placeholder Getting Started The validation methods covered here are performed using Google Chrome as the browser and vendor specific plugins. Vendor Plugins We recommend downloading the following plugins for Google Chrome: Google Tag Assistant Google Analytics Debugger Facebook Pixel Helper Adobe Analytics Debugger Tealium Tools Chrome Developer Tools We recommend taking a tutorial on Chrome Dev Tools to familiarize yourself with the interface: Chrome Dev Tools Tutorial Chrome Dev Tools Documentation Validating with Google Tag Assistant The following list provides links that describe parameters for popular Google tags: Google Analytics Parameters Cheat Sheet Google Analytics Enhanced Ecommerce Parameters Cheat Sheet Google Adwords Remarketing Parameters Google Adwords Remarketing Verification More About Google Tag Assistant Use the following steps to validate using the Google Tag Assistant: Once you have downloaded the plugin, open your site to where the Tealium tags are installed and click the plugin icon in the top right corner of your Chrome window. Select "Validate All Pages" then click Done. Click Allow to allow the plugin to check if other plugins are blocking any Google tags and then click on any Google tags appearing in the plugin interface for more details. For Google Analytics, click either Pageview Requests or Events. The following example shows the results that display when you click Pageview Requests. When you click either of those, you will see the parameters sent to Google. Clicking the URLs tab provides a more detailed view. The default view shows the unformatted URL request. Change to the formatted view by clicking table button. This will allow you to see each parameter sent to Google. However, you should be fine viewing the initial "Metadata" tab.   You can validate any other Google tags using this plugin as well. Some examples are: Floodlight, Google Ads, Google Publisher, DFP, Google Trusted Stores. Validating with Google Debugger The following list provides links that describe parameters for the Google Analytics tag: Google Analytics Parameters Cheat Sheet Google Analytics Enhanced Ecommerce Parameters Cheat Sheet Use the following steps to validate with Google Debugger: Once you have downloaded the plugin, open your site where the Tealium tags are installed and click the plugin icon in the top right corner of your Chrome window. The live output in the Chrome Developer Tools Console displays. Start triggering events and page views and you will see the Google Analytics output in the console. The output displays what is getting sent to Google Analytics. Validating with Facebook Pixel Helper There are a number of events that will be displayed in this window depending on the type of interaction. Go to Facebook Events to learn about these events and the parameters that can be sent with each. Use the following steps to validate with the Facebook Pixel Helper: Once you have downloaded the plugin, open your site where the Tealium tags are installed and click the plugin icon in the top right corner of your Chrome window. Once you expand an event within the plugin, the parameters display as follows: Each pixel type detected can be expanded to display the details. In this example, the "AddToCart" pixel event is shown: The data that displays is the data sent to Facebook. Validating with Adobe Analytics Debugger There are a number of parameters that will be displayed in the Adobe Analytics debugger. Go to Adobe Query Parameters to learn more about the parameters for the Adobe Analytics (AppMeasurement) tag. Use the following steps to validate using the Adobe Analytics Debugger: Once you have downloaded the plugin, open your site where the Tealium tags are installed and click the plugin icon in the top right corner of your Chrome window. The screen displays the live output in the Chrome Developer Tools Console. Start triggering events and pageviews and the Adobe Analytics output will display in the console. This console output represents all the data that is sent to Adobe in each server call. Validating with Chrome Developer Tools Not all vendors have their own plugins. In this case, we recommend using the Chrome Developer Tools' Network tab to validate that requests are successfully sent by the tags from the browser. For more information, see the Chrome DevTools Network Analysis and search the document for "View query string parameters" to learn more about the parameters available. Use the following steps to validate using Chrome Developer tools: Open your site where Tealium is installed. To display the Developer Tools, right-click the page and select Inspect. Click the Network tab. This example uses Google Analytics, but you can use any tag. In Tealium iQ, find the Tracking ID in the configuration portion of the tag and copy the ID number. Navigate back to your site where the Network tab is still open and paste the ID number in the "Filter" box. Click the Preserve Log checkbox and start executing page views and/or events. The network requests being sent by the tag displays. Click an entry to view the details of the request. You will see several sections of information here, such as "Request URL", "Response Headers" "Cookies" and "Query Parameters". We are most interested in "Request URL" and "Query Parameters" but you will find more information on the others here: Chrome Network Tab The Request URL is the entire URL that was either sent as a POST or GET to the vendor's server. This URL includes the server URL and the query string parameters (the data) that the vendor will receive. The Query String Parameters are a list of the parameters (not including the server url) that the vendor is receiving. This is most likely how data is passed from the page to the vendor. The following example shows the Query String Parameters from an Adobe AppMeasurement server call:  Troubleshooting There may be an instance where you find something missing in the Query Parameters or one of the plugins. If you would like to try and troubleshoot this yourself, there are some things you can try. First, use Web Companion or the Universal Tag Monitor to verify the data layer variables used in your page and event tracking calls. Learn more. If your data layer is incomplete, it may require additional development work to include the variables you need. If your data layer looks good and your tracking calls are working as expected, but your vendor tags are not receiving the data you expect, the next step is to verify the data mappings for your tag. Data mappings tell Tealium which data layer variables to send to the corresponding vendor parameters. Learn more. ... View more

This article will guide you through how to configure Tealium on an Android and/or iOS mobile app so you can properly track app downloads via Adobe Analytics or another analytics software, like Google Analytics.  In this article: Table of Contents Placeholder The Problem Tracking mobile app downloads and attributing downloads to marketing/ad spend is a tricky business, and is made more complicated by the fact that the different mobile operating systems do not handle the information in the same way. The Solution On Android, Google provides a handy referrer string to the app on first launch (known as "Install Referrer"), which provides standard Google "utm" campaign parameters in URL format that can be retrieved by your app developer and passed to third party analytics tools. On iOS, however, Apple does not provide this information, so the only way to get it is by device "fingerprinting", which attempts to identify a device by generating a hash from elements in the HTTP header information passed to the server (in Adobe's solution, they use the IP address and browser User Agent string to identify a device, with a 10 minute expiry time). Because of this limitation on iOS, acquisition information on iOS will always be less accurate than on Android. It is conceivable that within the 10 minute attribution "window", 2 users with the same user agent and IP address could download the same app (if, for example, they were both connecting through an HTTP proxy server). In this case, only the first user to launch the app would receive the attribution data. This situation could not arise on Android, because every download is uniquely tied to an individual device. Download Flow iOS Ad -> Adobe Acquisition V3 -> [Device Fingerprint stored by Adobe] -> iOS App Store -> App downloaded -|END| App Launch -> App sends beacon to Adobe Acquisition server -> Adobe responds with campaign information relating to this download on the device -> Data passed to Adobe Analytics with a lifecycle hit as context data -|END|  Android Ad -> Adobe Acquisition V3 -> [Unique one-time code generated by Adobe] -> Google Play store with UTM parameters -> App downloaded -|END| App Launch -> Broadcast Receiver receives INSTALL_REFERRER intent, containing utm parameters and one-time code -> App sends one time code to Adobe Acquisition V3 -> Adobe responds with campaign information -> Data passed to Adobe Analytics with a lifecycle hit as context data -|END| Full Description of the Process on Android For Android, the process is slightly different: Adobe link goes through to the Play Store and passes a "utm_content" parameter containing a unique ID App is launched. App receives INSTALL_REFERRER intent containing utm_content parameter with unique Adobe ID App makes a call to: http://c00.adobe.com/v3/<app_id>/end?a_ugid=<Unique_ID from utm_content> Adobe returns acquisition data to the app Callback fires and passes data to Adobe Analytics Tealium Configuration to Support Acquisition Tracking Usually, Adobe's Enterprise Cloud SDK would handle the acquisition process automatically via the Adobe SDK, but since Tealium does not require the Adobe SDK, we have to add some special config in Tealium iQ Tag Management to make this work. On iOS, no additional code is required in your app, but on Android, you will need to implement a Broadcast Receiver for the INSTALL_REFERRER intent. Please note that you can only have a single Broadcast Receiver listening for the INSTALL_REFERRER Intent, so if you have a requirement to trigger multiple Broadcast Receivers, you will need to implement a generic one, which will in turn trigger each Broadcast Receiver available in the app. Please see here for more info: http://stackoverflow.com/questions/9694639/more-than-one-broadcastreceiver-for-the-same-intent-with-contradictory-doc-and-p To assist with this, Tealium has provided an acquisition helper framework, which will set up the broadcast receiver for you. This can be found on the Tealium GitHub pages in the "support" directory. https://github.com/Tealium/tealium-android/tree/master/Support/InstallReferrer  Tag Configuration Requirements and Instructions Log in to Tealium iQ and add a new tag: "Custom Remote Command" Set the "Command ID" field in the tag's user interface to "_http". This tells the Custom Remote Command  system to make an HTTP request. To tell the tag which URL we wish to call, we need to add a few variables to the profile, which we'll set using extensions. Refer to the list of required variables below. Add a Load Rule to the Custom Remote Command tag:   utag_main_adobe_attribution is not defined This will ensure the tag only gets called once or until the acquisition data was returned successfully from Adobe. Required Variables The following variables are required: Callback – recommended variable name "callback" The callback function that will send the data to the Adobe Analytics tag URL – recommended variable name "acq_url" The URL that will be called to retrieve the acquisition campaign info Method – recommended variable name "acq_method" The HTTP method we'll be calling to retrieve the data. In this case, it will be "GET". Headers – recommended variable name "acq_headers" The HTTP header information we want to pass along with the request. This mapping accepts a JavaScript Object (JSON). Adobe matches based on User-Agent, so we need to ensure the Remote Command system has the correct User-Agent header set on the request. Install Referrer – recommended variable name "install_referrer" [First Party Cookie] utag_main_adobe_attribution – used to store acquisition data in a cookie to ensure the data is only sent to Adobe once.  Extension Requirements and Instructions  iOS Instructions Use the following steps for iOS: Add a "Set Data Values" extension, and select the three (3) new variables we created above as the target. The variables should be set to the following values: acq_method = [Text Value] -> GET acq_headers = [JS Code] -> {'User-Agent' : navigator.userAgent}; acq_url = [Text Value] -> https://c00.adobe.com/v3/<app_id>/end Add the following condition to the extension: ' platform ' contains (ignore case) 'ios' Android Instructions Use the following steps for Android:  Add a Set Data Values Extension, and select the three (3) new variables we created above as the target. They should be set to the following values, and in the following order: install_referrer = [JS Code] -> b.install_referrer.split("utm_content=")[1].split("&")[0]; acq_method = [Text Value] -> GET acq_headers = [JS Code] -> {'User-Agent' : navigator.userAgent}; acq_url = [JS Code] -> "https://c00.adobe.com/v3/<app_id>/end?a_ugid=" + b.install_referrer Add the following condition to the extension: ' platform ' contains (ignore case) 'android' AND install_referrer is populated The contents of these URLs are static for all Adobe clients, with the exception of the Tracking ID (long alphanumeric string between /v3/ and /end). This string is available in the Adobe Mobile Services UI. To get it, you must have added your app to the Mobile Services UI, then navigate to the SDK Acquisition Options config box and click More Details. Add Callback Extension Add a JavaScript Code Extension, scoped to the Custom Remote Command tag. This will contain our callback function which allows us to send the acquisition data returned from the Adobe servers to any endpoint we like (e.g. Adobe Analytics served through Tealium iQ Tag Manager) Add the following code to the JavaScript Extension. Feel free to customize the code to change what happens with the attribution data. Currently, the data is sent via a utag.link call to a specified tag ID, and also persisted in a first-party cookie for the duration of the session for future reference.  b.callback = function (code, body) { // var tag_id = null; // this will not fire any tags when the callback runs var tag_id = ['3', '5']; // this will fire tag with UID 3 and 5 when the callback runs if (body && body.toString().indexOf('null') === -1) { var context_data = JSON.parse(body).contextData; if (context_data) { utag.loader.SC('utag_main', {'adobe_attribution' : JSON.stringify(body)}); // store attribution data in utag_main cookie for later use var adobe_referrer_campaignname = context_data['a.referrer.campaign.name']; var adobe_referrer_trackingcode = context_data['a.referrer.campaign.trackingcode']; if (tag_id === null) { // fire attribution hit to all tags utag.link({ "adobe_attribution" : JSON.stringify(body), "adobe_referrer_campaignname" : adobe_referrer_campaignname, "adobe_referrer_trackingcode" : adobe_referrer_trackingcode, "link_name" : "acquisition" }); } else { utag.link({ "adobe_attribution" : JSON.stringify(body), "adobe_referrer_campaignname" : adobe_referrer_campaignname, "adobe_referrer_trackingcode" : adobe_referrer_trackingcode, "link_name" : "acquisition" }, null, tag_id); } } } }; Tag Mappings Custom Remote Command Tag acq_url -> url acq_method -> method acq_headers -> headers callback -> callback_function Adobe Analytics Tag Mappings (tag version AppMeasurement for JS 1.6.3) link_name -> link_name adobe_referrer_trackingcode -> contextData.a.referrer.campaign.trackingcode adobe_referrer_campaignname -> contextData.a.referrer.campaign.name The variables can also be mapped to other tags, such as Google Analytics, and the same acquisition data can also be sent to these tags. If the "ClearVars" option is not set in the Adobe config, the campaign data will be sent on every Adobe request until the app is restarted Testing iOS Testing Use the following steps for iOS testing. No additional tools or software is required. Open the following link in the Safari browser on your iDevice https://c00.adobe.com/v3/<app_id>/start?a_i_id=964656807&a_dd=i&ctxa.referrer.campaign.name=testcampname&ctxa.referrer.campaign.trackingcode=mytrackingcode Substitute the following values for your own: a_i_id The Apple application ID that uniquely identifies your app on the App Store Tracking Code and Campaign Name| (Optional) The trackingcode and campaign name parameters can be substituted for your own values if you wish The Adobe Tracking ID Long string between /v3/ and /star t You must obtain this from the Adobe Analytics console. Ensure you have correctly configured Tealium iQ, and then launch the app on your device. If you have configured TiQ correctly, you'll see a hit going out to Adobe Analytics with your campaign data attached, link name (pev2 param) "acquisition" See also: https://marketing.adobe.com/resources/help/en_US/mobile/ios/t_testing-version-3-acquisition.html Android Testing Use the following steps for Android testing. These steps require the Tealium InstallReferrer module and Android Studio. Follow an Adobe acquisition link to the Google Play Store. Note the utm parameters that are passed to the Play Store URL. Example Adobe link: https://c00.adobe.com/v3/<app_id>/start?a_g_id=com.tealium.digitalvelocity&a_dd=g&ctxa.referrer.campaign.name=name&ctxa.referrer.campaign.trackingcode=trackingcode This MUST be done on your Android device. Once your device has followed the link, copy the long string in the "utm_content" parameter that Adobe passed to the Play store, e.g:  https://play.google.com/store/apps/details?id=com.tealium.digitalvelocity&referrer=utm_campaign%3Dadb_acq_v3%26utm_source%3Dadb_acq_v3%26utm_content%3Dffe2779809e4ac4bf8f5842dce4c27a1dbe36918 The parameters are URL-encoded, and %3D is an equals symbol. Be sure not to include this in the string you copy down. Launch the app. Paste the following into your terminal (uses ADB - Android Debug Bridge). am broadcast -a com.android.vending.INSTALL_REFERRER -n "com.tealium.blankapp/com.tealium.installreferrer.InstallReferrerReceiver" --es "referrer" "utm_source=<source_from_adobe>&utm_medium=<medium_from_adobe>&utm_term=<term_from_adobe>&utm_content=46b25e284dc36d5a7ef8f0e6b393febe3fcc8327&utm_campaign=<name_from_adobe>";  Be sure to substitute "com.tealium.blankapp" for the fully-qualified package name of your app (e.g. com.yourcompany.appname). Also ensure that you substitute the value passed to utm_content for the actual value you saved earlier on. Example Adobe Analytics hit (dummy campaign data "name" for campaign name and "trackingcode" for tracking code: ... View more