Tealium Learning Center

This article describes how to set up the Optimizely Events connector in your Customer Data Hub account. The Beta version of this connector is currently available as an Experiment. (Learn more). This version can still be used if you already have it configured in your system but is no longer available in the marketplace. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send Event ✗ ✓ 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: Personal Token To authenticate, use a token in the request header generated from the following link: http://app.optimizely.com/v2/profile/api. All API request examples in this documentation use the same header. For more information on authentication, see Personal Token. 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 Event Parameters Parameter Description Account ID The Optimizely account to which these events should be attributed. Enrich Decisions Values are true or false. Should be set to true to enable the Optimizely Easy Event Tracking functionality. For more information about this field, see the Event API reference. See also How Optimizely counts conversions. Campaign ID Required The ID of the campaign containing this experiment. Experiment ID Required The ID of the experiment the visitor was exposed to. For Personalization Campaigns, explicitly send "null" as the Experiment ID for visitors not bucketed into an Experiment, in order to accurately calculate Campaign reach. Variation ID Required The ID of the variation the visitor was exposed to. For Personalization Campaigns, explicitly send "null" as the Variation ID for visitors not bucketed into any Experiment in order to accurately calculate campaign reach. Is Campaign Holdback Values are true or false. If true, the chosen experience was held back at the campaign level. Required for Personalization, omit otherwise. Timestamp Required Timestamp at which the event was generated, formatted in milliseconds since Unix epoch. Sends a {{unixTimestampMs}} by default if no value is provided by the user. UUID Required A unique identifier for this event. Created automatically using {{uuid}} . Used by Optimizely's backend to de-duplicate requests that are accidentally or erroneously replayed. Optimizely detects events that have the same entity_id , uuid and timestamp and saves only one of them. Ensure that each event uses a unique uuid or timestamp before sending. Entity ID Optional The ID of the entity corresponding to this attribute. Only required for custom attributes ( type="custom" ). Invalid for other attribute types. Event Name The event key (aka API name) for this event. Event Data Additional event data in key-value pairs. Tags Optional. Key-value attributes related to tags. If used, type and value must be included as two of the keys. Event Type The type of event. For example, to indicate a decision_point , type should be campaign_activated . Event Value A scalar value associated with an event. This should be some non-revenue number. Visitor ID Required A unique identifier for the visitor. Attributes Attributes associated with this visitor at the time of this request. Session ID A unique identifier that identifies the session context, if any, for these events. If omitted, the Optimizely backend calculates session-based results by inferring sessions and opening a session when an event is first received from a given visitor_id , and closing the session after 30 minutes with no events received for that visitor. Maximum session size is 24 hours. Anonymize IP Optimizely typically stores the client IP address for each request. Values are true or false. If this flag is set to true, the last octet of the IP address is truncated before it is stored. If set to false, the entire IP address is stored. Most relevant for consumers of this API that are implemented in a web browser or mobile client context and are subject to policies or regulations restricting the storage of end-user identifying information. This flag is independent of the IP anonymization setting in the Account and Project settings, which only controls how Optimizely clients set this flag. If this flag is set, care must be taken when using the IP filtering features, as fully-qualified explicit IP addresses will not function as filters (anonymization occurs before events are filtered by IP). Client Name Recommended for debugging purposes. A unique identifier for the system that generated this event. By convention, should be similar to the following example: organization_name/system_name For a complete description of the Event API, see the Event API reference. Client Version Recommended for debugging purposes. A version identifier for the system that generated this event. Project ID Optional. The Project ID needs only to be passed if you are using the Recommendations product. ... View more

This article describes how to set up the ReferralCandy connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Signup Advocate ✓ ✓ Invite Advocate ✓ ✓ Register a Purchase ✗ ✓ Update Status of Referred Purchase ✗ ✓ Unsubscribe an Advocate ✓ ✓ Resubscribe an Advocate ✓ ✓ 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 Access ID Your API access ID can be found in the "API Tokens" section of your profile page at https://my.referralcandy.com/settings. API Secret Key Your API secret key can be found in the "API Tokens" section of your profile page at   https://my.referralcandy.com/settings. 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 - Signup Advocate Parameters Parameter Description Email Address Advocate's email address. For information on this endpoint, see: https://www.referralcandy.com/api#signup. First Name Advocate's first name. Last Name Advocate's last name. Action - Invite Advocate Parameters Parameter Description Email Address Email address to send the invite to. For information on this endpoint, see: https://www.referralcandy.com/api#invite. Action - Register a Purchase Parameters Parameter Description Email Address Customer's email address. For information on this endpoint, see: https://www.referralcandy.com/api#purchase. First Name Customer's first name. Last Name Customer's last name Customer's Language Customer's preferred language. Defaults to campaign's default language if it is not set or not available to the campaign. Possible values: en, fr, de, es, it, ja, nl, ru, zh-CN, zh-HK, zh-TW, da, no, sv, pt-BR. Discount Code Discount code used in the order. Accepts Marketing Whether the customer-opted in to marketing. Possible values: true or false. Defaults to true. Order Timestamp Unix timestamp of order. If not provided, current Unix timestamp will be used. Browser IP IP address of customer when making the purchase. User Agent User agent string of the customer's web browser. Invoice Amount Total invoice amount for this purchase. Currency Code ISO 4217 currency code used in order invoice (for example: USD, GBP, INR). External Reference ID An ID that can be used to track this purchase externally. Action - Update Status of Referred Purchase Parameters Parameter Description Customer Email Email address of customer who made the referred purchase. For information on this endpoint, see: https://www.referralcandy.com/api#referral. Notify Referring Customer Whether to notify customer who referred customer specified above that the referral has been disregarded. Potential values: true or false. Defaults to true. Returned Purchase Whether the customer has returned his/her purchase. Potential values: true or false. If set to true, the referral will be disregarded and rewards will not be paid out. Action - Unsubscribe an Advocate Parameters Parameter Description Email Address Contact's email address. For more information on this endpoint, see: https://www.referralcandy.com/api#unsubscribed. Action - Resubscribe an Advocate Parameters Parameter Description Email Address Contact's email address. For more information on this endpoint, see: https://www.referralcandy.com/api#unsubscribed. ... View more

This article describes how to set up the Ambassador connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Record Campaign Referral Event ✓ ✓ Update Ambassador ✓ ✓ Add Ambassador Commission ✓ ✓ Remove Contact ✓ ✓ 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: Username: For information on how to find your username, see: https ://docs. getambassador .com/docs/authentication API Key For information on how to find your API key, see:   https ://docs. getambassador .com/docs/authentication 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 - Record Campaign Referral Event Parameters Parameter Description Email Address Your customer's email address. For more information on this endpoint, see: https://docs.getambassador.com/v2.0.0/reference#eventrecord. Campaign UID Your campaign's ID. Required if product ID is not used. Product ID Your product ID, which is assigned to one of your campaigns. Can be used instead of Campaign UID. Required if Campaign UID is not used. Short Code Referrer's "mbsy" shortcode, required for initial commissions. Revenue Revenue amount of the event. Default value is 0. Transaction UID Unique transaction ID for the event. IP Address Customer's IP address. Customer UID Your customer's internal unique ID. First Name Your customer's first name. Last Name Your customer's last name. Custom Field 1 Custom field. Related to ambassador. Custom Field 2 Custom field. Related to ambassador. Custom Field 3 Custom field. Related to ambassador. Email New Ambassador Email login credentials to new ambassadors (1=yes, 0=no). Default value is 1. Deactivate New Ambassador New ambassadors created are deactivated (1=yes, 0=no). Default value is 0. Auto Create Customer If the customer is not an ambassador, create them (1=yes, 0=no). Default value is 0 if you signed up for Ambassador after Nov 5 2013, otherwise default value is 1. Add to Group ID Define which group(s) new ambassadors will be created in. Using this parameter will override default group settings. Group IDs should be separated by commas. If add_to_group_id = -1 , then ambassador will not be added to any group. Event Data 1 Custom field. Related to the event. Event Data 2 Custom field. Related to the event. Event Data 3 Custom field. Related to the event. Commission is Approved Commission status (1=approved, 0=pending). Entering a value will override the campaign's auto approve setting; otherwise, the campaign's setting will be used if not provided. Street Your customer's street. City Your customer's city. State Your customer's state. Postal Code Your customer's postal code. Country Your customer's country. Phone Your customer's phone number. Action - Update Ambassador Parameters Parameter Description UID Your ambassador's internal unique ID. Required if email is not provided. If both UID and email are provided, UID will take precedence. For more information on this endpoint, see: https://docs.getambassador.com/v2.0.0/reference#ambassadorupdate. Email Address Your ambassador's email address. Required if UID not provided. If both email and UID are provided, UID will take precedence. New Email Address New email address for the ambassador. New UID New UID for the ambassador. First Name New first name for the ambassador. Last Name New last name for the ambassador. Custom Field 1 New value for custom field 1. Custom Field 2 New value for custom field 2. Custom Field 3 New value for custom field 3. Deactivate Ambassador 1=deactivate ambassador. 0=activate ambassador. Default value is 0. Deactivation will change the ambassador's status to 'Banned'. Send Welcome Email (1=yes, 0=no). Street New street for the ambassador. City New city for the ambassador. State New state for the ambassador. Postal Code New postal code for the ambassador. Country New country for the ambassador. Phone New phone for the ambassador. Paypal Email New PayPal email address for the ambassador. Company New company name for the ambassador. Set Groups Define which group(s) existing ambassadors will be put in. Using this parameter will override default group settings and an ambassador's current groups. Group IDs should be separated by commas. Action - Add Ambassador Commission Parameters Parameter Description UID Your ambassador's internal unique ID. Required if email address is not used. If both are present, UID takes precedence. For information on this endpoint, see: https://docs.getambassador.com/v2.0.0/reference#commissionadd. Ambassador Email Your ambassador's email address. Required if UID not used. If both are present, UID takes precedence. Campaign UID Your campaign's ID. Commission Amount Amount of commission. Customer Email Your customer's email address. First Name Your customer's first name. Last Name Your customer's last name. Revenue Amount Amount of revenue. Transaction UID Unique transaction ID for commission. Referrer UID Your referrer's internal unique ID. Customer UID Your customer's internal unique ID. Commission is Approved 1=approved commission, 0=pending commission. Email New Ambassador Email login credentials to new ambassadors (1=yes, 0=no). Deactivate New Ambassador New ambassadors create are deactivated (1=yes, 0=no). Event Data 1 Custom field. Related to event/commission. Event Data 2 Custom field. Related to event/commission. Event Data 3 Custom field. Related to event/commission. Action - Remove Contact Parameters Parameter Description Email Address Email address of the contact to remove. For information on this endpoint, see: https://docs.getambassador.com/v2.0.0/reference#complianceremove. ... View more

