Tealium Learning Center

This article describes usage report types and how to view and use the resulting data. In this article: How it Works The usage report provides reporting for the two (2) key metrics of your account: events and visitors. This data allows you to analyze how your visitor and event metrics are utilized by various Tealium services in your account and how the usage has varied over time. The usage report also helps estimate costs for data usage so that you can make informed decisions about your implementation. Viewing the Usage Report Go to Data Supply Chain > Usage Reports for an account-level view specific to the profile you are logged in as. The default dashboard view varies depending on which profile you are logged into. Viewing Reports for a Profile Use the following steps to view a usage report for a profile: Go to Data Supply Chain > Usage Reports. Select a profile and report type from the drop-down lists. (Default is All Profiles and All Usage Reports.) Click the calendar fields to select the date range for the report. The default date range is set between January 1st of the current year and the current date. To change the default, contact your account administrator. Click Get Report. The requested reports display. Interpreting Reports Reports are displayed as line graphs. The date range is plotted on the horizontal axis and the metric, such as the number of events and visitors, is plotted along the vertical axis and marked by dots. Clicking on a dot displays the aggregate metric values and the day on which it was aggregated. You may view reports as part of the All Usage Report or select individual report types from the drop-down list. Report Types The following lists describe the available report types. All Usage Reports Displays all reports sequentially in the reports dashboard. This is the default view. Data Collection Reports Data Collection reports correspond to real-time and offline events flowing into your Customer Data Hub profile and return the following reports: Total Inbound Events The sum total of real-time and file import events. Data usage cost for EventStream is calculated based on the Total Inbound Events report. Total Real-time Events The number of events that are captured by the Tealium Collect tag from your website or mobile app in the date range specified. Learn more about Live Events and Feeds. Total File Import Events The number of file import rows or lines imported into AudienceStream.  Total AudienceStream Events The number of live events received by AudienceStream. If the AudienceStream event filter is enabled, this report only includes filtered AudienceStream events. Data usage cost for AudienceStream is calculated based on the Total AudienceStream Events report. Connector Reports Correspond to event usage by connectors and return the following reports: Total Connector Calls Sum total of server requests made for triggering EventStream and AudienceStream connector actions. Connector Calls - EventStream Number of server requests made by EventStream connector actions.  The number of connector calls contracted with EventStream is based on this report. Connector Calls - AudienceStream Number of server requests made by AudienceStream connector actions. Data Layer Enrichment Reports Data Layer Enrichment reports correspond to the AudienceStream Data Layer Enrichment service. This report returns the number of times the Tealium Collect tag made requests (calls) to the AudienceStream data layer for fetching the latest visitor profile. DataAccess Reports Data Access reports correspond to events and audiences exported through the DataAccess service and return the following reports: Total DataAccess Records Inserted The sum total of events and visitors exported using DataAccess. Total EventDB Events Inserted The number of events exported to the Amazon Redshift database assigned to your account/profile. Total EventStore Events Inserted The number of events exported to the Amazon S3 folder assigned to your account/profile. Total AudienceDB Visitors Inserted The number of visitors exported to the Amazon Redshift database assigned to your account/profile. Total AudienceStore visitors Inserted The number of visitors exported to the Amazon S3 folder assigned to your account/profile. Billing Estimation Usage costs for EventStream, EventDB, and EventStore products, as well as customers with EDF and CDH bundles are calculated based on the Total Inbound Events report, which includes the total volume of events flowing into your account. Usage costs for AudienceStream, AudienceDB, AudienceStore and Predict products are calculated based on the AudienceStream Filtered Events report. Every event, at its point of entry into the Tealium Customer Data Hub, counts towards the total volume and is charged equally. The usage report does not provide billing or pricing information. Your final usage cost is determined not just by your event volume, but also by your contract terms and implementation setup. Contact your account manager for all billing and pricing inquiries. FAQ Why can't I see today's data in my reports? Usage reports can take up to 48 hours to completely process and display the data flowing through Customer Data Hub. If your date range only spans the last 24-48 hours, you may not see data populated in the reports. As a best practice, choose an end date that is at least 48 hours back from the current date. Why can't I choose a date prior to April 1, 2016? The usage reports provide data for up to one year from the time of their release. This method provides most accounts with the data they need to evaluate their annual billing cycle. ... View more

This article describes how to set up the Cheetah Digital connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send Email to Subscriber (Advanced API Call - ebmtrigger1) ✓ ✗ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: API Username The username for the API Category: Authentication Service API endpoint. API Password The password for the API Category: Authentication Service API endpoint. API URL Supports private IP networks, for example https://trig.{client-domain}.com/. Define your client domain if needed. Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Send Email to Subscriber (Advanced API Call - ebmtrigger1) Parameters Parameter Description email Required Target email address. eid Required Event ID tied to target mailing template. aid Affiliate ID for target mailing. from_address Sender/From email address. from_text Text part of from header. replyto Reply-To header. b Engage Global Suppression Tool (GST). certify Send with a third party certification stamp. mtype Certified message type. test Test flag to trigger non-deployed event. part Mailing part to use for the test. Preferred Content Type Optional HTML=Optional A specialized instance of a PARAM value that indicates the preferred content type: 0 – Text only 1 – HTML/Text multipart 2 – Rich Text/Text multipart Email CB Data Fields to Set Optional Add one line item per field (line items provided are pipe delimited). cb=Optional A list of client-defined suppression bit indexes for the Global Suppression Tool (GST) to change, ranging from 1 to 25. If the cb parameter is passed, the b parameter must also be specified with a value of 0 or 1. Indicates whether the standard stoplist should be included when evaluating suppression for an address. Email REQ Data Fields to Set Optional Add one line item per field (line items provided are pipe delimited). req=Optional Specify required personalization fields that must be non-empty for success. Looping dynamic content fields may only be required explicitly, replacing * with appropriate values ( ITEMS.* ). Alternatively, setting req to a value of 1 specifies that all personalization fields present must be non-empty. Set Dynamic Content Tags/Parameters Optional Add one line item per field (line items provided are pipe delimited). PARAM= The value of any upper case parameter is made available for substitution into the email in place of a tag consisting of two (2) percentage signs, the parameter name, and two (2) percentage signs. Example: For PARAM, the tag would be " %%PARAM%% . Uppercase parameters start with A - Z or _ , followed by any number of characters A - Z , 0 - 9 , or underscore ( _ ). Values are URL-decoded before substitution. Tags referring to parameters not supplied in the API call are replaced with an empty string. There is no size limit to values (entire order tables can be supplied). There is no versioning of the parameters for the three (3) different types of email creative (text, html, rich text/aol). If variable content needs to be formatted differently depending on creative, the API call should supply the different versions with different parameter names. Mailing should be set up to use version-appropriate tags. The parameters T , TRACK , and EMAIL are reserved for internal use. The API is error-tolerant for PARAM names. If a PARAM is supplied that does not exist in the template, it will be silently ignored. Ensure that you proofread all names so that they are not lost due to a spelling error. Enable Subscriber Lookup via getuser1 API Call Enabling this option triggers an extra API call where the target subscriber is looked-up up using the getuser1 API call. The result is matched against the Subscriber List ID configured in the next section, and if satisfied an email is sent via ebmtrigger1 API call. The AID returned from this API call will be used regardless and will override the configuration in the "Email General Data Fields to Set" section unless the "Exclude using AID returned from Subscriber Lookup" is checked. Exclude using AID returned from "Subscriber Lookup" This option is only used when "Subscriber Lookup" is also enabled. If checked the AID returned for the "Subscriber Lookup" API call will not be included in the subsequent ebmtrigger1 API call, otherwise the AID from "Subscriber Lookup" will be included and override the configurations in the "Email General Data Fields to Set" section. Target Subscriber List ID to match against Subscriber Lookup ( getuser1 API Call) This option is only used when "Subscriber Lookup" is also enabled. email See the "Email General Data Fields to Set" row in this table. Required The email address provided in "Email General Data Fields to Set" section will be used to lookup the subscriber. Target Subscriber List ID Required The subscriber list ID that is used to match against getuser1 API call response. Vendor Documentation Additional information is contained in the following vendor documentation attachments to this article: Cheetah Digital API Best Practices Messaging: Email Cheetah Digital API Technical Guide: login1 Messaging: Email Cheetah Digital API Technical Guide: ebmtrigger1 Messaging: Email ... View more