This article describes how to set up the Friendbuy connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Email Opt Out ✓ ✓ Send Email ✓ ✓ Post a Purchase ✗ ✓ 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 Access Key For information on how to get your API Access Key, see: Developer Docs: Security. API Secret Key For information on how to get your API Secret Key, see:  Developer Docs: Security. 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 - Email Opt Out Parameters Parameter Description Email Address Email address to add to opt-out list. Only single email addresses allowed. For more information on this endpoint, see: https://developers.friendbuy.com/#span-class-method-post-post-span-span-class-restofendpoint-opt_outs-emails-span. Action - Send Email Parameters Parameter Description Email Address Where to send the email. Only single email addresses allowed. For more information on this endpoint, see: https://developers.friendbuy.com/#span-class-method-post-post-span-span-class-restofendpoint-communication_emails-span. Email Template ID ID of communication email template to be used. Coupon Bank ID ID of coupon bank to be used. Action - Post a Purchase Parameters Parameter Description Order ID Unique order ID for the purchase. If this order ID has been previously used, the request will fail and no new purchase (and no new conversion) will be created. For more information on this endpoint, see: https://developers.friendbuy.com/#span-class-method-post-post-span-span-class-restofendpoint-purchases-span. Referral Code Refcode that referred the friend to make the purchase. Required unless Coupon Code is present. If both Referral Code and Coupon Code are provided, Referral Code will take precedence. Coupon Code Coupon code that brought the friend to the merchant to make the purchase. Required unless Referral Code is present. Order Amount Amount of the order. Order Email Email address associated with the order. New Customer Whether or not the purchase is made by a new (first-time) customer. Possible values: true or false. Used to check for reward eligibility, since Friendbuy allows merchants to state “must be a new customer” as one of the reward criteria. Customer ID The ID you assigned to your customer (not the same as the internal Friendbuy-assigned ID). Customer First Name   Customer Last Name   Customer Email Email address associated with the customer. Stripe Customer ID Stripe’s ID for the customer. Chargebee Customer ID Chargebee’s ID for the customer ... View more

This article describes how to set up the SparkPost connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add or Update a Suppression ✓ ✓ Send Email ✓ ✓ 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 Endpoint To find your SparkPost API endpoint, please see the 'Endpoint' section at https://developers.sparkpost.com/api. Please include 'https://' at the beginning of your API endpoint. API Key For information on where to find your SparkPost API keys, visit: https://app.sparkpost.com/account/api-keys. 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 - Add or Update a Suppression Parameters Parameter Description Email Address Email address of the user. For more information on this endpoint, visit: https://developers.sparkpost.com/api/suppression-list/#suppression-list-put-create-or-update-a-suppression. Suppression Record Type Possible Values: transactional or non_transactional . Description Explanation for the suppression. Action - Send Email Parameters Parameter Description Recipient Email Address Valid recipient email address. Only single values allowed. For more information on this endpoint, visit: https://developers.sparkpost.com/api/transmissions/#transmissions-post-send-a-template. Template ID ID of the email template to use. Recipient Name Name attached to the recipient email address. Campaign ID Name of the campaign. Maximum length: 64 bytes. Description Description of the transmission. Maximum length: 1024 bytes. Substitution Data Key-value pairs that are provided to the Sparkpost Template Engine. For more information on the Sparkpost Template Engine/Language, see: https://developers.sparkpost.com/api/template-language/. Transmission Metadata Key-value pairs associated with a transmission (email send). Metadata is provided to the Sparkpost Template Engine. A maximum of 1000 bytes of merged metadata (Transmission Metadata + Recipient Metadata) is available with Recipient Metadata taking precedence over Transmission Metadata when there are conflicts. For more information on the Sparkpost Template Engine/Language, see: https://developers.sparkpost.com/api/template-language. Recipient Metadata Key-value pairs associated with a recipient. Metadata is provided to the Sparkpost Template Engine. A maximum of 1000 bytes of merged metadata (Transmission Metadata + Recipient Metadata) is available with Recipient Metadata taking precedence over Transmission Metadata when there are conflicts. For more information on the Sparkpost Template Engine/Language, see: https://developers.sparkpost.com/api/template-language. Return Path Email address to use for envelope FROM. The domain of the Return Path address must be a CNAME-verified sending domain. For non-enterprise accounts, the local part of the Return Path address will be overwritten by SparkPost. For Enterprise accounts, the Return Path may be any valid email address and the local part in the Return Path will not be overwritten by SparkPost. Header To Email address to display in the 'To' header (instead of Recipient Email Address). Use Draft Template Whether to use the draft version. If this is set to true and no draft exists, the email will fail. Default value is false. Potential values: true or false. Tags Single value or array of text labels associated with a recipient. Maximum number of tags: 10 per recipient, 100 system wide. Any tags over the limits are ignored. ... View more

Tableau is an advanced data visualization platform. This article describes how to connect Tableau to the Tealium DataAccess solution. In this article: Table of Contents Placeholder Prerequisites Basic knowledge of Tableau Be sure to install the appropriate drivers from the Tableau website at http://www.tableau.com/support/drivers dsfds. To install, click Amazon Redshift and follow the directions on the screen. Tealium has a partnership with Tableau but is not a reseller. Ensure that you obtain the proper Tableau licensing before attempting to use the product. If you need assistance, contact your Account Manager to initiate and facilitate support. Connecting to Redshift This section describes how to add a new data soure and connect to Amazon Redshift. Use the following steps to connect to Amazon Redshift: Add a new data source. Enter your Redshift Credentials. Ensure that you require Secure Sockets Layer (SSL). Select a schema. Select the schema that most closely resembles your account and profile. For example, if your account is tealium and your profile is dataaccess your schema will be tealium__dataaccess . Select one or more tables. Tables and views for your account are listed in the Tables section. Select the tables that you want to analyze in Tableau. At this point, you can optionally join multiple tables if you know which fields relate the tables together. During this process, you will have to tell Tableau which field in the “left” table is related to the field in the “right” table and the enter the type of join that you want to create between the two tables (left, right, inner, or full outer). For additional information, see: Tableau: Joining Tables To start using the data, create a new sheet or select an existing sheet. AudienceDB Example In the following example, the keys used to join two (2) tables together are as follows:   visits_view.“visit - visitor id”  =  visitors_view_normalized.“visitor - id” Preparing Data for Analysis When using a new data source, organize the fields prior to creating any reports, as described in the following suggestions: Dimensions and Measures By default, most (or all) fields are imported as “dimensions”, or fields that you want to slice your data by. If you intend to use a field as metric that you can summarize, convert these fields from “dimensions” to “measures”. This often includes fields such as Order Total, Total Units, etc. Custom Measures EventDB is event-level data; therefore you will often want to count how often an event (row or record) contains a field with a specific value. An example is a custom measure of “Unique Visitors”. This is accomplished by creating a new calculated field using calculation shown in the following example. In this instance, it will count the unique number of times that a specific visitor ID appeared in the data:   COUNTD([Event - Visitor Id]) Examples of Custom Calculations The following list provides examples of other custom calculations you may want to use: Total Events (Measure)   COUNTD([Event - Id]) Mac+Chrome Revenue (Measure) IF FIND([Event - User Agent],"Chrome") > 0 AND FIND([Event - User Agent],"Mac") > 0 THEN [Event - Udo - Order Subtotal] END Unique Orders COUNTD([Event - Udo - Order Id]) High Value Orders COUNTD(IF [Event - Udo - Order Subtotal] > 500 THEN [Event - Udo - Order Id] END) While there are several default fields in EventDB, most of the other fields are unique to each customer database and based on what is configured in Tealium IQ. You can create custom calculations using any combination of default or custom fields in EventDB. Troubleshooting Unable to connect to RedShift due to a password issue Check that your password does not contain any of the following disallowed characters: Plus sign ( + ) At symbol ( @ ) Right or left curly brackets (  {,  } ) Right parenthesis (  ) ) Semicolon ( ; ) An error message occurs when attempting to connect to any Tableau Server page The Tableau server gateway port (Default = 80) is likely blocked by something outside of the Tableau Server, such as a proxy or firewall. As a result, the response from Tableau server does not reach the user. If you receive this message, it is likely that one of the following has occurred: The connection was reset. The connection to the server was reset while the page was loading. The site is temporarily unavailable or too busy, try again in a few moments. If you cannot load any pages, check your computer's network connection. If your computer or network is protected by a firewall or proxy, ensure that your browser is permitted to access the web. To resolve this issue, work with your IT team to unlock the port used as the gateway port on the Tableau server. Resources Tableau Knowledge Base Contains detailed information about commonly asked questions and best practices. Connecting Tableau to an Amazon RedShift Data Source This article describes how to connect Tableau to an Amazon Redshift database and set up the data source. ... View more

This article describes how to set up the Intercom connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Create or Update User ✓ ✓ Add Tag Based on ID ✓ ✗ Add Tag Based on User ID ✓ ✗ Add Tag Based on Email ✓ ✗ 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: Access Token: Access Tokens use the bearer authorization header when you make a request. For more information about creating an access token, see Authorization: Access Tokens. 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 - Create or Update User Parameters Parameter Description User ID A unique string identifier for the user. It is required on creation if an email is not supplied *Either User ID or Email must be supplied Reference the following API documentation for more info Email The user's email address. It is required on creation if a user_id is not supplied *Either User ID or Email must be supplied Phone Number The user's phone number ID The ID may be used for user updates Signed Up At The time the user signed up Name The user's full name Last Seen IP An IP address (e.g. "1.2.3.4") representing the last IP address the user visited from your application form. (Used for updating location data) Last Seen User Agent The user agent the user last visited your application with Last Request At A UNIX timestamp (in seconds) representing the date the user last visited your application Unsubscribed From Emails A Boolean value representing the users unsubscribed status Default value if not sent is false Update Last Request At A Boolean value, which if true, instructs Intercom to update the users' last_request_at value to the current API service time in UTC Default value if not sent is false New Session A Boolean value, which if true, instructs Intercom to register the request as a session Action - Add Tag Based on ID Parameters Parameter Description Name Name of the tag. For more information on this endpoint, visit: Tag or Untag Users Reference ID ID of the user. Untag To untag a company or user, each user or company object sent in the tagging request can be submitted with an untag field whose value is set to true. Setting the untagvalue to false is the same as requesting the object be tagged. Action - Add Tag Based on User ID Parameters Parameter Description Name Name of the tag. For more information on this endpoint, visit: Tag or Untag Users Reference User ID The User ID of the user Untag To untag a company or user, each user or company object sent in the tagging request can be submitted with an untag field whose value is set to true. Setting the untagvalue to false is the same as requesting the object be tagged. Action - Add Tag Based on Email Parameters Parameter Description Name The name of the tag. For more information on this endpoint, visit: Tag or Untag Users Reference Email Email of the user Untag To untag a company or user, each user or company object sent in the tagging request can be submitted with an untag field whose value is set to true. Setting the untagvalue to false is the same as requesting the object be tagged. ... View more

View the Release Notes summary to learn about updated product features, enhancements, and fixes. To view details about how to use a new feature, click the Learn More link next to the description. Tags New/Cool Stuff New marketplace tag: Fit Analytics New marketplace tag: Sidecar Updated Adobe Target tag to version 1.6.2. (Learn more) Updated the Urban Airship tag template with latest vendor code. Updated Yieldify tag to the latest version. Fixes Corrected issue with the Fullstory tag requiring an update of the event API call. Renamed Delacon SVG logo file to logo_delacon_calltracking.svg to correct 404   error on tealium.com/integrations. Updated Adform tag template base URL  to a1.adform.net. Updated Google Analytics (gtag.js) to add routing support. (Learn more) Connectors New/Cool Stuff New marketplace connector: dotmailer. Deprecated previous dotmailer connector and replaced with this quick connector. (Learn more) New marketplace connector: Intercom. Deprecated previous Intercom connector and replaced with this quick connector. (Learn more) New marketplace connector: Webhook OAuth2 2-Legged (Learn more) New marketplace connector: Webtrekk (Learn more) Added logic to Mixpanel connector to filter out empty values. (Learn more) Enabled Event Stream support for the following AudienceStream Connectors: Optimizely Dynamic Customer Profile (DCP), Centro DSP, DataXu, TheTradeDesk, SalesForce DMP, DoubleClick for Publishers (DFP), DoubleClick Bid Manager, and AppNexus. Enhanced the "Merge Visitor into List" action for the Responsys connector to support merge status rules. ( Learn more ) Renamed Blue Kai connector to Blue Kai Mobile. (Learn more) Fixes Deprecated Google AdWords Customer Match connector until batching support is fully implemented. Universal Data Hub New/Cool Stuff Updated Publish dialog to be asynchronous to allow users to close the window during the publishing process. Fixes Corrected issue causing unpredictable results and profile problems when deleting attributes with dependent rules. Stitched Visitor Count and Badges/Audiences to correct sorting issues with numbers more than 1000 in Visitor Profile Sampler. iQ Tag Management New/Cool Stuff Added the tag status checker to the Tags tab in the user interface for convenience and ease of use when evaluating the status of all your tags on a given screen. (Learn more) The tags view in the user interface now display a list of related extensions for a better overview of the tag. (Learn more) Updated the CSS for Consent Manager and Preferences with a more responsive design. (Learn more) Updated the user interface for the JavaScript Code extension. (Learn more) Installations Fixes Updated Tealium for iOS to protect volatile data from being accessed by multiple threads. Corrected Android device integrations issue by updating the Last Event on Pause to prevent registering a crash on startup. ... View more

This article describes how to set up the DoubleClick for Publishers (DFP) connector in your Customer Data Hub account. In this article: Connector Actions Action Name AudienceStream EventStream Add Visitor to User-List or Segment ✓ ✓ Remove Visitor from User-List or Segment ✓ ✓ 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. When you add this connector you are prompted to accept the vendor's data platform policy. After adding the connector, configure the following settings: Client Customer ID Required Your (DoubleClick Customer) Identifier in the selected Product. Create a New Segment Use the following steps to create a new segment in AudienceStream: Click Create a New Segment from the top of the Actions selection drop-down screen. Enter the Segment Name, Segment Member Lifespan, Integration Code, and Segment Description. Click Create Segment. The Integration Code is an ID used by user list sellers to correlate IDs on their systems. If no ID is available, you can manually enter a random number between 1 and 1000. Confirmation displays in the form of a check mark next to the Create Segment button to verify that the segment has been created. 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 - Add Visitor to User-List or Segment Parameters Parameter Description Select the Target User-list/Segment Required User map identifier. Specifies the user that this operation applies to. This is the target User-list/Segment where the user will be added to. Google User ID Google User ID Provided by the ADX cookie-matching service. iOS Advertising ID iOS Advertising ID Android Advertising ID Android Advertising ID RIDA Roku ID AFAI Amazon Fire TV ID MSAI XBOX/Microsoft ID Data Source ID Optional An ID indicating the data source that contributed this membership. Required to be in the range of 1 to 1,000. Any ID greater than 1,000 results in a BAD_DATA_SOURCE_ID error. These IDs do not have reference or meaning for Google and are only used as labels for reporting purposes. Action - Remove Visitor from User-List or Segment Parameters Parameter Description Select the Target User-list/Segment Required, this is the target User-list/Segment where the user will be removed from. Google User ID Google User ID Provided by the ADX cookie-matching service. iOS Advertising ID iOS Advertising ID Android Advertising ID Android Advertising ID RIDA Roku ID AFAI Amazon Fire TV ID MSAI XBOX/Microsoft ID Data Source ID Optional An ID indicating the data source that contributed this membership. Required to be in the range of 1 to 1,000. Any ID greater than 1,000 results in a BAD_DATA_SOURCE_ID error. These IDs do not have reference or meaning for Google and are only used as labels for reporting purposes. ... View more

This article describes how to set up the DoubleClick for Ad Exchange connector in your Customer Data Hub account. In this article: Connector Actions Action Name AudienceStream EventStream Add Visitor to User-List or Segment ✓ ✓ Remove Visitor from User-List or Segment ✓ ✓ 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. When you add this connector you are prompted to accept the vendor's data platform policy. After adding the connector, configure the following settings: Client Customer ID (Required) Your (DoubleClick Customer) Identifier in the selected product. Select the Target Product (Required) The target product, either DoubleClick AdExhchange - Buyer or DoubleClick AdExchange - Publisher. Create a New Segment Use the following steps to create a new segment in AudienceStream: Click Create a New Segment from the top of the Actions selection drop-down screen. Enter the Segment Name, Segment Member Lifespan, Integration Code, and Segment Description. Click Create Segment. The Integration Code is an ID used by user list sellers to correlate IDs on their systems. If no ID is available, you can manually enter a random number between 1 and 1000. Confirmation displays in the form of a check mark next to the Create Segment button to verify that the segment has been created. 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 - Add Visitor to User-List or Segment Parameters Parameter Description Select the Target User-list/Segment Required User map identifier. Specifies the user that this operation applies to. This is the target User-list/Segment where the user will be added to. Google User ID Google User ID Provided by the ADX cookie-matching service. iOS Advertising ID iOS Advertising ID Android Advertising ID Android Advertising ID RIDA Roku ID AFAI Amazon Fire TV ID MSAI XBOX/Microsoft ID Data Source ID Optional An ID indicating the data source that contributed this membership. Required to be in the range of 1 to 1,000. Any ID greater than 1,000 results in a BAD_DATA_SOURCE_ID error. These IDs do not have reference or meaning for Google and are only used as labels for reporting purposes. Action - Remove Visitor from User-List or Segment Parameters Parameter Description Select the Target User-list/Segment Required, this is the target User-list/Segment where the user will be removed from. Google User ID Google User ID Provided by the ADX cookie-matching service. iOS Advertising ID iOS Advertising ID Android Advertising ID Android Advertising ID RIDA Roku ID AFAI Amazon Fire TV ID MSAI XBOX/Microsoft ID Data Source ID Optional An ID indicating the data source that contributed this membership. Required to be in the range of 1 to 1,000. Any ID greater than 1,000 results in a BAD_DATA_SOURCE_ID error. These IDs do not have reference or meaning for Google and are only used as labels for reporting purposes. ... View more

Using DataXu Audience Ingestion APIs are designed send audience data into the DataXu platform. This article describes how to set up the DataXu Audiences connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add User to Segment(s) ✓ ✓ 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: 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 - Add User to Segment(s) Parameters Parameter Description Endpoint URL Optional When provided it will override the default endpoint Default endpoint is http://s2s-v2.w55c.net/s2s-servlet Segment(s) List/Array/Set of segment ids to which the user should be added. These segment ids can be either DataXu’s segment identifier (i.e. pixel id or segment uid) or the data partner’s segment identifier. Only Customer Data Hub Array/List/Set types are supported for all attributes configured in this section. i.e. only pick such data type as the value. Alias Type Represents kind of alias (API key of "alias_type") DataXu accepts the following alias types: DX GOOGLE_AD_ID SHA1_GOOGLE_AD_ID MD5_GOOGLE_AD_ID IDFA SHA1_IDFA MD5_IDFA ANDROID_ID SHA1_ANDROID_ID MD5_ANDROID_ID Alias ID Represents the actual identifier for the user (API key of "alias_id") and the specified "Alias Type" Timestamp Represents the time of the user’s addition to the audience (API key of "timestamp") Optional and preferably in UTC. example: 2016-12-01T15:16:33Z    ... View more