Problem You've followed our guide on Webtrends Tag: Basic Configuration and enabled the YouTube plug-in for Webtrends, but you aren't seeing any video tracking calls.  Solution If you are embedding the YouTube iframe player on your site then you also need to insert the YouTube iframe API. This is a JavaScript library hosted by YouTube that must be loaded into the page. The video tracking must also be activated with the   enablejsapi parameter on your video URLs. Enabling the API To enable the YouTube player to be controlled by the API: Append this key/value parameter to your video URLs: &enablejsapi=1 See more examples from YouTube. Loading the Iframe API To load the YouTube Iframe API: Add the Tealium Generic Tag and drag it above the WebTrends tag to ensure it fires first. In Advanced Settings, set the Custom Script Source to //www.youtube.com/iframe_api The WebTrends tag handles the rest of the YouTube video tracking functionality. From the Network panel of your browser console you can see the Webtrends video calls firing:   ... View more

Introduction   Understanding what is required to be implemented by your developers in order to use the Google Publisher Tag in Tealium iQ can be daunting but it needn't be - it is easy once you have read this guide.   Contents   1 Ad Slot Requirements    1.1 Requirements    1.2 Examples 2. Page Requirements    2.1 Divs for Ad Slot    2.2 Data Layer 3 Example Page Code 4 Tealium iQ Example Extension     1. Ad Slot Requirements   1.1 Requirements   First, you need to know what ad slots are required on any given page and what they need to look like. They key pieces of information you need to know are:   Hint! It is useful to read Google's example Tag Sample to understand the Google code   Required per Ad Slot   What? What is it? Notes Example Google Equivalent Code Div ID What is the <div> ID that we will be injecting the ad into. It needs to be unique per page but it doesn’t need to be unique across the whole site "gpt_mpu" googletag.defineSlot("/1234/travel/asia/food", [[468, 60], [728, 90], [300, 250]], "div-gpt-ad-123456789-1")   Ad Sizes Array of ad sizes it will support What ads sizes will it support? [468, 60], [728, 90], [300, 250] googletag.defineSlot("/1234/travel/asia/food", [[468, 60], [728, 90], [300, 250]], "div-gpt-ad-123456789-1") Targeted Ad Unit (slot ID) This is the "travel/asia/food" within "/1234/travel/asia/food" This can be populated by various vars in the data layer. For example: page_section = "travel" page_section_2 = "asia" page_section_3 = "food" Note: the network code can be set in Tealium page_section = "travel" page_section_2 = "asia" page_section_3 = "food" googletag.defineSlot("/1234/travel/asia/food", [[468, 60], [728, 90], [300, 250]], "div-gpt-ad-123456789-1") Key Value Targeting This adds additional targeting capabilities per ad slot You can have as many of these as Google will allow gender = "male" pos = "top" .setTargeting("gender", "male") .setTargeting("pos", "top")   In addition, if you have any Key Value Targeting requirements per page (i.e. targeting criteria relevant to every ad call on the page, e.g. "author" or "topic") we also need to know these:   Required per Page   What? What is it? Notes Example Google Equivalent Code Key Value Targeting (page-level) Allows you to add targeting criteria across all ad slots on a page You can have as many of these as Google will allow topic = "basketball" setTargeting("topic","basketball")     1.2 Examples Here are some examples of what you would need:   Required per Ad Slot   What is this? Div ID Ad Sizes Targeted Ad Unit (Slot ID) Key Value Targeting Leaderboard slot "gpt_leaderboard" [728, 90], [468, 60] page_section = "travel" page_section_2 = "asia" page_section_3 = "food" pos = "top" MPU slot "gpt_mpu" [336x268], [300,250] page_section = "travel" page_section_2 = "asia" page_section_3 = "food" pos = "content" MPU slot 2 "gpt_mpu_2" [336x268], [300,250] page_section = "travel" page_section_2 = "asia" page_section_3 = "food" pos = "footer" Skyscraper slot "gpt_skyscraper" [160x600] page_section = "travel" page_section_2 = "asia" page_section_3 = "food" pos = "out_of_page"   Required per Page   What? What is it? Notes Example Key Value Targeting (page-level) Allows you to add targeting criteria across all ad slots on a page You can have as many of these as Google will allow topic = "basketball"   2. Page Requirements   2.1 Divs for Ad Slot   Each page will require a <div> to be inserted into the page where each ad needs to be injected into. Each <div> needs an ID which matches the ad which needs to be injected:       These need to be generated server-side to ensure they are available immediately for Tealium to inject ads into.   2.2 Data Layer The data layer needs to contain the information about the ad slots as detailed above. This information must be made available in the Universal Data Object (UDO) called utag_data.   Normally, Tealium does not recommend nesting variables within the UDO but nesting will be much easier for generating ad calls.       utag_data = { ... "page_section_name": "travel", // an example variable for Slot ID, e.g. "/travel/asia/food" "page_section_name_2": "asia", // an example variable for Slot ID, e.g. "/travel/asia/food" "page_section_name_3": "food", // an example variable for Slot ID, e.g. "/travel/asia/food" "device_type": "desktop", // Page-level single key-value pair targeting (e.g. .setTargeting("device_type", "desktop")) "page_topics": ["eastern","stir fry"], // Page-level multiple values for the same key (e.g. .setTargeting("topics". ["eastern", "stir-fry"])) ... "ad_slots": { "gpt_leaderboard": { // div name 1 "name": "gpt_leaderboard", // div name 2 "sizes": [[728, 90],[468, 60]], "targeting": { "pos": ["top"] } }, "gpt_mpu": { // div name 2 "name": "gpt_mpu", // div name 2 "sizes": [[300, 250],[336, 280]], "targeting": { "pos": ["right"], "mobile": ["false"], } } } }   3. Example Page Code   An example page might look like this:   <head> ... <!-- Loading utag.sync synchronously --> <script type="text/javascript" src="//tags.tiqcdn.com/utag/account_name/profile_name/environment/utag.sync.js"></script> ... </head> <body> <!-- Tealium Universal Data Object --> <script type="text/javascript"> utag_data = { ... "page_section_name": "travel", "page_section_name_2": "asia", "page_section_name_3": "food", "device_type": "desktop", "page_topics": ["eastern","stir fry"], ... "ad_slots": { "gpt_leaderboard": { // div name 1 "name": "gpt_leaderboard", // div name 2 "sizes": [[728, 90],[468, 60]], "targeting": { "pos": ["top"] } }, "gpt_mpu": { // div name 2 "name": "gpt_mpu", // div name 2 "sizes": [[300, 250],[336, 280]], "targeting": { "pos": ["right"], "mobile": ["false"], } } } } </script> <!-- Tealium utag.js Async call --> <script type="text/javascript"> (function(a,b,c,d) { a='//tags.tiqcdn.com/utag/account_name/profile_name/environment/utag.js'; b=document;c='script'; d=b.createElement(c);d.src=a; d.type='text/java'+c; d.async=true; a=b.getElementsByTagName(c)[0]; a.parentNode.insertBefore(d,a); })(); </script> ... <!-- Ad Slot 1 --> <div id="gpt_leaderboard"></div> ... <!-- Ad Slot 2 --> <div id="gpt_mpu"></div> ... </body>   4. Tealium iQ Example Extension   Here is an example Javascript extension which can be scoped to the GPT tag to generate the relevant ad calls. This will work with the above example:   // ### CONFIGURATION ### b.gpt_network_code = "YOUR NETWORK CODE"; // replace with your network code // ### DO NOT EDIT BELOW THIS LINE ### b.gpt_slot_id = "/" + b.gpt_network_code + "/" + b.page_section_name + "/" + b.page_section_name_2 + "/" + b.page_section_name_3; u.gptSlots = []; u.setTargeting = {}; // loop through and generate ad slots if (utag.ut.typeOf(b.ad_slots) === "object") { for (varName in b.ad_slots) { u.gptSlots.push([b.gpt_slot_id, b.ad_slots[varName].sizes, b.ad_slots[varName].name,b.ad_slots[varName].targeting]) } }       ... View more