The Tealium Xamarin integration provides a set of cross-platform interfaces and configuration classes that interface with the native Tealium iOS and Android SDKs to simplify Tealium tracking Xamarin developers. In this article: Table of Contents Placeholder Overview The Tealium Xamarin integration provides a set of cross-platform interfaces and configuration classes that interface with our native iOS and Android SDKs to make Tealium tracking more straightforward for Xamarin developers. DLLs and Lifecycle Modules Dynamic-Link Libraries (DLLs)  described in this article are available at: https://github.com/Tealium/tealium-xamarin. Available DLLs Several DLLs are available for the Xamarin integration: Tealium.Common.dll This DLL contains cross-platform code, interfaces, and common code to be used in all projects within your Xamarin application. Add this DLL as a reference in both shared project and platform-specific projects. Abstraction DLLs Abstraction DLLS are included to create an easy-to-use C# API wrapper for the native Tealium SDKs and should only be referenced in platform-specific projects. These libraries contain platform-specific, concrete class implementations for the interfaces and abstract classes provided by the Tealium common library. You can code all of your cross-platform logic against the common library. Tealium.Droid.dll –  for Android mobile platforms Tealium.iOS.dll  –  for Apple mobile platforms There are DLLs specific to each mobile platform which are referenced by the abstraction DLLs. The platform DLLs are binding libraries and therefore embed our the native SDKs - they provide auto-generated wrapper code that would allow you to interact with our native SDKs directly and as a result they can be used standalone if desired. Tealium.Platform.Droid.dll Tealium.Platform.iOS.dll Binding libraries can be used by themselves. The fact that they are automatically generated results in vastly different namespaces for each platform, which adds an extra complication to development efforts. It is advised to make use of the Common and platform-specific abstraction libraries  instead. Lifecycle Modules An optional lifecycle module is available by referencing the relevant DLL for the platform. These are binding libraries for the native equivalent SDKs: Tealium.Platform.Lifecycle.Droid.dll Tealium.Platform.Lifecycle.iOS.dll Android Shared Project Example The following example illustrates the Shared project and Android platform-specific project from a typical Xamarin based app: As shown in the example, the Shared Project references only the Tealium.Common.dll library, whereas the Android-specific project references all of the following: Tealium.Common.dll Tealium.Droid.dll Tealium.Platform.Droid.dll Tealium.Platform.Lifecycle.Droid.dll Basic Configuration The first step for initialization is to ensure that your projects reference the appropriate libraries as described in the Overview. Though not required, Tealium recommends using the TealiumInstanceManager classes provided as they provide out-of-the-box, thread-safe Tealium instance management. Android Example The following example applies to an Android project: using Tealium.Droid; //... ITealiumInstanceManager instanceManager = new TealiumInstanceManager(new TealiumInstanceFactoryDroid(<myAndroidApplication>)); //Optional Lifecycle Module enablement - ensure to reference Tealium.Platform.Lifecycle.Droid.dll TealiumLifecycleManager.SetLifecycleAutoTracking = TealiumDroid.Lifecycle.TealiumLifecycleControlDelegation.SetLifecycleAutoTracking; iOS Example The following example applies to an Apple project: using Tealium.iOS; //... ITealiumInstanceManager instanceManager = new TealiumInstanceManager(new TealiumInstanceFactoryIOS()); //Optional Lifecycle Module enablement - ensure to reference Tealium.Platform.Lifecycle.iOS.dll TealiumLifecycleManager.SetLifecycleAutoTracking = TealiumIOS.Lifecycle.TealiumLifecycleControlDelegation.SetLifecycleAutoTracking; Creating Instances Once the TealiumInstanceManager is created, you can begin creating Tealium instances as with the native SDKs. The TealiumInstanceManager is a multiton pattern that provides access to multiple named instances if you need to track data on more than a Tealium profile. Use the following steps to create a new instance: Create a TealiumConfig object to hold various required and optional configuration items, as shown in the following example: TealiumConfig tealConfig = new TealiumConfig("TEALIUM_INSTANCE",//Instance Name "tealiummobile",//Tealium Account Name "demo",//Tealium Profile Name "dev",//Tealium Envrionment true);//Optional Auto Lifecycle AutoTracking (default: true) When complete, you can then can use your TealiumInstanceManager to create a Tealium instance which can be used to track your events, as shown in the following example: ITealium tealium = instanceManager . CreateInstance (tealC onfig ); Advanced Configuration The TealiumConfig class has constructor options that allow you to specify optional parameters to enable or disable the more advanced aspects of the Tealium Mobile SDKs. These parameters are optional as not all customers require these features. Remote Commands An object containing RemoteCommand blocks if you need to work with the features provided by the TagBridge tag. Similarly, you can supply code for the delegated methods that you can use in the native versions of the SDKs as well, such as Remote Commands. While the majority of the events within mobile are either sent to our data collection servers to be actioned through connectors, or processed in the tag management web view to trigger vendor tags. Remote Commands provide additional flexibility in that events used for tag management can pass data back to your native code through the IRemoteCommand interface. The following sample code prints out the CommandId (set to TealiumConsts.REMOTE_COMMAND_ID ). Using this example, you will also have access to a full payload of data, as configured in the associated TagBridge Custom Command tag required to set this up: static List<IRemoteCommand> SetupRemoteCommands() { var command = new DelegateRemoteCommand(TealiumConsts.REMOTE_COMMAND_ID, "Test command " + TealiumConsts.REMOTE_COMMAND_ID) { HandleResponseDelegate = (DelegateRemoteCommand cmd, IRemoteCommandResponse resp) => { System.Diagnostics.Debug.WriteLine($"Handling command {cmd.CommandId}..."); } }; return new List<IRemoteCommand>() { command }; } Delegate Methods There are five delegated methods that allow you to inject code into the processing logic within the Tealium SDK: DelegateDispatchValidator Provides two delegate methods  where the Boolean return value determines whether or not an existing dispatch should be dropped or queued. This is useful if you have steps within your app where you know that the user may be offline or you specifically want to write your own batching logic for example. ShouldDropDispatchDelegate ShouldQueueDispatchDelegate DispatchSentDelegateEventListener Called whenever a dispatch has been sent. DispatchQueuedDelegateEventListener Called whenever a dispatch has been queued. WebViewReadyDelegateEventListener Called when the WebView is fully loaded and ready, if you are using the Tag Management module. SettingsPublishedDelegateEventListener Executed when there has been an updated set of publish settings retrieved. The following example illustrates the usage of the delegate method: static TealiumAdvancedConfig SetupAdvancedConfig() { DelegateDispatchValidator validator = new DelegateDispatchValidator() { ShouldDropDispatchDelegate = (ITealium arg1, IDispatch arg2) => { System.Diagnostics.Debug.WriteLine("Inside ShouldDropDispatchDelegate!"); return false; }, ShouldQueueDispatchDelegate = (ITealium arg1, IDispatch arg2, bool shouldQueue) => { System.Diagnostics.Debug.WriteLine("Inside ShouldQueueDispatchDelegate!"); return shouldQueue; } }; DispatchSentDelegateEventListener sendingListener = new DispatchSentDelegateEventListener() { DispatchSent = (tealium, dispatch) => { System.Diagnostics.Debug.WriteLine("Inside DispatchSent!"); dispatch.PutString("KeyAddedBySendListener", "Value added by sending listener."); } }; DispatchQueuedDelegateEventListener queuingListener = new DispatchQueuedDelegateEventListener() { DispatchQueued = (tealium, dispatch) => { System.Diagnostics.Debug.WriteLine("Inside DispatchQueued!"); dispatch.PutString("KeyAddedByQueuedListener", "Value added by queuing listener."); } }; WebViewReadyDelegateEventListener webViewListener = new WebViewReadyDelegateEventListener() { WebViewReady = (tealium, webView) => { System.Diagnostics.Debug.WriteLine("Inside WebViewReady!"); } }; SettingsPublishedDelegateEventListener settingsListener = new SettingsPublishedDelegateEventListener() { SettingsPublished = (tealium) => { System.Diagnostics.Debug.WriteLine("Inside SettingsPublished!"); } }; TealiumAdvancedConfig advConfig = new TealiumAdvancedConfig(validator, sendingListener, queuingListener, webViewListener, settingsListener); return advConfig; } Tracking To trigger specific events within your app, use the appropriate method for the type of event that you want to track, as shown in the following sections. Screen View Tracking The following example uses screen view tracking: // Get ITealium instance ITealium tealium = instanceManager . GetExistingInstance ( TealiumConsts . INSTANCE_ID ); // Track a Page View event with the title "View Name" but no extra event data. tealium . TrackView ( " View Name " ); // Track a Page View event with the title "View Name" along with the "page_type" event daata. tealium . TrackView ( " View Name " , new Dictionary < String , object >( 1 ){ { " page_type " , " product detail page " } }); // Track a Page View event with the title "View Name" along with a single piece of event data. // This an equivalent way to the track call directly above. tealium . TrackView ( " View Name " , " page_type " , " product detail page " ); Event Tracking The following example uses event tracking: // Get ITealium instance ITealium tealium = instanceManager.GetExistingInstance(TealiumConsts.INSTANCE_ID); // The TrackEvent method has the same overloads as TrackView, so only one additional example is provided. // Track an Event with three pieces of specific Event Data. tealium.TrackEvent("Event Name", new Dictionary<String, object>(3){ {"event_category", "Menu"}, {"event_action", "Button Click"}, {"event_label", "Logo"} }); Adding Event Data As with the native SDKs, there are two additional types of variables that you can set to be added to each of your events. Persistent Data Persistent data will be merged into your event-specific data dictionary on every event that you trigger, as well as persist between launches, as shown in the following example: //Get ITealium instance ITealium tealium = instanceManager.GetExistingInstance(TealiumConsts.INSTANCE_ID); tealium.AddPersistentDataSources(new Dictionary<string, object>(1) { //Data will be merged into every event. { "PersistentDataTest", "Example persistent value." } }); Volatile Data Volatile data will be merged into your event-specific data dictionary on every event, just like persistent data. The key difference is that once the application is closed, volatile data is lost and will not be present on the next launch. //Get ITealium instance ITealium tealium = instanceManager.GetExistingInstance(TealiumConsts.INSTANCE_ID); tealium . AddVolatileDataSources ( new Dictionary < string , object >( 1 ) { //Data will be merged into every event. { " VolatileDataTest " , " Example volatile value. " } }); Consent Management The Consent Management feature comes from the two native SDKs embedded into the DLLs named Tealium.Platform.*.dlls . The Tealium.Common.dll provides the following category and status enums to use: Tealium.ConsentManager.ConsentStatus Tealium.ConsentManager.ConsentCategory Enabling Consent Management To enable Consent Management, simply pass the optional parameter in the constructor of TealiumConfig or set it as a property, as shown in the following example: TealiumConfig tealC onfig = new TealiumConfig ( TealiumConsts . INSTANCE_ID , TealiumConsts . ACCOUNT_NAME , TealiumConsts . PROFILE_NAME , TealiumConsts . ENVIRONMENT , true , commands , advConfig , false ); //optional Consent Manager Enablement. //or subsequently enable it: tealConfig . IsConsentManagerEnabled = true ; //then initialise your Tealium Instance: var tealium = instanceManager . CreateInstance (tealC onfig ); Overriding Initial Consent Status As with the native SDKs for both Android and iOS, when Consent Management is enabled, new users are assumed to be in an Unknown state. Tracking requests are queued up until the consent status has been opted-in or out, at which point events will be sent or purged, respectively. You can override the initial status through properties on the TealiumConfig object, as shown in the following example: // enable Consent Manager: tealConfig . IsConsentManagerEnabled = true ; // Set Users to be Consented by default: tealConfig. InitialUserConsentStatus = ConsentManager . ConsentStatus . Consented ; // Or set Users to be Not Consented by default: tealConfig. InitialUserConsentStatus = ConsentManager . ConsentStatus . NotConsented ; // Opt users into All Categories tealConfig. InitialUserConsentCategories = ConsentManager . AllCategories ; // or none: tealConfig. InitialUserConsentCategories = ConsentManager . NoCategories ; // or partial opt-in, only to Analytics and Mobile categories. tealConfig. InitialUserConsentCategories = new ConsentCategory []{ ConsentManager . ConsentCategory . Analytics , ConsentManager . ConsentCategory . Mobile }; Updating the User Consent Selection The ConsentManager can be interacted with directly from the Tealium instance, through the ConsentManager property. If you need to update a user's consent selection, simply pass the relevant values. Only the enum values available in the ConsentManager.ConsentCategory and ConsentManager.ConsentStatus should be used, as shown in the following example: // if the user is in an Unknown state, then the following code would trigger any queued events would be sent after this: ITealium tealium = instanceManager . GetExistingInstance ( TealiumConsts . INSTANCE_ID ); tealium . ConsentManager . UserConsentStatus = ConsentManager . ConsentStatus . Consented ; // The above will inherently opt the user into all categories as none have been provide. // To grant consent and opt into a subset of categories you can use the overload: tealium . ConsentManager . UserConsentStatusWithCategories ( ConsentManager . ConsentStatus . Consented , new ConsentCategory []{ ConsentManager . ConsentCategory . Analytics }); Resetting Consent Preferences Additional options area available to reset the currently selected consent preferences. This will revert the user back to an Unknown status so that subsequent events will begin being queued again. To completely disable, disable it on the TealiumConfig object, as shown in the following example: ITealium tealium = instanceManager . GetExistingInstance ( TealiumConsts . INSTANCE_ID ); tealium . ConsentManager . ResetUserConsentPreferences (); Resources The following sections provide links to Tealium and Xamarin resources that contain detailed information about Tealium for iOS and Android Tealium Documentation The following resources provide links to Tealium documentation for Android and iOS. If you are building a mobile application in Xamarin, you will use bindings to our iOS and Android libraries. Tealium for iOS Tealium for Android Alternatively, if only using UDH services (AudienceStream, EventStream, DataAccess), the Tealium  C#  library may be used as the native code in a Xamarin project. Vendor Documentation The following resources provide links to Xamarin's extensive documentation for adding Tealium's Android and iOS libraries: Xamarin Binding a Java Library Xamarin - Binding an iOS Objective-C Library Walkthrough: Binding an iOS Objective-C Library ... View more

This article describes how to set up the The Trade Desk In-App Events connector in your Customer Data Hub account. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send In-App Event ✓ ✓ 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: Advertiser ID (adv) Represents your Advertiser ID on The Trade Desk. 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 In-App Event Parameters Parameter Description TTD Event Tracker ID ( upid ) TTD Event Tracker ID ( upid ) Mobile App Event ( ref ) This should be the same as the name of the event. Same as the value that you have configured on The Trade Desk configuration page for this specific event ( ref ) Mobile Client IP Address ( client_ip ) Mobile Client IP Address ( client_ip ) Mobile IDFA for iOS ( idfa ) IDFA is the iOS ID for Advertisers ( idfa ) Mobile GPS ADID for Android ( gps_adid ) ADID is the Google Play Advertiser ID ( gps_adid ) Mobile NAID for Windows ( win_naid ) Windows NAID is the Windows Phone Device ID ( win_naid ) Revenue Tracking Value ( v ) Revenue tracking parameters v and vf are only sent if the UI is enabled. ISO 4217 currency codes are used for vf field Floating point numbers are expected for the v field. Example: 0.99 , 3.99 Revenue Tracking Currency ( vf ) Revenue tracking parameters v and vf are only sent if the UI is enabled Note that ISO 4217 currency codes are used for vf field Floating point numbers are expected for the v field. Example: 0.99 , 3.99 Additional Query Data Provide any additional url query parameter data if needed   ... View more

This article describes how to set up the The Trade Desk (theTradeDesk) connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send First Party Advertiser Data ✓ ✓ 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: Agency Secret Key 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 First Party Advertiser Data Parameters Parameter Description Data Center Region Required Select data center geographically closest to where user data comes from. Advertiser ID Required Advertiser ID Trade Desk ID (TDID) Trade Desk ID ( TDID ) Device Advertising ID (DAID) Device Advertising ID ( DAID ) Override TTL in Minutes Override time to live ( ttl ), in minutes Override Timestamp Override timestamp Data Name Required Data Name ... View more

This article describes how to set up the dotdigital connector in your Customer Data Hub account. Table of Contents Placeholder How it Works The dotdigital connector provides digital marketing professionals with SaaS technology solutions and tools, and offers an email marketing platform. Connector Actions Action Name AudienceStream EventStream Trigger Campaign ✓ ✓ Send Email Using a Triggered Campaign ✓ ✓ Send SMS ✓ ✓ Create or Update Contact ✓ ✗ Add Contact to Address Book ✓ ✗ Delete Contact from Address Book ✓ ✗ 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 Username for your API user. To get started using the API, you must first create an API user. These API user credentials (username/password) are required to authenticate each operation/method call and to ensure that you are connected to the correct account. For setup information, see the following vendor documentation: Getting Started with the API API Password Password for your API user. Region ID Region ID to be included in every API endpoint. You can find your API endpoint under Settings > Access > API users. 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 - Trigger Campaign Parameters Parameter Description Campaign ID The ID of the campaign, which needs to be included within the request body. Address Book ID The Address Book ID the campaign is to be sent to. You must specify either an Address Book ID or a Contact ID. Contact ID The Contact ID the campaign is to be sent to. You must specify either an Address Book ID or a Contact ID. Send Date The date and time at which you want the campaign to be sent. Action - Send Email Using a Triggered Campaign Parameters Parameter Description To Address The email address of the recipient. Campaign ID The ID of the triggered campaign. For more information on this endpoint, see the following vendor documentation: Send transactional email using a triggered campaign. Personalization Values Each personalization value is a key-value pair. Action - Send SMS Parameters Parameter Description Telephone Number The mobile number of the contact. Message The SMS message to be sent to your contact's mobile phone. Action - Create or Update Contact Parameters Parameter Description Email The email address of the contact. For more information on this endpoint, see the following vendor documentation: Create contact. Data Fields Each contact data field is a key-value pair. Opt-In Type The opt-in type of the contact. Email Type The email type of the contact. Contact Id The ID of the contact. This must be set to update a contact. Action - Add Contact to Address Book Parameters Parameter Description Address Book ID The ID of the Address Book. For more information on this endpoint, see the following vendor documentation: Add contact to address book. Email The email address of the contact. For more information on this endpoint, see the following vendor documentation: Create contact. Data Fields Each contact data field is a key/value pair. Opt-In Type The opt-in type of the contact. Email Type The email type of the contact. Action - Delete Contact from Address Book Parameters Parameter Description Address Book ID The ID of the Address Book. For more information on this endpoint, see the following vendor documentation: Delete contact from address book. Contact ID The ID of the contact to be deleted. ... View more

A Dynamic Customer Profile (DCP) is a single, actionable view of your customer built from a combination of first and third-party customer data. It enables you to deliver consistent, personalized web and mobile experiences for your most valuable customers, and measure the impact of those experiences. In this article: Table of Contents Placeholder This article describes how to set up the Optimizely Dynamic Customer Profiles connector in your Customer Data Hub account. Connector Actions Action Name AudienceStream EventStream Update Customer Profile ✓ ✓ 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 Token: Visit http://app.optimizely.com/tokens to generate an API token, or http://developers.optimizely.com/classic/token for more information. 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 - Update Customer Profile Parameters Parameter Description DCP Service ID For more information on where to find your DCP Service ID, visit: Create Audiences with Dynamic Customer Profiles. Datasource ID For more information on where to find your Datasource ID, visit: Create Audiences with Dynamic Customer Profiles. Customer ID in Datasource For more information on where to find your Customer ID, visit: Create Audiences with Dynamic Customer Profiles. Tealium recommends using the Optimizely end user ID found in the first party cookie. Customer Profile Attributes A Profile Attribute describes one aspect of a customer's profile within a data source. The specified attribute value overwrites any existing value specified earlier. If a key does not correspond to a registered attribute name, the write will fail, and if a value does not respect the attribute's datatype/format, the write will fail. ... View more

The most advanced analytics for mobile in the world. This article describes how to set up the Mixpanel connector in your Customer Data Hub account. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Track Event ✓ ✓ Update Profile - Set ✓ ✓ Update Profile - Add ✓ ✓ Update Profile - Append ✓ ✓ Update Profile - Union ✓ ✓ Update Profile - Unset ✓ ✓ Update Profile - Delete ✓ ✓ Update Profile - Track Revenue ✓ ✓ Create Alias ✓ ✓ 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 Project Token: A project token is required to send profile and events data to Mixpanel. See: Where can I find my project token? 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 - Track Event Parameters Parameter Description User ID   IP Address   Override Event Time   Event Name (Required) Event Data Custom properties to add to your event Date type properties are converted to Mixpanel date format 'YYYY-MM-DDThh:mm:ss' Properties with empty values are skipped and not included Action - Update Profile - Set Parameters Parameter Description Ignore Last Seen Update   User ID (Required) IP Address   Override Update Time   Created   Phone Number   Last Name   Email   First Name   Full Name   Do Not Overwrite Existing Property Values (Set Once)   Action - Update Profile - Add Parameters Parameter Description Ignore Last Seen Update   User ID (Required) IP Address   Override Update Time   Add Data Specify properties to add a numerical amount to their existing value It is possible to decrement values by providing a negative amount Properties with empty values are skipped and not included Action - Update Profile - Append Parameters Parameter Description Ignore Last Seen Update   User ID (Required) IP Address   Override Update Time   Append Data Specify properties to append a value to their existing list of values Appending to a property that doesn't exist produces a new list with one element Properties with empty values are skipped and not included Action - Update Profile - Union Parameters Parameter Description Ignore Last Seen Update   User ID (Required) IP Address   Override Update Time   Union Data Specify properties to merge their values with the existing list on the user profile Properties must be of Array type in Data Layer Properties with empty values are skipped and not included Duplicate values are ignored Action - Update Profile - Unset Parameters Parameter Description Ignore Last Seen Update   User ID (Required) IP Address   Override Update Time   Unset Data Specify properties to permanently remove them and their values from a user profile Supports Array type in Data Layer Action - Update Profile - Delete Parameters Parameter Description Ignore Last Seen Update   User ID (Required) IP Address   Override Update Time   Action - Update Profile - Track Revenue Parameters Parameter Description Ignore Last Seen Update   User ID (Required) IP Address   Override Update Time   Transaction Amount (Required) Transaction Time (Required) Action - Create Alias Parameters Parameter Description Original User ID Previously set identifier for a user Typically a temporary generated ID before a better user ID becomes available (example: user's email after sign up) New Alias User ID New ID to map to original ID Typically an alias is set immediately after user signs up and all subsequent events & updates utilize the new alias ID For more info see: Using Mixpanel Alias ... View more

View the Release Notes summary to learn about updated product features, enhancements, and fixes. To view details about how to use a new feature, click the Learn More link next to the description. Tags New/Cool Stuff New marketplace tag: Affirm New marketplace tag: AudienceOne Discovery (Cookie Matching) New marketplace tag: RTB House Retargeting New marketplace tag: Snapchat New marketplace tag: Wunderman Segment Broadcasting Updated Adjuggler tag to reflect name branding change to Nui Media. Updated Adobe AppMeasurement tag to version 2.10.0 and VAPI to 3.3.0. Updated AT Internet tag tooltips and code to Version 5.12.0. Updated Amplitude tag to the latest library version and updated the set user property event order. Updated AudienceOne Discovery tag to rename aone_home_work parameter to aone_work_zip. Updated Baidu tag to include events, custom variables, and eCommerce tracking. Updated BrightRoll Conversion tag to OATH Ad Platforms Conversion due to rebranding. Updated CJ Affiliate tag to save cjevent in a cookie and make the configuration of a referral period optional. Updated default Google Ads pageview to a Conversion ID. Updated Fullstory tag snippet and added event to fire on links. Updated Google AdWords tag to   support multiple Google Ads Conversion IDs and Labels and multiple Google Analytics Tracker IDs. Updated Logicad tag to newest version. Updated new Taboola tag to include new events and deprecated older version of the tag. Updated Norton Guarantee Seal to set hash code as a configuration item. Fixes Corrected issue with ContentSquare UX Analytics tag to add validation for required parameters. Corrected issue with Mopinion tag that prevented proper initialization. Connectors New/Cool Stuff New marketplace connector: BlueKai (Learn more) New marketplace connector: Facebook Ads, Customer-Provided Credentials (Learn more) Updated Emarsys connector to support all editable field types available in Emarsys. (Learn more) Updated Selligent connector to include new actions: Add to Action List and Trigger Campaign. (Learn more) Fixes Added support for merge-fields date-formatting and product arrays. Corrected Experian CheetahMail connector issues with CB and REQ parameters and enforced validation for the existence of the associated email. Corrected volume issue related to missing Adobe event parameters in the Salesforce Email Studio (formerly ExactTarget) connector drop-down menu. Universal Data Hub New/Cool Stuff Updated Profile Settings field to "EventDB Retention Time" and the description to read "This determines how long EventDB data will be retained." Updated user interface to ensure that the Chrome tab displays the account name in the tab title when one or more instances of UDH are open in the Chrome browser. Updated user interface to set the default order of enrichments for a profile to match the order displayed in the interface. Fixes Corrected issue causing rules to be removed automatically when an associated enrichment is removed. iQ Tag Management Fixes Corrected display issue for variables in the user interface for the Data Layer tab. Corrected draft promotion process permissions issue with the JavaScript extension. Removed ES6 code in TiQ to prevent blocking for users of Internet Explorer (IE). Installations Fixes Added millisecond-precise timestamp to all hits from iOS Objective-C SDK. Applied minor bug fixes for Swift SDK. Applied minor fix to make RemoteCommand subclassable when using dependency managers, such as CocoaPods. Corrected WatchOS Objective-C issue causing tracking failure when completion handler is not specified. Updated Android device library to support POST data to event endpoint to allow the use of complex nested objects as data layers. Updated Android, Swift, and Objective-C SDKs to use a default 30 minute time out for teal_session_id. (Configurable)   ... View more

This article describes how to import CSV files as a data source, allowing offline data to become enriched and actionable within the Customer Data Hub. Before you begin: Preparing a CSV File for Import This guide has the following sections: How It Works Learn about the process of setting up a file import data source, uploading files, and the final results within the Customer Data Hub. Using the File Import Data Source Step by step instructions for setting up a file import data source. Import Status See how to check on the status of your file imports, including details metrics for number of rows processed and errors. In this article: Table of Contents Placeholder Prerequisites Your account must be enabled for AudienceStream How It Works The File Import feature provides the ability to import a CSV file to supplement online visitor profiles with valuable offline data. Using this feature, you can import a CSV file using a file transfer service, such as an Amazon S3 Bucket. The Tealium server connects to the file service, reads the file and ingests the data. Each imported row is processed as an event. Once ingested, the data can then be enriched, stitched to existing visitor profiles, and sent to other vendors. There are two components used in setting up a file import: a column mapping configuration and a file transfer service. CSV Column Mapping The column mapping configuration determines the event attributes that correspond to each column in the CSV file. The column names are often different from the attribute names in the Customer Data Hub, so this mapping ensures that the data is imported properly. For example, a CSV file might have a column named postalCode , but the matching event attribute is named customer_zip , so a column mapping is needed to associate the two. Mappings can be configured based on an existing event specification or as a custom event. Event Spec Mapping When a file import uses an event specification mapping, the event attributes are preselected and you specify the CSV column name that corresponds to each attribute. Each row is processed as an event of the selected specification, for example tealium_event = "purchase" Custom Mapping When a file import uses a custom event mapping, you specify the event attribute that corresponds to each CSV column. Each row is processed as an event with the following event identifier: tealium_event = "imported" File Transfer Service The file transfer service is a secure location where you upload the files to be imported. The following file transfer services are supported: Amazon S3 (Tealium bucket or your own bucket) Tealium uses VPC endpoints to access S3 buckets directly through the AWS network. Use IAM credentials to allow Tealium to access to your own bucket. Microsoft Azure File/Blob Storage FTP/SFTP If using your own file transfer service, be sure to have the connection details ready before proceeding. Workflow The order of operations for importing a file as a data source is as follows: Step 1 - Create a File Import data source Create a CSV file to import. (Learn more). Choose a file name related to the type of data to import, such as store_purchases . Upload a sample file to automatically detect the column names. Map the columns to event attributes. Configure a new file transfer service or assign an existing file transfer service to your file import data source. Step 2 - Upload a CSV file Manual Upload Drop a file into the upload area of the file import data source. File Transfer Service Upload files to the configured file transfer service. The system checks for new files every 10 minutes. File Import Process Once a file transfer service is assigned to a file import data source you will upload files to the service. The system then uses the following order of operations: Check for New Files The system checks the file transfer service for new files every 10 minutes. Copy New Files When a new file is detected, it is copied from the file transfer location and processed in the Customer Data Hub. Match Filename Prefix to File Import Data Source The prefix of the filename is used to identify which file import data source to use when importing the data in the file. Process Files The header line is read to identify the attributes being ingested. From there, the following processing is performed: Visitor Lookup The visitor ID is used for a lookup of the visitor record in AudienceStream. If an existing visitor record is not found a new one is created. Grouping rows with the same visitor ID will increase the speed of the import. Attribute Enrichment The visitor record will be enriched according to the attributes imported and the existing enrichments in your account. Using the File Import Data Source Setting up a file import data source requires that you prepare a CSV file, configure column mappings, and assign a file transfer service. Before you begin, create a sample CSV file (less than 1,000 rows) to use during the setup process. It will be used to automatically detect the column mappings. Use the following steps to begin setting up a file import: In the sidebar, select Sources > Data Sources. Click + Add Data Source. Add a File Import Data Source Upload a Sample File Configure Column Mappings Configure a File Service Adding a File Import Data Source Use the following steps to add a file import data source: In the sidebar, select Sources > Data Sources. Click + Add Data Source. Under Categories, click File Import and select the File Import platform. In the Name field, enter a unique name related to the file type and click Continue. Upload a Sample File The first step in setting up a file import is to upload sample CSV file. This will automatically detect the columns names in the file and pre-configure them on the column mappings screen. This step is optional and can be skipped by clicking Continue to go directly to the column mappings screen. Use the following steps to upload a sample file: Select a file. Click [Choose a file...] and select the file and click Open, or Drag and Drop a file directly onto the upload area. The Sample Preview displays the file contents in table format. Scroll through the sample file to verify that the columns and data look correct. The detected column names are listed in CSV format below the table and are pre-populated on the column mapping screen. If there are problems with the sample file, click Remove next to the uploaded file name and try another file. Click Continue to go to the Mapping screen. Configure Column Mappings The Mapping screen is used to indicate the type of data being imported and how to map the CSV columns to event attributes. Event Specification Each row of the CSV file is processed as an event. Use the drop-down menu to select which specification matches the data in the file, otherwise select Custom. This selection determines the value of the tealium_event attribute during the import process. If Custom is selected, tealium_event is set to "imported", otherwise it is set to the corresponding specification name e.g. "purchase". Changing the selected specification will reset the column mapping table. Column Mapping Table The column mapping table contains the following columns: Column Label from CSV The columns names from the CSV (pre-populated from the sample file) Date Formatter A date formatter for columns that contain date/time values. Event Attribute The event attribute to receive the data from that column. Sample 1 – Sample 3 Values from the sample file. Use the following steps to map each column to an event attribute: Enter or select a column name from the file (if not already pre-selected). Click the drop-down list in each Event Attribute column and select the event attribute you want that column to map to. Note each CSV column heading must be unique. Columns with date/time values must have a matching date format setting. Click the checkbox in the date column next to any column for which you need to customize the timestamp format. The default value is yyyy-MM-dd . An interactive menu displays that allows you customize the timestamp format for that column. Repeat the column mapping and date formatting steps for each column. Click the red "X" to left of any column you do not want to map to remove that column from the list. (Optional) Click the Enable Visitor ID Mapping in AudienceStream checkbox. Click Continue to advance to the Service Configuration tab. Configure a File Service The file transfer service is a secure location used you upload your files for Tealium to retrieve them. If you are using your own file transfer service, ensure that you have the connection details ready before proceeding. Tealium supports the following file transfer services: Amazon S3 (Tealium bucket or your own bucket) Microsoft Azure File/Blob Storage FTP/SFTP Use the following steps to add and configure your file transfer service: Select a service from the Choose File Service drop-down list. (Optional) If you do not have a file service set up or want to add a new service, click + Add New File Service. The Configure File Service dialog displays. Enter the File Service Name. From the Service drop-down list, select a supported file service from the list. Enter the credentials necessary to access the service you selected. If you selected Tealium S3 Bucket, the necessary credentials are generated for you automatically. Click Save to save this service for future use. Enter the File Name Prefix, such as ordercompleted. The prefix of the filename is used to identify which file import data source to use when importing the data in the file. In this example, the prefix is used to create a CSV file titled ordercompleted_VERSION.csv. Use the slider to Enable or Disable Service Processing for File Import. When set to ON, the file service is checked and files are processed every 10 minutes. Set to OFF if you are not ready to start processing files. You can enable the service later. Click Continue to advance to the Summary tab. Summary In this final step, you will view the summary, make any needed corrections, and then save and publish. View the Event Attribute Mappings. To make changes, click Previous twice to return to the Mapping tab to update. Click Finish to exit the configuration dialog. Your new data source now displays in the list of data sources. Click Save/Publish to save and publish your changes. Upload a File to a File Service The final step is to upload your CSV files, which is done outside of the product interface. To upload a file to a file service, a third-party application is required to initiate the upload. Though you may use any client for this purpose, Tealium recommends Cyberduck because it’s free and supports FTP and Amazon S3. When multiple files are uploaded at the same time using SFTP or S3, the files are processed in the order of the upload timestamp. Use the following steps to upload a file via FTP or Amazon S3 using Cyberduck: Install (or launch) Cyberduck. Create a new connection and give it a title. From the first drop-down list, select the file transfer service used in your File Transfer Service configuration. Enter the credentials (username and password) for your service. My FTP Connection and My SFTP Connection Tealium S3 Bucket – the credentials are pre-populated as an Access Key (username) and Secret Key (password). Provide other details, such as the server, path, port, etc, required by your service. Learn more about accessing third-party S3 buckets using Cyberduck. Save the connection. You are now ready to upload files by dragging and dropping your CSV files into Cyberduck. If you try to access an S3 bucket that is empty, the message "Listing directory / failed." may be displayed. The workaround is to add ".s3.amazonaws.com" to the end of the information in the "Path" field and then cut and paste everything from the "Path" field into the "Server" field instead (leaving the "Path" field empty). This is an issue only for when the bucket is empty; after that the normal set-up will work. When using SFTP, the file must be located in the root folder. Files cannot be located in the sub-folders of an SFTP connection. Check Import Status Once the file import data source is set up and has begun importing files, you can view the import activity from the Status tab. A rolling month report will display, with details about how many rows were processed, with and without errors, in graphical format. A tabular view displays directly underneath the graph. You can also see events imported from files on the Live Events screen by navigating to Live Events and selecting the File Import data source you want to view from the drop-down list. If an error occurs, hovering over the red area of a bar in the graphical display displays a breakdown of the errors. Tooltips will show common errors with a link to detailed report of all errors hosted in S3. Hover over any bar in the display to view details about the number of rows processed. FAQ This section addresses frequently asked questions (FAQs) about the feature described in this article. What if the file transfer service fails? If AudienceStream fails to copy a file using the file transfer service, it will retry in 10 minutes. What if the file fails to be processed? When a file process failure occurs, the file is ignored. The system will not attempt to process the file again. The most common reasons for failure are: The CSV file is improperly formatted and is therefore not a valid CSV file. The CSV file must be in UTF-8 format with no BOM encoding. Column names used in the file definition do not exist in the file A column name is used more than once in the File Service configuration Can files be encrypted with PGP/GPG? File import does not support PGP or GPG key encryption. Unencrypted or decrypted files prior to transfer in order for them to be uploaded successfully. Files are secured with native SFTP in transit, or native S3 in transit and at rest. Can files be compressed? File import does not support compressed (zipped) files. Extract (unzip) files prior to transfer in order for them to be uploaded successfully. ... View more

This article provides best practices for writing queries on EventDB and AudienceDB. In this article: Table of Contents Placeholder Query Best Practices This section provides an example of a "bad" query and describes how the query impacts results, and then provides best practice suggestions on how to create a "good" query with more efficient, meaningful results. Example of a "Bad" Query The following example shows a "bad" query, wherein the results are not as useful as they could be: SELECT * FROM events_view__all_events__all_events This query can impact your results in the following ways: Inefficient – This query does not include a where clause filter which will result in the entire table being scanned and returning much more data than is needed. Performance – Selecting all of the columns in a schema is an expensive operation, especially when using columnar databases such as Redshift. This query will take longer than necessary since, in most cases, all columns are not needed in the result set. Best Practices for a "Good" Query The following list suggests best practices for meaningful query results and provides code examples for each: Select Specific Columns Only select the columns that contain the data you are interested in analyzing: SELECT   "event - udo - referrer" FROM events_view__all_events__all_events Predicate Filter (WHERE Clause) Wherever possible, use predicate column filters to reduce the subset of data to be queried. SELECT   "event - udo - referrer" FROM events_view__all_events__all_events WHERE "event - udo - referrer" = 'google.com' AND "event - udo - page_name" = ‘Home’ Specify a Date Range Filter on date columns to limit the amount of data scanned. SELECT   "event - udo - referrer" FROM events_view__all_events__all_events WHERE "event - udo - referrer" = 'google.com' AND "event - time" BETWEEN ‘2018-07-01’ and ‘2018-07-31’ About Redshift Spectrum EventDB and AudienceDB are hosted on Amazon Redshift and Amazon Redshift Spectrum. This section describes issues that pertain only to Redshift Spectrum  databases . How do I know if I am on Redshift Spectrum or standard Redshift? Redshift Spectrum users have this additional schema, in addition to the standard account__profile schema.  account__profile__spectrum How does using Redshift Spectrum impact my data and query performance? Redshift Spectrum users connect to their Spectrum database in the same way that standard Redshift users connect to their databases. The differences are as follows: Redshift Spectrum user data is stored in S3 instead of within a physical Redshift cluster disk. Redshift Spectrum allows the customer to store and query large amounts of data in comparison to traditional Redshift database user storage. Some users, depending on their data size and query requirements, are hosted on Redshift Spectrum as opposed to standard Redshift. Redshift Spectrum table schemas have additional columns that are referred to as partition columns. How do I use partition column predicate filters? Partition columns, when queried appropriately, can vastly accelerate query performance when performing large scans on Redshift Spectrum databases. The following table provides query examples with partition column predicate filters for AudienceDB and EventDB: Environment Example AudienceDB SELECT col1, col2 FROM account__profile.visitors_view WHERE "visit - day" >= ‘2018-01-01’ SELECT col1, col2 FROM account__profile.visits_view WHERE "visit - day" >= ‘2018-01-01’ EventDB SELECT col1, col2 FROM account__profile.events_view__all_events__all_events WHERE "event - day" >= ‘2018-01-01’ Additional Vendor Information For additional vendor information about query best practices, see the following AWS documentation: Amazon Redshift Best Practices for Designing Queries Improving Amazon Redshift Spectrum Query Performance ... View more

The data supply chain dashboard provides a high level overview of your configuration, summary metrics of your usage, and status alerts that need attention. This article describes the information available in the dashboard and how to change the views. In this article: Table of Contents Placeholder How it Works The overview dashboard provides a comprehensive summary of the data supply chain of the Customer Data Hub. The dashboard uses three interactive panels to represent your data flow: Filters - adjust the dashboard view by product and by time period. Data Flow Summary - see summary metrics of your data flow and important status alerts. Data Flow Details - inspect specific components to see data connections and health status. Data Supply Chain Views The Data Supply Chain dashboard view changes depending on the product view and time period selected. To view, click to select a product and then use the drop-down list to select a time period. Most views contain the following information, with differences described in the product-specific sections below. Data Sources – quick link to data sources Events Received – quick link to live events Events Inspected – quick link to event specifications and summary metrics for event types All Products From the All Products summary view, select from the standard information listed in the overview or one of the following views: Actions Triggered – view the number of successful and failed connector actions Connectors – quick link to EventStream and AudienceStream connectors  EventStream From the EventStream summary view, select from the standard information listed in the overview or one of the following views: Enrichments Applied – quick link to attributes Active Feeds – quick link to feeds EventStream Actions Triggered – view the number of successful or failed EventStream actions EventStream Connectors – quick link to EventStream connectors AudienceStream From the AudienceStream summary view, select from the standard information listed in the overview or one of the following views: Visit Count – view the number of visitors in the time period selected Active Audiences – quick link to audiences AudienceStream Actions Triggered – view the number of successful or failed AudienceStream actions AudienceStream Connectors – quick link to AudienceStream connectors EventStore From the EventStore summary view, select from the standard information listed in the overview or one of the following views: EventStore Feeds – quick link to feeds Events Sent to S3 – view the number of events sent to your S3 bucket EventDB From the EventDB summary view, select from the standard information listed in the overview or one of the following views: EventDB Feeds – quick link to feeds Events Sent to Redshift – view the number of events sent to Redshift AudienceStore From the AudienceStore summary, select Data Sources or one of the following views: Active Audiences – quick link to audiences Visitors Sent to S3 – view the number of visitors sent to your S3 bucket AudienceDB From the AudienceDB summary, select Data Sources or one of the following views: Active Audiences – quick link to audiences Visitors Sent to RedShift – view the number of visitors sent to Redshift Additional Views and Navigation This section describes additional views and the interactions available within with the body of the interface. View Data Flow and Relationships Data relationships and data flow clearly displays in the lower portion of your screen. You can quickly view these relationships and the flow and drill down into the details of related items to edit. Expand and Collapse Expand or collapse the details for an item. Sort Results Use the up (▲) or down (▼) arrows to sort results by volume or whether an action fired successfully or failed to fire. View More Options Click on the More Options vertical ellipses (︙) to go directly to a data source, connector, or event feed to edit. View Errors and Warnings Hover over the warning icon to view error or warning messages and click an available Learn More link to read about how to solve the issue. ... View more

View the Release Notes summary to learn about updated product features, enhancements, and fixes. To view details about how to use a new feature, click the Learn More link next to the description. Tags New/Cool Stuff Added support for the Goal Currency mapping parameter for the Bing UET tag. New marketplace tag: Conversant New marketplace tag: Delacon Call Tracking New marketplace tag: GroupBy New marketplace tag: Holimetrix New marketplace tag: iAdvize New marketplace tag: SchemaApp Updated branding for Adobe ID Service and terminology (Marketing Cloud to Enterprise Cloud). (Learn more) Updated eCommerce default values for the LiveIntent tag and updated configuration parameters to allow mapping override for "name" for the purchase event. Updated Google Ads Cookie Matching Tag to support treating additional mappings as query string parameters. Updated Google Analytics tag to add support for Google AMP Client ID. Updated Google Marketing platform tag branding for Google AdWords, Analytics, and DoubleClick. Updated Pepperjam tag with track click ID query parameters, save in cookie, and send with pixel. Updated Rakuten Marketing conversion code for Safari Tracking Prevention. Updated SellPoints tag to current tag template patterns, updated base_url, and added a cache-busting query string parameter. Updated Sophus3 tag to newest version. Updated the AT Internet Smart Tag integration to allow alphanumeric Visitor IDs. Updated the IBM Digital Analytics tag to support the error tag (cmCreateErrorTag). Updated the script URL for the LightningBolt tag. Fixes Corrected issue with duplicate loading of Google Analytics, DoubleClick, and AdWords (gtag.js). Combined Google Analytics mapping labels for Event and Timing value. Updated Tealium Collect tag to address issue handling pipe-delimited lists of server endpoints. Updated the ClickTrack for AdForm tag call to only use the order data. Connectors New/Cool Stuff New   marketplace   connector:   AWS   Firehose   (Learn more) New   marketplace   connector:   Centro   DSP (Learn more) New   marketplace   connector:   Freshdesk (Learn more) New   marketplace   connector:   PersistIQ (Learn more) Fixes Corrected issue causing   SmartFocus   connector to send dynamic content without   MemberSync. Corrected the   sfdmp.json   file for the   Salesforce   DMP   (Krux) connector to make the connector available in EventStream. Deprecated EventStream non-mobile actions with default mappings for Google Analytics and Adobe Analytics and created actions with default mappings removed. Made AudienceStream connector visitor's current visit checks null safe due to delayed actions and Audience Sizing job actions having null current visits. Placed a temporary hold on the availability of the Zoho Mail connector from the marketplace until OAUTH2 is implemented. Temporarily hid the Floodlight   connector from the connector marketplace pending resolution of API limit issues and the ability to offer API batching. Universal Data Hub New/Cool Stuff Applied updates to ensure visitors using Trace do not skip end of visit processing due to early eviction. Fixes Corrected issue to not allow attributes to be added to event specifications when the values are generated by a data source. Corrected Trace-related browser console error when logging into   UDH. iQ Tag Management New/Cool Stuff Added static mapping support for marketplace tags. (Learn more) Built-in DOM variables now display in the UI on the Data Layer tab. (Learn more) Replaced in-product code editors with new, more flexible ace.c9.io editor. The Javascript extension now offers draft mode, scheduled promotion, a robust editor, and is integrated with the publish engine and permissions. (Learn more) Fixes Corrected duplicate JavaScript draft mode extension issue. Corrected issue in Consent Manager related to content definitions that disabled the ability to override user language selection. Corrected issue in which a JavaScript Code extension scoped to tag did not update utag.js timestamp for cache busting. Corrected issue with ES6 function inside utui.core.js to prevent blocking login for users logging in from older browsers. Installations New/Cool Stuff Added Mobile SDK support for Crash Data collect in iOS in preparation for UDH Connector support for end-to-end integration with New Relic. (Learn more) Updated iOS (Objective C) SDK to use HTTP Collect API (/event) in place of legacy vdata. ... View more

We recently identified some issues with how the Explicit Consent Prompt was handling tracking calls under certain conditions. This led to scenarios where extra tracking calls were being made or tracking calls were being permitted prior to consent. The latest release of this feature has addressed these issues. Who Is Affected Pages Using noview Option If you are using the utag override option, noview , then you might have experienced extra tracking calls. The explicit consent prompt was ignoring the noview option and triggering tracking calls based on the consent status. Since a page that uses the noview option typically triggers a tracking call based on other criteria, this often led to duplicate tracking calls. Event Tracking Prior to Consent If your page tracks additional events to the initial page load, then these might have been allowed even prior to acquiring consent. If the explicit consent prompt was actively displayed to the visitor, tracking calls that occurred at the same time were incorrectly allowed. How It Works Now The latest updates to the Explicit Consent Prompt include the following fixes: Explicit Consent Prompt will not trigger a tracking call if the noview option is enabled. If you previously implemented a work-around for this scenario, you should test the new behavior and make adjustments as needed. Tracking calls that occur while the consent prompt is active will be queued and handled appropriately after consent is received. These changes will be reflected upon your next publish. We always recommend that you publish to Dev or QA first to test your changes before promoting to Prod. ... View more

View the Release Notes summary to learn about updated product features, enhancements, and fixes. To view details about how to use a new feature, click the Learn More link next to the description. Tags New/Cool Stuff Added support for item-level basket reporting on the "Purchase" event when using the Google AdWords Conversion Tracking tag. New marketplace tag: Adobe Audience Manager New marketplace tag: Impact Universal Tracking New marketplace tag: SnapChat New marketplace tag: Teavaro New marketplace tags: Google Customer Reviews (Badge and Survey) Updated AT Internet tag to allow XTO parameter mappings for multiple categories. Updated Pinterest tag to include enhanced match. Updated the TRUSTe tag to TrustArc and added new GTM and CDN parameters. Fixes Corrected issues bundling multiple Doubleclick Floodlight (gtag.js) tags. Corrected link to Help Docs in the UI for the Currency Converter tag. Updated Google AdSense tag to address error when attempting to add advertisements. Updated Google gtag.js tags to resolve issues when bundling. Connectors New/Cool Stuff Implemented Mailchimp and Sendgrid as the first two push-based input connectors in UDH. (Learn more) New marketplace connector: Adobe Target New marketplace connector: CallRail New marketplace connector: CO-SENDER New marketplace connector: Krux (Salesforce DMP) New marketplace connector: Postways New marketplace connector: Square New marketplace connector: Streak New marketplace connector: Taplytics New marketplace connector: XiTi Analytics (AT Internet) The Centro connector is now hidden and not available from the connector marketplace due to the deprecation of the Centro s2s endpoint. The MediaMath connector is now deprecated and no longer available from the connector marketplace. Existing actions will remain functional with the addition of an informational message regarding deprecation. Updated Amazon Kinesis Data Streams (KDS) and Amazon Simple Queue Service (AWS SQS) connectors to enable TiQ data-sources. Updated DCM Floodlight Connector Setup Guide inline and TLC documentation. (Learn more) Updated Facebook connector API to current version. Updated Selligent connector to add support for linked lists.  ( Learn more ) Updated the Google DoubleClick Campaign Manager (DCM) Floodlight connector to add "api@tealium.com" as a user in their FL account and, as a result, no longer require user login. Fixes Corrected Adobe connector context data (XML) to be passed in the correct format. Universal Data Hub New/Cool Stuff Added button to UDH UI to allow user to scroll back to the top on the attributes tab. Added the ability to support persistent cookie-sync data for EventStream. (Learn more) Applied updates to optimize API Sampler performance. Made Universal data attributes available in the drop-down lists for the "Join Attributes" enrichment. Provided the ability to store DataCloud profiles in Amazon Aurora to aid in profile migration. Updated Audience Sizing language in UI to match new UDH user interface. Updated messaging in UDH to clarify configuration requirements for Visitor ID attributes in regard to visitor stitching. Updated ON/OFF toggle button colors in user interface to more easily discern toggle position. Updated the order of enrichments in the UI to honor the calculated sort order. Updated the UDH UI to allow easier selection of ADB attributes. Updated UDH UI to display secondary Visitor IDs in the Visitor API to assist users in determining the reason that a look up may not return the expected visitor. Fixes Corrected console error in UDH when clicking on duplicate icon for custom UDH attribute. Corrected issue in UDH to allow for the selection of more than one event specification. Corrected issue to allow Tealium Cookie Sync (TCS) cookie to insert values into events for PUT/POST collect calls. Removed whitespace from the end of attribute names and applied checks to ensure there is no additional whitespace prior to saving. Updated audience-level retention values to no longer require correction of visitorRetentionDays for existing profiles. Updated Product Feedback dialog to consistently render correctly on all screens. iQ Tag Management New/Cool Stuff Added Single Sign-On (SSO) support to FreshDesk from TLC. Applied post-deployment update to Cascading Style Sheet (CSS) for the new TiQ interface to correct minor cosmetic issues. Applied changes to mobile profiles to ensure that the Tealium Collect and the Tag Management modules cannot both be enabled at the same time. (Learn more) Installations New/Cool Stuff Integrated Privacy Manager for Android mobile library to streamline GDPR compliance for customer. ... View more

The JavaScript Code extension is designed for implementing custom JavaScript code through Tealium iQ Tag Management. It comes with a built-in code editor and configuration options for when and where to run the code. This is the basic version of the JavaScript Code extension. For advanced needs, see the Advanced JavaScript Code Extension. In this article: Table of Contents Placeholder Prerequisites Permission to Manage JS Code Extension This permission is required to add or edit a JavaScript Code extension in your account. utag version 4.38 or higher This version provides support for the execution options under the All Tags scope Upgrade to this version if you have not already done so. How It Works The JavaScript Code extension give you the power to create custom code to be included in the files that load on your site. Depending on the scope of the extension, the code loads in either utag.js or in a vendor utag.#.js file. The code entered into the text box of the extension is included in the utag files just as it appears, but it is important to note that the code is run from an anonymous function wrapper, as shown in the following example: function(a, b) { // content of JavaScript Code extension runs here } The parameters represent the following: a: indicates which tracking call was made "view" for utag.view() and "link" for utag.link(). b: a reference to the data object passed to the tracking call. While the JavaScript Code extension is flexible and can be used for most anything you would want to accomplish within your tag management solution, it is important to understand the impact it could have on your account. Tealium recommends that you try to use the other built-in extensions to accomplish your task before turning to the JavaScript Code extension. Consider the following Pros and Cons of using the JavaScript Code extension: Pros Fully customizable code can accomplish most anything that can be accomplished using JavaScript. Faster and more familiar for developers that are accustomed to writing front-end JavaScript. Cons Difficult for non-developers to understand and edit. More difficult to maintain over time. Prone to typos and logic errors. Variable names are hard-coded and therefore not updated if you change the name of a variable on the Data Layer tab. A changed variable name will not be propagated to the JavaScript Code extension. For example, if you change the name of a variable you must also change all occurrences of that variable within JavaScript Code extensions. Conditions Conditions add an extra layer of control on top of the Scope. You can apply any number of conditional statements in the Set Data Values and Join Data Values extensions. These conditions control when the JavaScript Code extension will run. Execution Order and Run Once The JavaScript Code extension offers the following options for determining the timing of when the code will run. To learn about the order of operations in utag.js, see Order of Operations. Before Load Rules After Load Rules (default) After Tags Run Once after Load Rules Run Once before Load Rules Run Once after Tags By default, a JavaScript Code extension runs for every tracking call, including in-page event tracking, which would potentially cause it to run more than once per page load. If you want to prevent multiple executions of your code, choose one of the Run Once options in the execution drop-down list. These options are only available in the All Tags scope and require utag v4.38 or higher. Before You Begin Consider the following before you begin: Do not surround the code with <script> tags since the content of the text box will be included in a JavaScript file exactly as you enter it. If you are referencing a variable from the utag_data object, such as page_name or language , use b['VARIABLE'] . (Learn more about the b object.) If you are referencing a variable defined in the tag template of the scoped tag, such as account_id or base_url , use u['VARIABLE'] . Configuration Steps Use the following steps to configure the JavaScript code extension: Go to the Extensions Marketplace and add the JavaScript Code Extension from the Advanced tab. Title: Enter a name for this extension. Scope: Choose from the following options: Preloader (does not support Conditions) DOM Ready All Tags Vendor Tag(s) Execution: This drop-down list is only available to the All Tags scope. Choose one of the following options: Before Load Rules After Load Rules (default) After Tags Run Once after Load Rules Run Once before Load Rules Run Once after Tags Enter your JavaScript Code in the editor. Condition (optional) Click Add Condition and create a conditional statement. The first drop-down list is populated with variables and the second drop-down list provides a list of evaluating operators. If you are running the conditional logic against a value, enter it in the text field. To apply multiple conditions, choose between the AND and OR logic. Save and publish the changes. Frequently Asked Questions (FAQ) Why am I unable to add or edit the new JavaScript Code Extension? You do not have the Manage JS Code Extension permission in your Tealium iQ account. Contact your Tealium account administrator to obtain the permission. Why can't I select Preloader with Conditions? In the preloader state, the Data Layer is not yet populated and there is no utag data with which to evaluate the conditional logic. For this reason, the Conditions drop-down selections are greyed out when Preloader is selected. What's the difference between Preloader and Run Once Before Load Rules? Both will cause the extension to run once before the Data Layer is populated—except the Preloader does not support conditions. Be mindful of this caveat when configuring the Scope. ... View more