Tealium Learning Center

This article describes how to set up the Chameleon connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Create User ✓ ✓ Update User ✓ ✓ 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 key API key can be found here: https://www.trychameleon.com/integrations 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 User Parameters Parameter Description User ID An ID that uniquely identifies the user in your database. For more information, see: Send User Properties Email An email address to connect their data in integrations you enable. User Data Any and all parameters pertinent to the user. Action - Update User Parameters Parameter Description User ID An ID that uniquely identifies the user in your database. For more information, see: Send User Properties Email An email address to connect their data in integrations you enable. User Data Any and all parameters pertinent to the user. ... View more

This article describes how to set up the Klenty connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Create Prospect ✓ ✓ Update Prospect ✓ ✓ 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 key To access the Kenty REST API's, you must have a Klenty account from which to generate your API key. Use the following steps to obtain this API key: Log into your Klenty account. Go to Settings > User Preferences > Klenty API Key. Click on the Generate API Key key icon to. For more information, see: http://support.klenty.com/articles/2530207-klenty-api 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 Prospect Parameters Parameter Description Username The username associated with the account. For more information, see: http://support.klenty.com/articles/2530207-klenty-api Email The email address of the prospect. First Name The first name of the prospect. Phone The phone number of the prospect. Company The company associated with the prospect. Full Name The full name of the prospect. Last Name The last name of the prospect. Middle Name The middle name of the prospect. Department The department associated with the prospect. Company Domain The company domain associated with the prospect. Title The title of the prospect. Location The location of the prospect. City The city associated with the prospect. Country The country associated with the prospect. List The list associated with the prospect. Tag The tag associated with the prospect. Action - Update Prospect Parameters Parameter Description Username The username associated with the account. For more information, see: http://support.klenty.com/articles/2530207-klenty-api Prospect Identifier The identifier of the prospect, typically email. Email The email address of the prospect. First Name The first name of the prospect. Phone The phone number of the prospect. Company The company associated with the prospect. Full Name The full name of the prospect. Last Name The last name of the prospect. Middle Name The middle name of the prospect. Department The department associated with the prospect. Company Domain The company domain associated with the prospect. Title The title of the prospect. Location The location of the prospect. City The city associated with the prospect. Country The country associated with the prospect. List The list associated with the prospect. Tag The tag associated with the prospect. ... View more

This article describes how to set up the iSpot TV Conversion Tracking connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send Pixel ✓ ✓ 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: Site ID The tracking code requires a unique Site ID for each unique web site or app, which will be provided by iSpot. The format for Site ID is TC-1234-1, where: TC stands for tracking code 1234 is the client's account id -1 is the site identifier, which increments per site. 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 Pixel Parameters Parameter Description IP Address IP address should be IPv4 only. Example: 23.123.223 Tealium will pass the value as part of the X-Forwarded-For request header. User Agent Pass the user agent of the original client device. Tealium will pass the User-Agent in the request header. Cookies The iSpot cookie will be sent as part of the Cookie request header. The value of this cookie can be derived from the original client-side browser via JSON response from the service. Example: https://ps.ispot.tv/v2/your-site-id.gif Referrer Referrer of the original visit, which is sent in the referer request header. Event Time If the time difference between the client visit and server-side request is greater than a few minutes, pass the original UTC time of the client visit formatted as yyyy-MM-dd hh:mm:ss If you do not specify an Event Time, Tealium will generate one at execution time. Custom Data The iSpot Tracking Code supports passing custom data for your business goals. Pass individual fields in this section and Tealium will combine them into a URL-encoded JSON object. ... View more

This article describes how to set up the Userlist connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Track User Data ✓ ✓ Track 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: Push API key To start sending data into Userlist, you first have to get your Push API Key, which is used to authenticate your requests to the Push API and connect the data with your account. Keep this Push API Key secure. For more information, see: Getting Your User Data into the System (Integration Guide). 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 User Data Parameters Parameter Description Identifier Unique identifier for this user. This can be either the user's primary key in your database, a generated tracking identifier or their email address. For more information, see: Getting Your User Data into the System (Integration Guide). Email The email address that will be used to send messages to this user. Signed Up At The time the user signed up, formatted using ISO 8601. If it is not set, Userlist will use the current time. Last Seen At The time the user was last seen inside your application. Formatted using ISO 8601. If it is not set, Userlist will use the current time. Userlist will update this property whenever an event happens for this user. Properties Custom properties that further describe the user. What you store here is totally up to you. The object's keys are normalized to snake_case . If they are set, we will use name , or first_name and last_name to represent the user inside of Userlist. Action - Track Event Parameters Parameter Description Name The name of the event that is triggered. The name will be normalized to snake_case . For more information, see Getting Your User Data into the System (Integration Guide). User If the identifier is not known to the system, it will create a new user. If the user already exists it will update it using the given information. Occurred At The time at which the event occurred. Formatted using ISO 8601. The system will use the current time if you do not provide input. Properties Custom properties that further describe the event. What you store in there is totally up to you. The object's keys will be normalized to snake_case . ... View more

This article describes how to set up the Tamber connector in your Customer Data Hub account. 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: Project Key Most requests can be made with only a Project key. All requests can be made with only an Engine key, as the Project will be automatically inferred. For more information, see: https://tamber.com/docs/api/#authentication Engine Key Most requests can be made with only a Project key. All requests can be made with only an Engine key, as the Project will be automatically inferred. For more information, see: https://tamber.com/docs/api/#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 - Send Event Parameters Parameter Description User Unique identifier for the user. If the user does not yet exist, this action will create one. For more information, see: https://tamber.com/docs/api/#event-track Behavior The unique behavior name. Item Item associated with the event. Amount The amount that the behavior was performed. Example: Percentage of the movie that was watched, rating given, etc.). Defaults to 1.0 if a value is not supplied. Created Time the event occurred. Defaults to the current time if a value is not supplied. Hit Set to true to indicate that the event represents a successful recommendation. Example: The item in the event was presented to the user as a recommendation. Context Data The context in which the event occurred. Useful for segmenting events data to determine the impact of interface elements and other contextual variables on user behavior. Also useful for A/B testing interface changes. ... View more

This article describes how to set up the Sizmek connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add User To Sizmek Segment(s) ✓ ✓ Remove User From Sizmek Segment(s) ✓ ✓ Replace all Sizemek Segments for User ✓ ✓ 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 Sizmek Segment(s) Parameters Parameter Description   cookie_id Required. Obtain the value from the visitor's browser.   segments Required. Pipe-separated list of segment IDs. If you pass an array type, Tealium will correctly format the data to be passed.   advertiser_id Optional. Sizmek Advertiser ID.  Set advertiser_id to zero ( 0 ) for a third-party advertiser.   account_id Optional. Account ID   adid Optional. Android ID used for mobile users.   idfa Optional. Apple IDFA used for mobile users. Additional Information This action is an incremental update of the user's segments. To send any other query parameter key-value pairs, map a Custom value key to the value. Action - Remove User From Sizmek Segment(s) Parameters Parameter Description   cookie_id Required. Obtain the value from the visitor's browser.   segments Required. Pipe-separated list of segment IDs. If you pass an array type, Tealium will correctly format the data to be passed.   advertiser_id Optional. Sizmek Advertiser ID.  Set advertiser_id to zero ( 0 ) for a third-party advertiser.   account_id Optional. Account ID   adid Optional. Android ID used for mobile users.   idfa Optional. Apple IDFA used for mobile users. Additional Information This action is an incremental update of the user's segments. To send any other query parameter key-value pairs, map a Custom value key to the value. Action - Replace all Sizemek Segments for User Parameters Parameter Description   cookie_id Required. Obtain the value from the visitor's browser.   segments Required. Pipe-separated list of segment IDs. If you pass an array type, Tealium will correctly format the data to be passed.   advertiser_id Optional. Sizmek Advertiser ID.  Set advertiser_id to zero ( 0 ) for a third-party advertiser.   account_id Optional. Account ID   adid Optional. Android ID used for mobile users.   idfa Optional. Apple IDFA used for mobile users. Additional Information This action is an incremental update of the user's segments. To send any other query parameter key-value pairs, map a Custom value key to the value. ... View more

This article describes how to set up the Twitter Custom Audiences connector. In this article: API Information This connector uses the following vendor API: API Name: Twitter Ads API API Version: v11 API Endpoint: https://ads-api.twitter.com/ Documentation: Twitter Custom Audiences API Batch Limits This connector uses batched requests to support high-volume data transfers to the vendor. Requests are queued until one of the following three (3) thresholds is met: Max number of requests: 1000 Max time since oldest request: 60 minutes Max size of requests: 2 MB Prerequisites Sign up for a developer account. Both Essential and Elevated developer access can access the Ads API. Please see the access levels to determine what access is required. Create a developer App and secure your token Request access to the Ads API. Make sure to include the correct App ID in the application. The App ID can be found in the Developer Portal under Projects & Apps. Example: 16489123 Note:  If you are already building on the Twitter Developer Platform and have a developer account, skip to step three. How it Works Twitter Custom Audiences gives you control on who sees your Twitter Ads. Twitter Ads gives you powerful context to connect your message to what’s most meaningful to your customers in real time. Engaging with real-time Tweets can influence conversations in a way that can help build your business. Audiences is a tool in your Twitter Ads account that allows you to review and manage your audiences. You can access it by navigating to Tools > Audiences. From there, you can use your Custom Audiences in your campaign targeting to directly reach the users you care about. Tealium provides the ability to create a Twitter Custom Audience through the user interface within AudienceStream and leverage your audience data to populate the Audience lists. Additionally, Audience lists can be created in your Twitter Ads account and populate into AudienceStream to add or remove users. Examples of audiences that you can re-target previous customers, web visitors who haven't yet converted, and/or target high-value customers. Tealium provides a list of hashed identifiers that can be sent to Twitter to add or remove a user from the custom audience list, and Twitter performs a match and produces segments that are made available against media buying on Twitter. Your lists are matched with @handles on Twitter so that you can directly target them in your campaigns, making your marketing highly relevant. Considerations All user identifiers except "Partner User ID" must be hashed using SHA256 hashing methods and normalized. If the "User Identifier is already hashed" checkbox is unchecked, The connector action will normalize and hash the mapped value.  When you create a Custom Audience, there's an initial processing period where the users on the Custom Audience are "matched" by the Twitter systems to their Twitter @handle. This will then enable ad serving with the Promoted Ads to their account. It's possible that not all of the users on your Custom Audience are active Twitter users, which is why you might see a final Custom Audience size that is smaller than the connector actions firing volume. All Custom Audiences show up in AudienceStream, but only those in "Ready" serving status will properly target users in your campaign. This is viewable within your Twitter Ads account > Audiences section. An audience can only be targeted if it matches at least 100 users active within the past 90 days on Twitter-owned and -operated clients. Generally speaking audience changes are processed in batches that run every 6-8 hours. While an audience change is processing the existing audience to be updated is unaffected. Audience lists created through AudienceStream will be added as a "List" Type within the Ads Campaign manager. It is recommended to not use Twitter data to derive or infer potentially sensitive characteristics about Twitter users. A listing of these characteristics can be found at More About Restricted uses of the Twitter APIs. Connector Actions Action Name AudienceStream EventStream Add User To Custom Audience ✓ ✓ Remove User From Custom Audience ✓ ✓ 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: Ad Account ID Required. Provide your Twitter Ad Account ID. Your Account ID can be located in your account's URL when logged in. Example: If the URL is https://ads.twitter.com/accounts/1234abcd/, the account ID is 1234abcd. Create a Custom Audience Overview The Create Custom Audience overlay appears within the Configuration screen of the Twitter Custom Audiences connector. The Name field is the only required value for creation of an Audience List. The list_type parameter was previously used to identify the user identifier type of the Audience (i.e. email, Twitter User ID, Partner User ID, etc.) however Audiences now have the ability to accept multiple user identifiers for the same Audience and this field is no longer required. 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 Custom Audience Parameters Parameter Description Custom Audience Required Select audience from list. This value is retrieved from the Twitter Ads account and will appear instantly when created through the AudienceStream Configuration screen. For more information, see Custom Audiences. Device ID User Device ID. This value should be an iOS Advertising Identifier, Google Advertising ID, or when not available - Android ID.  Email User Email. If an unhashed email address is mapped, please utilize the User Identifier Hashing checkbox. Otherwise a SHA256 Email should be mapped. Partner User ID The user's ID in the partner's system.  If your company uses its own standard ID system to track users (i.e. not common user identifiers like email addresses, device ids, twitter user ID, etc...) then this is the recommended parameter. Phone Number The user's phone number. This value is no longer supported by the API and should not be mapped Twitter Handle The Twitter @handle belonging to the user. Twitter ID The Twitter ID belonging to the user. The Twitter ID is a unique value that every account on Twitter has. No two people have the same ID. Although an account can change its @handle, it can never change its Twitter ID User Identifier Hashing All user identifiers except "Partner User ID" must be hashed using SHA256 hashing methods and normalized. If the checkbox is unchecked, the Add User action will normalize and hash the mapped value. Effective At Membership option. The UTC time at which the custom audience associations should take effect. Expressed in ISO 8601. Defaults to the current date and time. A millisecond (MS) since epoch timestamp may be provided, and will be formatted correctly. Expired At Membership option. The UTC time at which the custom audience associations should expire. The specified time must be later than the value of "Effective At". Expressed in ISO 8601. Defaults to your configured default expiration period, which is typically 30 days or 720 hours from the value of "Effective At". Action - Remove User From Custom Audience Parameters Parameter Description Custom Audience Required Select audience from list. This value is retrieved from the Twitter Ads account and will appear instantly when created through the AudienceStream Configuration screen. For more information, see Custom Audiences. Device ID User Device ID. This value should be an iOS Advertising Identifier, Google Advertising ID, or when not available - Android ID.  Email User Email. If an unhashed email address is mapped, please utilize the User Identifier Hashing checkbox. Otherwise a SHA256 Email should be mapped. Partner User ID Partner User ID. If your company uses its own standard ID system to track users (i.e. not common user identifiers like email addresses, device ids, twitter user ID, etc...) then this is the recommended parameter. Phone Number The user's phone number. This value is no longer supported by the API and should not be mapped Twitter Handle The Twitter @handle belonging to the user. Twitter ID The Twitter ID belonging to the user. The Twitter ID is a unique value that every account on Twitter has. No two people have the same ID. Although an account can change its @handle, it can never change its Twitter ID User Identifier Hashing All user identifiers except "Partner User ID" must be hashed using SHA256 hashing methods and normalized. If the checkbox is unchecked,  the Remove User action will normalize and hash the mapped value. Effective At Membership option. The UTC time at which the custom audience associations should take effect. Expressed in ISO 8601. Defaults to the current date and time. A millisecond (ms) since epoch timestamp may be provided, and will be formatted correctly. Expired At Membership option. The UTC time at which the custom audience associations should expire. The specified time must be later than the value of "Effective At". Expressed in ISO 8601. Defaults to your configured default expiration period, which is typically 30 days or 720 hours from the value of "Effective At". ... 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: Confirmit New marketplace tag: ContactWare for CX New marketplace tag: Jornaya New marketplace tag: LiveIntent In-App Tracking Updated the Adobe AppMeasurement for JavaScript tag to Version 2.14. (Learn more) Updated the Adobe Experience Cloud ID service tag to Version 4.3. (Learn more) Updated Facebook Pixel to support passing an event. Updated the Tealium Collect tag to capture downstream tag data. Fixes Corrected the network ID parameter name for the Adition tag. Updated the tab description for User ID and AuthState for the Adobe Experience Cloud ID Service tag. Connectors New/Cool lStuff Updated API error messaging for the Google Adwords Customer Match connector to include more detailed information. Fixes Corrected an issue with connector HTTP request retries that caused an abnormal number of reported errors (excludes SOAP and older connectors). Updated the Facebook Ads connector to remove the MULTI_HASH filter from the audience lookup options. iQ Tag Management Fixes Corrected issue causing the Go Live Notification email to be sent more than once for some accounts Updated the Tealium welcome email template to include updated links to Documentation, Forums, and Tealium Education Online. Universal Data Hub New/Cool Stuff Added rule and audience support for "matches regular expression (Regex)" for string operands. The Visitor Profile Sampler now displays a stitching distribution graph and five dashlets displaying a report of the most frequently asked questions. (Learn more) Fixes Corrected issue causing an error when selecting the Visitor ID attribute as a perspective in Audience Discovery. Corrected issue in AudienceDB to display all attributes instead of only displaying the enabled attributes. Installations Fixes Corrected issue causing Android application crashes when running multiple webviews. ... View more

This article describes how to load Tealium data into Snowflake using the Snowflake web interface. This article focuses on the Snowflake web interface and Data Load wizard and provides an overview of Snowflake command line tools. For more detailed information about using Snowflake, see the Snowflake Documentation. In this article: Table of Contents Placeholder How it Works Tealium DataAccess customers can use the Snowflake web interface to connect their data to an external solution for advanced querying and data analysis. The web interface provides an intuitive wizard that you can use to load limited amounts of data into a table from a small set of flat files. To do this, the wizard uses the PUT and COPY commands to load data and then simplifies the data loading process by combining the staging files and loading data phases into one single operation. The web interface is intended for loading small numbers of files (up to 50 MB). This limitation ensures optimal performance due to the fact that browser performance can vary between hardware, browser types, and browser versions. Prerequisites The following items are required to connect your DataAccess data from the Tealium-issued Amazon S3 bucket: Tealium DataAccess with AudienceStore and EventStore enabled You must configure the AudienceStore connector within AudienceStream in order for data to be delivered to your DataAccess bucket. For additional information about AudienceStream configuration, see the Tealium AudienceStore Setup Guide. Valid Tealium DataAccess credentials for either EventStore and/or AudienceStore. Getting Started The following sections guide you through the steps required use the Snowflake Data Load web interface to select source files and load Tealium data into Snowflake. Tealium recommends loading DataAccess data to a table with a variant data type, which accommodates the semi-structured nature of JSON files without enforcing schema requirements. See the Best Practices section in this document for additional information and tips on parsing the data after it has loaded. Open the Data Load Wizard Use the following steps to open the Snowflake Data Load wizard: Log in to your Snowflake account. Click Databases > Tables. Do one of the following: Click a table row to select it and then click the Load Data button. Click a table name to open the table details page, and then click the Load Table button. The Load Data wizard displays. Proceed to the next section to select your source files from DataAccess, which will enable you to begin loading data into the table you selected. Select Source Files from DataAccess When prompted to select source files, you will create a new stage for your Tealium DataAccess data that resides in AWS S3. Use the following steps to select source files from Tealium DataAccess: Select Existing Amazon S3 Location. Click Next. Proceed to the next section to enter your DataAccess credentials. Enter Your DataAccess Credentials Use the following steps to enter your DataAccess credentials: Retrieve your DataAccess credentials for EventStore or AudienceStore if you have not done so already. The credentials are the same for both EventStore and AudienceStore. If your credentials have already been generated, your Secret Access Key does not display. Work with your colleagues to retrieve the existing key or to determine if a new one should be regenerated. Once you have your valid credentials, enter them into the following fields: Access Key Enter the Access Key ID provided by Tealium, for example: AKIA**************** Secret Key Enter the Secret Access Key provided by Tealium. Bucket Enter only the first value from the path field in Tealium, for example: If your Tealium Path is: /dataaccess-us-east-1.tealiumiq.com/myaccount/main Enter : dataaccess-us-east-1.tealiumiq.com (without slashes). Prefix Enter the remaining part of the path field from Tealium, starting with the account name and ending with a trailing slash (/). Example: myaccount/main/ Region Select the region indicated by your bucket name, for example us-east-1. Proceed to the next section to create a file format. Create a File Format Use the following steps to create a file format: Click the plus (+) symbol next to the drop-down list. The Create File Format dialog displays. Enter the following information: In the Name field, enter a name for the file format you will use for your DataAccess data, for example: TEALIUM_JSON. This is a required field. Select a Schema Name type from the drop-down list, for example: Public. Select a Format Type from the drop-down list, for example: JSON. Select a Compression Method ;from the drop-down list, for example: Gzip. Select one or more of the following checkboxes: Enable Octal Allow Duplicate Strip Outer Array Strip Null Values Ignore UTF-8 Errors In the Comment field, enter descriptive comments about this file format. Example: Tealium stores JSON data in Gzip compressed files. Click Finish. Proceed to the next section to load your data. Load Data Use the following steps to continue manually loading data using the web interface, continue reading the steps below. You can optionally load data from the command line. If you select this method, skip to the Load Using Command Line section. Select your previously-named file format from the drop-down list. Click Load to immediately load data or click Next to configure additional load options. If the warehouse is not currently running, resuming the warehouse could take up to 5 minutes, in addition to the time required for loading. Load Using Command Line (Optional) Use the following steps to load your data from the command line: Install SnowSQL Before you can load data from command line, you must install SnowSQL on your machine. (Learn more) Configure Snow SQL After completing the SnowSQL installation, you must edit your configuration file with your credentials to be able to connect to your Snowflake instance. Open your configuration file located in the following directory: For Linux/Mac OS ~/.snowsql/ For Windows %USERPROFILE%\.snowsql\ Edit the file by modifying the connections section to input your credentials. Example: [connections.tealium_example] #Can be used in SnowSql as connect tealium_example accountname = MY_ACCOUNT_NAME username = MYUSER password = ******************** Modify the options or variables sections as you prefer. (Learn more) Connect through SnowSQL Once your connection details are saved in your configuration file, connect to SnowSQL using a shell command. Replace  tealium_example with your connection name: $ snowsql -c tealium_example To customize your connection, see Connecting Through SnowSQL. Load Data Using the COPY INTO Command Once you are connected, execute a COPY INTO <table>  command to load your data into the target table. The following example loads data from files in the named stage my_dataaccess_stage  which was created in the previous steps. Using appended pathing, the statement only loads files located in the events subdirectory: COPY INTO mytable FROM ‘@my_dataaccess_stage/events/’ FILE_FORMAT ‘TEALIUM_JSON’; Best Practices This section provides helpful information about best practices for parsing data after the data is loaded. Parse EventStore Data EventStore is formatted in a flattened JSON file. If you followed the data loading steps described in this document, your EventStore data should now be structured in your variant type column. In order to format the data into a more usable structure for querying, you must parse the JSON. The following sample query defines all default EventStore attributes columns into dedicated columns of a database view: CREATE OR REPLACE VIEW TEALIUM_STD_EVENTS AS SELECT JSON:"visitorid"::string as visitorid , JSON:"eventid"::string as eventid , JSON:"useragent"::string as useragent , JSON:"device_type"::string as device_type , JSON:"eventtime"::number as eventtime , JSON:"dom_domain"::string as dom_domain , JSON:"dom_pathname"::string as dom_pathname , JSON:"dom_query_string"::string as dom_query_string , JSON:"dom_title"::string as dom_title , JSON:"dom_url"::string as dom_url , JSON:"dom_viewport_height"::number as dom_viewport_height , JSON:"dom_viewport_width"::number as dom_viewport_width , JSON:"pageurl_domain"::string as pageurl_domain , JSON:"pageurl_full_url"::string as pageurl_full_url , JSON:"pageurl_path"::string as pageurl_path , JSON:"pageurl_querystring"::string as pageurl_querystring , JSON:"pageurl_scheme"::string as pageurl_scheme , JSON:"referrerurl_domain"::string as referrerurl_domain , JSON:"referrerurl_full_url"::string as referrerurl_full_url , JSON:"referrerurl_path"::string as referrerurl_path , JSON:"referrerurl_querystring"::string as referrerurl_querystring , JSON:"referrerurl_scheme"::string as referrerurl_scheme , JSON:"udo_ut_account"::string as udo_ut_account , JSON:"udo_ut_domain"::string as udo_ut_domain , JSON:"udo_ut_env"::string as udo_ut_env , JSON:"udo_ut_event"::string as udo_ut_event , JSON:"udo_ut_profile"::string as udo_ut_profile , JSON:"udo_ut_version"::string as udo_ut_version , JSON:"firstpartycookies_utag_main__pn"::number as cookie_utag_main__page_number , JSON:"firstpartycookies_utag_main__sn"::number as cookie_utag_main__session_number , JSON:"firstpartycookies_utag_main__ss"::number as cookie_utag_main__session_start_flag , JSON:"firstpartycookies_utag_main__st"::number as cookie_utag_main__sessoin_timeout , JSON:"firstpartycookies_utag_main_ses_id"::number as cookie_utag_main__session_id , JSON:"udo_timing_pathname"::string as timing_pathname , JSON:"udo_timing_dns"::number as timing_dns , JSON:"udo_timing_load"::number as timing_load , JSON:"udo_timing_connect"::number as timing_connect , JSON:"udo_timing_response"::number as timing_response , JSON:"udo_timing_dom_interactive_to_complete"::number as timing_dom_interactive_to_complete , JSON:"udo_timing_front_end"::number as timing_front_end , JSON:"udo_timing_dom_loading_to_interactive"::number as timing_dom_loading_to_interactive , JSON:"udo_timing_query_string"::string as timing_query_string , JSON:"udo_timing_domain"::string as timing_domain , JSON:"udo_timing_fetch_to_interactive":: as timing_fetch_to_interactive , JSON:"udo_timing_timestamp"::number as timing_timestamp , JSON:"udo_timing_fetch_to_complete"::number as timing_fetch_to_complete , JSON:"udo_timing_fetch_to_response"::number as timing_fetch_to_response , JSON:"udo_timing_time_to_first_byte"::number as timing_time_to_first_byte FROM EVENTSTORE_SAMPLE; For detailed information about these fields, see the EventStore Data Guide. Parse AudienceStore Data AudienceStore data can have several variations, each depending on the configuration of the connector actions. In the previous setup steps, you defined your file format for the Snowflake stage as JSON. You can use the following sample query to create a view containing all default visitor badges, dates, strings, numbers and Booleans. CREATE OR REPLACE VIEW TEALIUM_STD_VISITORS AS SELECT JSON:_id::string as "visitor_id" , JSON:metrics."Average visit duration in minutes"::number as "avg_visit_duration" , JSON:metrics."Average visits per week"::number as "avg_visits_per_week" , JSON:metrics."Lifetime event count"::number as "ltm_event_count" , JSON:metrics."Lifetime visit count"::number as "ltm_visit_count" , JSON:metrics."Total direct visits"::number as "total_direct_visits" , JSON:metrics."Total referred visits"::number as "total_referred_visits" , JSON:metrics."Total time spent on site in minutes"::number as "total_time_onsite" , JSON:metrics."Weeks since first visit"::number as "weeks_since_first_visit" , JSON:dates."First visit"::number as "first_visit_date" , JSON:dates."Last visit"::number as "last_visit_date" , JSON:properties."Last event url"::string as "last_event_url" , JSON:properties."Lifetime browser types used (favorite)"::string as "ltm_browser_types_used_fav" , JSON:properties."Lifetime browser versions used (favorite)"::string as "ltm_browser_versions_used_fav" , JSON:properties."Lifetime devices used (favorite)"::string as "ltm_devices_used_fav" , JSON:properties."Lifetime operating systems used (favorite)"::string as "ltm_os_used_fav" , JSON:properties."Lifetime platforms used (favorite)"::string as "ltm_platforms_used_fav" , JSON:badges."Fan"::boolean as "fan_badge" , JSON:badges."Frequent visitor"::boolean as "frequent_visitor_badge" , JSON:badges."Unbadged"::boolean as "unbadged" , ."Returning visitor"::boolean as "returning_visitor_flag" FROM AUDIENCESTORE_SAMPLE; For more advanced parsing of the visitor profile object, see the Snowflake Semi-Structured Data documentation. Additional Resources See the following resources for additional information: Working with AudienceStore and EventStore - Tealium Documentation EventStore Data Guide - Tealium Documentation Preparing to Load Data - Snowflake Documentation Data Loading Considerations - Snowflake Documentation ... 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: Azure Application Insights Added cross-domain tracking and support for the Google Ads Conversion Tracking and Remarketing tag for renaming the (gtag.js) data layer. (Learn more) Updated the Insider InOne tag base URL for  and added support for the partner_id parameter. Updated the FullStory tag to support an event source parameter. Created new version of the Monetate tag. (Learn more) Fixes Corrected issue with event mapping in user interface when using the Facebook Pixel. Corrected rendering issue with drop-down field for the Webtrekk connector that occurred when the Publish to Prod setting was set to Off. Updated the Facebook Pixel tag to allow multiple custom tracking events on same trigger. (Learn more) Updated the Kenshoo Infinity tag base_url  and conversion code. Connectors New/Cool Stuff New marketplace connector: APSIS (Learn more) New marketplace connector: Criteo (hidden) (Learn more) New marketplace connector: Mixmax (Learn more) New marketplace connector: MoEngage (Learn more) New marketplace connector: ONTRAPORT (Learn more) New marketplace connector: Sarbacane (Learn more) New marketplace connector: SendPulse (Learn more) Updated Google DCM Floodlight Batch Connector to increase batch buffer settings to delay API calls. iQ Tag Management Fixes Corrected issue causing parameter fields in Consent Manager to not expand properly when additional fields are viewed or opened. Corrected issue causing yellow notification banner to erroneously display for a different user after switching accounts or profiles. Corrected issue where the data mapping toolbox would not load if a data layer variable was missing the Name property. Corrected issue with merge function that caused unchanged reports, tags, and extensions to display as changed. Universal Data Hub Fixes Applied further updates and enhancements to the new user interface. (Learn more) Corrected issue causing potentially inaccurate EventStream event counts to display in the interface. Corrected permission synchronization issue between TiQ and UDH user permissions. Corrected user interface issue where users could no longer view AudienceStream attributes after deleting a visitor tally (other attributes no affected). Installations Fixes Corrected Lifecycle isFirstLaunch issue in Objective-C. New/Cool Stuff Added sample application to display the use of the current Firebase Remote command for Swift. (Learn more) ... View more

This article describes how to set up the Mixmax connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Create a Contact ✓ ✗ Update a Contact ✓ ✗ Delete a Contact ✓ ✗ Add Contact to a Contact Group ✓ ✗ Remove Contact from a Contact Group ✓ ✗ 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 Your Mixmax API token. For more information on how to generate a token, see: https://developer.mixmax.com/reference#getting-started-with-the-api 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 a Contact Parameters Parameter Description Email Email address for the contact. Unique per contact. If you create a new contact with the same email as an existing contact, this will be merged with that contact. For more information, see: https://developer.mixmax.com/reference#contacts-1 Name Name for the contact. Contact ID Google ID that this contact is associated with, if a contact exists in Google Contacts for this same email address. Salesforce ID Salesforce ID that this contact is associated with, if a contact exists in Salesforce (either contact or a lead) for this same email address. Mark As Used True or false. Meta-field Will increment the contact's usedCount and also set the timestamp to now. Enrich True or false. Meta-field If true, will merge in information from third party sources such as Salesforce if there is a Salesforce account connected and the email address of this contact matches. Meta Contact variables from any source, such as Salesforce, that are used to populate sequences and template variables. Action - Update a Contact Parameters Parameter Description ID The ID for the contact to be updated. For more information, see: https://developer.mixmax.com/reference#contactsid-1 Email The email address for the contact. Name Name for the contact. Contact ID Google ID that this contact is associated with, if a contact exists in Google Contacts for this same email address. Salesforce ID Salesforce ID that this contact is associated with, if a contact exists in Salesforce (either contact or a lead) for this same email address. Meta Contact variables from any source, such as Salesforce, that are used to populate sequences and template variables. Action - Delete a Contact Parameters Parameter Description ID ID of the contact to be deleted. For more information, see: https://developer.mixmax.com/reference#contactsid-2 Action - Add Contact to a Contact Group Parameters Parameter Description Contact Group ID The ID of the Contact Group the Contact will be added to. For more information, see: https://developer.mixmax.com/reference#contactgroupsidcontacts-1 Email Email of the contact to add. Resolves the email to a contact owned by the user. Either Email or Contact ID must be defined. Contact ID The ID of the contact to add to the group. Either Email or Contact ID must be defined. Name Name for the contact. Meta Contact variables from any source, such as Salesforce, that are used to populate sequences and template variables. Action - Remove Contact from a Contact Group Parameters Parameter Description Contact Group ID The ID of the Contact Group the Contact will be removed from. For more information, see: https://developer.mixmax.com/reference#contactgroupsidcontactscontactid Contact ID The ID of the contact to remove from the group. ... View more

This article describes how to set up the APSIS connector in your Customer Data Hub account. In this article: Connector Actions Action Name AudienceStream EventStream Create Subscriber and Add to Mailing List (Queued) ✓ ✗ Update Subscriber (Queued) ✓ ✗ Add Subscriber to Mailing List ✓ ✗ Remove Subscriber from Mailing List ✓ ✗ Delete Subscriber (Queued) ✓ ✗ Send Transactional 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 Key To get an API key, log in to your APSIS Pro account and select the Account section. Find the API Keys link and click to generate a new API key. One account can have multiple API keys. You can manage your keys using the Account Settings section in APSIS Pro. For more information, see APSIS: Getting Started 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 Subscriber and Add to Mailing List (Queued) Batch Limits This action uses batched requests to support high-volume data transfers to the vendor. Requests are queued until one of the following three (3) thresholds is met: Max number of requests: 10 Max time since oldest request: 1 minutes Max size of requests: 1 MB Parameters Parameter Description Mailing List The ID of the list the subscriber should be added to. If you know mailing list ID, you can enter it as Custom Value. Select the list the subscriber should be added to, or provide list ID directly. For more information, see SubscriberService.CreateSubscriber. Create Mode If the subscriber's account already exists and this parameter is set to "Create or Update", then the subscriber's data will be updated. It is not possible to update existing subscriber when subscribing with double opt-in. Country code The subscriber's country code. Desired format The subscriber's desired format. Email address Required. The subscriber's email address. External ID The subscriber's external ID. Name The name of the subscriber. Password The subscriber's password. Phone number The subscriber's phone number. Demographic Data The subscriber's list of demographic data fields. The keys and possible values of data fields are defined in the APSIS account management console. Template Variables Optional. Provide template variables for Demographic Data. For more information, see Template Variables Guide Name nested template variables with the dot notation. Example: items.name Nested template variables are typically built from data layer list attributes. Templates Optional: provide templates to be referenced in Demographic Data. For more information, see Templates Guide. Templates are injected by name with double curly braces into supported fields. Example: {{SomeTemplateName}} Action - Update Subscriber (Queued) Batch Limits This action uses batched requests to support high-volume data transfers to the vendor. Requests are queued until one of the following three (3) thresholds is met: Max number of requests: 10 Max time since oldest request: 1 minutes Max size of requests: 1 MB Parameters Parameter Description Country code The subscriber's country code. Desired format The subscriber's desired format. Email address Required. The subscriber's email address Name The name of the subscriber. Password The subscriber's password. Phone number The subscriber's phone number. User ID The subscriber's ID. For more information, see Update Subscribers Demographic Data The subscriber's list of demographic data fields. The keys and possible values of data fields are defined in the account management console. Template Variables Optional. Provide template variables for Demographic Data. For more information see Template Variables Guide. Name nested template variables with the dot notation. Example: items.name Nested template variables are typically built from data layer list attributes. Templates Optional: provide templates to be referenced in Demographic Data. For more information see Template Variables Guide. Templates are injected by name with double curly braces into supported fields. Example: {{SomeTemplateName}} Action - Add Subscriber to Mailing List Parameters Parameter Description Mailing List Select the list the subscriber should be added to, or provide list ID directly. For more information, see SubscriberService.CreateSubscriber. If you know mailing list ID, you can enter it as Custom Value Subscriber's Email Required. The subscriber's email address Subscriber's ID The subscriber's ID. For more information, see Update Subscribers Action - Remove Subscriber from Mailing List Parameters Parameter Description Mailing List Select the list the subscriber should be added to, or provide list ID directly. For more information, see SubscriberService.CreateSubscriber. If you know mailing list ID, you can enter it as Custom Value Subscriber's Email Required. The subscriber's email address Subscriber's Id The subscriber's ID. For more information, see Update Subscribers Action - Delete Subscriber (Queued) Batch Limits This action uses batched requests to support high-volume data transfers to the vendor. Requests are queued until one of the following three (3) thresholds is met: Max number of requests: 10 Max time since oldest request: 1 minutes Max size of requests: 1 MB Parameters Parameter Description Subscriber's Email Required. The subscriber's email address Action - Send Transactional Email Parameters Parameter Description Transactional Project Select the transactional project. ID of the project. For more information, see Send Transactional Email Disable inactive projects True or false indicating if sending should be allowed when project is inactive Default value is true. Country code The subscriber's country code. Demographic data for HTML The subscriber's list of demographic data fields. The keys and possible values of data fields are defined in the APSIS account management console. Desired format The subscriber's desired format. Email address Required. The subscriber's email address External ID The subscriber's external ID. Name The name of the subscriber. Phone number The subscriber's phone number. Send Date Send date. Sending Type Possible values: m - marketing t - transactional (default) Demographic Data The subscriber's list of demographic data fields. The keys and possible values of data fields are defined in the APSIS account management console. Template Variables Optional. Provide template variables for Demographic Data. For more information, see Template Variables Guide. Name nested template variables with the dot notation. Example: items.name Nested template variables are typically built from data layer list attributes. Templates Optional: provide templates to be referenced in Demographic Data. For more information, see Templates Guide. Templates are injected by name with double curly braces into supported fields. Example: {{SomeTemplateName}} ... View more

This article describes how to set up the Ontraport connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Create a Contact ✓ ✗ Update a Contact ✓ ✗ Delete a 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: API key In order to get started making requests on our API, you must obtain a unique API key and App ID. These credentials can be requested in your Administration settings. For more information, see Ontraport Introduction. App ID In order to get started making requests on our API, you must obtain a unique API key and App ID. These credentials can be requested in your Administration settings. For more information, see Ontraport Introduction. 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 a Contact Parameters Parameter Description First Name String. The contact's first name. For more information, see Create a Contact. Last Name String. The contact's last name. Email String. The contact's email address. F-Referrer Integer (number). The affiliate ID of the first affiliate to refer the contact. L-Referrer Integer (number). The affiliate ID of the last affiliate to refer the contact. Address String. The contact's postal address. Address 2 String. A second address field which is generally used for storing suite or unit numbers. City String. The contact's city. State String. The contact's state. Zip String. The contact's postal code. Country String. The contact's country. Birthday Timestamp (number). The contact's birthday, measured in seconds from the Unix Epoch. Priority Integer (number). The contact's priority. High = > 8 Medium = > 9 Low = > 10 None = > 0 Status Integer (number). The contact's Sales Stage. 1 = > Closed - Lost 2 = > Closed - Won 3 = > Committed 4 = > Consideration 5 = > Demo Scheduled 6 = > Qualified Lead 7 = > New Prospect Cell Phone String. The contact's mobile phone number. Home Phone String. The contact's home phone number. SMS Number String. The mobile number where the contact prefers to receive text messages. Office Phone String. The contact's office phone number. Fax String. The contact's fax number. Company String. The company the contact is affiliated with. Title String. The contact's job title. Website String. The contact's website. Bulk Mail Integer (number). A flag that indicates a contact's bulk email status.  0 = > Transactional Only  1 =  > Opted-in 2 = > Double opt-in -2 = > hard bounce -5 = > Under review You can only set the value to zero (0) through the API. You cannot manually opt-in a contact who has opted to receive only transactional mail. Bulk SMS Integer (number). A flag that indicates whether or not a contact is opted in to receive bulk texts.   0 = > Opted-out  1 = > Opted-in  2 = > Double opt-in -2 = > hard bounce You can only set the value to 0 through the API. You cannot manually opt-in a contact who has opted out. New Lead Source Integer/string. The lead source for the first tracking URL the contact arrived from. This field accepts the lead source name if use UTM Names has a value of true, and ID if it is not passed or has a value of false UTM variables passed by name will be created if they do not exist. New Content integer/string. The content for the first tracking URL the contact arrived from. This field accepts the contact name if use UTM Names has a value of true, and ID if it is not passed or has a value of false. UTM variables passed by name will be created if they do not exist. New Medium Integer/string. The medium for the first tracking URL the contact arrived from. This field accepts the medium name if use UTM Names has a value of true, and ID if it is not passed or has a value of false. UTM variables passed by name will be created if they do not exist. New Campaign Integer/string. The tracking campaign for the first tracking URL the contact arrived from. This field accepts the tracking campaign name if use UTM Names has a value of true, and ID if it is not passed or has a value of false. UTM variables passed by name will be created if they do not exist. New Term Integer/string. The term for the first tracking URL the contact arrived from. This field accepts the tracking campaign name if use UTM Names has a value of true, and ID if it is not passed or has a value of false. UTM variables passed by name will be created if they do not exist. Last Lead Source Integer/string. The lead source for the last tracking URL the contact arrived from. This field accepts the lead source name if use UTM Names has a value of true, and ID if it is not passed or has a value of false. UTM variables passed by name will be created if they do not exist. Last Content Integer/string. The content for the last tracking URL the contact arrived from. This field accepts the content name if use UTM Names has a value of true, and ID if it is not passed or has a value of false. UTM variables passed by name will be created if they do not exist. Last Medium Integer/string. The medium for the last tracking URL the contact arrived from. This field accepts the medium name if use UTM Names has a value of true, and ID if it is not passed or has a value of false. UTM variables passed by name will be created if they do not exist. Last Campaign Integer/string. The tracking campaign for the last tracking URL the contact arrived from. This field accepts the tracking campaign name if use UTM Names has a value of true, and ID if it is not passed or has a value of false. UTM variables passed by name will be created if they do not exist. Last Term Integer/string. The term for the last tracking URL the contact arrived from. This field accepts the tracking campaign name if use UTM Names has a value of true, and ID if it is not passed or has a value of false. UTM variables passed by name will be created if they do not exist. Use UTM Names True or false. Used to indicate that UTM variables will be passed by name rather than ID. Defaults value is false. Referral Page String. The page the contact was referred from. Affilliate Sales Integer (number). If the contact is an affiliate, the total number of affiliate sales. Affiliate Amount Double (string). If the contact is an affiliate, the total amount of affiliate sales. Program ID Integer (number). For affiliates, the partner program ID. Affiliate Paypal String. Affiliate email address for PayPal payments. Timezone String. The contact's timezone. Number Purchased Integer (number). The contact's total orders. Action - Update a Contact Parameters Parameter Description Contact ID The ID of the contact to update is required. The other fields should only be used if you want to change the existing value. For more information, see Update a Contact. First Name String. The contact's first name. Last Name String. The contact's last name. Email String. The contact's email address. F-Referrer Integer (number). The affiliate ID of the first affiliate to refer the contact. L-Referrer Integer (number). The affiliate ID of the last affiliate to refer the contact. Address String. The contact's postal address. Address 2 String. A second address field which is generally used for storing suite or unit numbers. City String. The contact's city. State String. The contact's state. Zip String. The contact's postal code. Country String. The contact's country. Birthday Timestamp (number). The contact's birthday, measured in seconds from the Unix Epoch. Priority Integer (number). The contact's priority. High = > 8 Medium = > 9 Low = > 10 None = > 0 Status Integer (number). The contact's sales stage. 1 = > Closed - Lost 2 = > Closed - Won 3 = > Committed 4 = > Consideration 5 = > Demo Scheduled 6 = > Qualified Lead 7 = > New Prospect Cell Phone String. The contact's mobile phone number. Home Phone String. The contact's home phone number. SMS Number String. The mobile number where the contact prefers to receive text messages. Office Phone String. The contact's office phone number. Fax String. The contact's fax number. Company String. The company the contact is affiliated with. Title String. The contact's job title. Website String. The contact's website. Bulk Mail Integer (number). A flag that indicates a contact's bulk email status.   0 = > Transactional Only  1 = > Opted-in  2 = > Double opt-in -2 = > hard bounce -5 = > Under review You can only set the value to 0 through the API. You cannot manually opt-in a contact who has opted to receive only transactional mail. Bulk SMS Integer (number). A flag that indicates whether or not a contact is opted in to receive bulk texts.   0 = > Opted-out  1 = > Opted-in  2 = > Double opt-in -2 = > hard bounce You can only set the value to 0 through the API. You cannot manually opt-in a contact who has opted out. New Lead Source Integer/string. The lead source for the first tracking URL the contact arrived from. This field accepts the lead source name if use UTM Names has a value of true, and ID if it is not passed or has a value of false. UTM variables passed by name will be created if they do not exist. New Content integer/string. The content for the first tracking URL the contact arrived from. This field accepts the contact name if use UTM Names has a value of true, and ID if it is not passed or has a value of false. UTM variables passed by name will be created if they do not exist. New Medium Integer/string. The medium for the first tracking URL the contact arrived from. This field accepts the medium name if use UTM Names has a value of true, and ID if it is not passed or has a value of false. UTM variables passed by name will be created if they do not exist. New Campaign Integer/string. The tracking campaign for the first tracking URL the contact arrived from. This field accepts the tracking campaign name if use UTM Names has a value of true, and ID if it is not passed or has a value of false UTM variables passed by name will be created if they do not exist. New Term Integer/string. The term for the first tracking URL the contact arrived from. This field accepts the tracking campaign name if use UTM Names has a value of true, and ID if it is not passed or has a value of false. UTM variables passed by name will be created if they do not exist. Last Lead Source Integer/string. The lead source for the last tracking URL the contact arrived from. This field accepts the lead source name if use UTM Names has a value of true, and ID if it is not passed or has a value of false. UTM variables passed by name will be created if they do not exist. Last Content Integer/string. The content for the last tracking URL the contact arrived from. This field accepts the content name if use UTM Names has a value of true, and ID if it is not passed or has a value of false. UTM variables passed by name will be created if they do not exist. Last Medium Integer/string. The medium for the last tracking URL the contact arrived from. This field accepts the medium name if use UTM Names has a value of true, and ID if it is not passed or has a value of false. UTM variables passed by name will be created if they do not exist. New Campaign Integer/string. The tracking campaign for the first tracking URL the contact arrived from. This field accepts the tracking campaign name if use UTM Names has a value of true, and ID if it is not passed or has a value of false UTM variables passed by name will be created if they do not exist. Last Term Integer/string. The term for the last tracking URL the contact arrived from. This field accepts the tracking campaign name if use UTM Names has a value of true, and ID if it is not passed or has a value of false. UTM variables passed by name will be created if they do not exist. Use UTM Names True or false. Used to indicate that UTM variables will be passed by name rather than ID. Defaults value is false. Referral Page String. The page the contact was referred from. Affilliate Sales Integer (number) If the contact is an affiliate, the total number of affiliate sales. Affiliate Amount Double (string). If the contact is an affiliate, the total amount of affiliate sales. Program ID Integer (number). For affiliates, the partner program ID. Affiliate Paypal String. Affiliate email address for PayPal payments. Timezone String. The contact's timezone. Number Purchased Integer (number). The contact's total orders. Action - Delete a Contact Parameters Parameter Description Contact ID ID of the contact to be deleted. For more information, see Delete a Specific Contact. ... View more

This article describes how to set up the Sarbacane connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add or Edit a Contact ✓ ✗ Add Recipients to a Campaign ✓ ✗ 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: Account ID For more information about your Account ID, see: https://developers.sarbacane.com/#authentification API key For more information about your API key, see: https://developers.sarbacane.com/#authentification 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 Edit a Contact Parameters Parameter Description List ID ID of the list concerned. For more information, see: https://developers.sarbacane.com/#ajouter-modifier-un-contact Email The email of the contact. Must use either email and/or phone. Phone Phone number of the contact. Must use either email and/or phone. Field ID's Key:value pairs of ID's of columns and values to be added to those columns. For more information on how to retrieve or add column ID's, see: https://developers.sarbacane.com/#lister-les-champs-personnalises Action - Add Recipients to a Campaign Parameters Parameter Description Campaign ID ID of the campaign For more information, see: https://developers.sarbacane.com/#ajouter-des-destinataires Email The email of the contact. Must use either email and/or phone. Phone Phone number of the contact. Must use either email and/or phone. ... View more

This article describes how to set up the MoEngage connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add/Modify User Information ✓ ✓ 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 Data API ID. See https://docs.moengage.com/docs/data-import-apis#section-authentication Password Data API 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 - Add/Modify User Information Parameters Parameter Description Customer ID The unique identifier which is set and passed on from MoEngage SDK. For more information, see: https://docs.moengage.com/docs/data-import-apis#section-addmodify-user-information Name The name of the user you are updating. First Name First name of the user. Last Name Last name of the user. Email Email of the user. Age Age of the user. Gender Male or female. Case-sensitive. Mobile Phone number of the user. Geography Location of the user, latitude and longitude (- lat,lng). Must be an array of numbers attribute type. Source Acquisition source of the user. Created Time User created time. Last Seen User last seen time. Transactions Number of transactions by the user. Revenue Lifetime value of the user. Platform The current platform on which the user is interacting with the system, such as Android, Windows, iOS, etc. ... View more

This article describes how to set up the SendPulse connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add Email to Mailing List (single opt-in) ✓ ✗ Add Email to Mailing List (double opt-in) ✓ ✗ Delete Email from Mailing List ✓ ✗ 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: Client ID See https://sendpulse.com/integrations/ap authorization for information about your OAuth2 credentials. Client Secret Required. Provide your web application client secret. 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 Email to Mailing List (single opt-in) Parameters Parameter Description List ID ID of the mailing to list to which you are adding the user. For more information, see: https://sendpulse.com/integrations/api/bulk-email Email Email address of the user to be added to the list. Action - Add Email to Mailing List (double opt-in) Parameters Parameter Description List ID ID of the mailing to list to which you are adding the user. For more information, see: https://sendpulse.com/integrations/api/bulk-email Sender Email Your sender email. Sender email address must be activated in your SendPulse account in Email-Service settings-From address menu. Email Email address of the user to be added to the list. Action - Delete Email from Mailing List Parameters Parameter Description List ID ID of the list from which you are deleting the contact. For more information, see: https://sendpulse.com/integrations/api/bulk-email Email Email address to be deleted from list. ... 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: Knotch Updated the Floodlight (gtag.js) tag to add support for "purchase-details". (Learn more) Updated the Google Analytics (gtag.js) tag to allow configuration set method in a link event. Updated to the Tealium Collect tag to abide by Interactive Advertising Bureau (IAB) consent settings when present. Fixes Updated the Adobe Analytics AppMeasurement tag for JS to support mapping to linkName and linkType for AppMeasurement, Versions 2.12.0 and later. Updated the Facebook Pixel tag to normalize case in advanced matching unless the item being matched is recognized. (Learn more) Connectors New/Cool Stuff New marketplace connector: Adestra (Learn more) New marketplace connector: Eloqua Custom Objects (Learn more) New marketplace connector: Enchant (Learn more) New marketplace connector: Infobip (Learn more) New marketplace connector: LeadSquared (Learn more) New marketplace connector: LeanPlum (Learn more) New marketplace connector: Mocean (Learn more) New marketplace connector: DCM Floodlight (Learn more) New marketplace connector: Google Adwords Customer Match. (Learn more) Updated and replaced the existing Cordial connector. (Learn more) Updated the DialogOne connector to latest version. (Learn more) Updated the Optimizely Events connector to latest version. (Learn more) Updated the Selligent connector to add custom attributes for the Add to Action List and Trigger Campaign actions. Updated the Selligent connector to use REST calls and Auth mechanism in Data-Distributor in order to support returning 500 items per HTTP call (increased from 200 to 500). Fixes Updated the Optimizely Events connector to correct API link listed in Tool Tips to generate a token and updated the logo for all Optimizely connectors. (Learn more) Corrected issue with the Google AdWords Customer Match connector causing a VendorApiException error. Deprecated the Twitter Tailored Audiences connector. Corrected the Facebook Offline Conversations connector to enable AudienceStream support.  (Learn more) Updated the Webtrekk connector to exclude empty values from the API call. (Learn more) iQ Tag Management New/Cool Stuff Introduced the new unified interface. (Learn more) Fixes Updated message text returned when an incorrect email address entered at login to ensure that the email address is properly masked. Users entering five (5) unsuccessful two-factor authentication (2FA) codes with a valid username and password are now locked out for 10 minutes before they can retry. Universal Data Hub New/Cool Stuff Introduced the new unified user interface. (Learn more) Updated AudienceStream options to expose relevant profile settings to the Admin user. Fixes Corrected issue in new rule editor that did not allow the number zero (0) as a string literal entry. Corrected issue in the display of the rule modal where drop-down values appeared incorrectly when adding a new attribute (display issue only). Corrected issue that caused rules assigned within enrichments to be assigned to all enrichments in an attribute instead of the expected behavior of only assigning to the enrichment that is being worked on. Corrected an issue on the rules screen causing the loading status to stick at 65%. Updated file import data source to accept Microsoft MIME file types for .csv file imports. Installations Fixes Corrected issue with React Native on mobile by updating to the Version 1.0.4 fixes for possible null activity and other null checks in Consent Manager methods. ... View more

This connector is now deprecated and no longer available in the tag marketplace. The underlying Google AdWords API is planning to be retired on April 27, 2022. Learn more from the Google Ads Developer Blog. You need to replace your existing Google AdWords connectors with the updated Google Ads Customer Match connector. This article describes how to set up the Google AdWords Customer Match (Customer-Provided Credentials and Tealium-Provided Credentials) connectors. In this article: Table of Contents Placeholder Requirements There are two types of Google AdWords Customer Match Connectors. Ensure that you select the appropriate one when adding the connector. Google Adwords Customer Match (Customer-Provided Credentials) Requires Google approval. Google Adwords Customer Match (Tealium-Provided Credentials) Tealium has been pre-approved to handle volume, bypassing your need to go through the application process. API Information This connector uses the following vendor API: API Name: Google Audience Partner API DmpUserListService API Version: v201809 API Endpoint: https://ddp.googleapis.com/ Documentation: AdWords API Batch Limits This connector uses batched requests to support high-volume data transfers to the vendor. Requests are queued until one of the following three (3) thresholds is met: Max number of requests: 100000 Max time since oldest request: 60 minutes Max size of requests: 100 MB Connector Actions Action Name AudienceStream EventStream Add User to Remarketing List ✓ ✓ Remove User from Remarketing List ✓ ✓ 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: AdWords Customer ID Required Provide the Adwords account Customer ID to manage. Developer Token Required Provide the API developer token that has been approved by Google to make production volume API requests. Obtaining and approving a developer token is a multi-step process that you will need to own and manage. To get started, click here. 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 Remarketing List Parameters Parameter Description Remarketing List Select a remarketing user list to add user to. For more information, see: Remarketing and Audience Targeting. Available options contain only user lists of first party CRM data type. User Identifier Required. Map applicable user identifier. For additional information, see: Remarketing and Audience Targeting. Required fields depend on the list type selected, as follows: Contact Info ( CONTACT_INFO ) Minimum Required: Email, Phone Number or All Address information. Email, Phone Number, First and Last Name must be trimmed of whitespace, lowercased and SHA-256 encoded. If mapped values are plain text, check the Contact Info Hash check box in the optional section. Country Code must follow the 2-letter ISO-3166 Alpha-2 format. CRM ( CRM_ID ) Required User ID Advertiser generated and accessible to whitelisted clients only. Mobile Advertising ( MOBILE_ADVERTISING_ID ) Required Mobile ID Mobile Device ID (advertising ID/IDFA). Contact Info Hash Optional Check if mapped contact information is in plain text. Values are automatically SHA-256 hashed. Action - Remove User from Remarketing List Parameters Parameter Description Remarketing List Select a remarketing user list to remove user from. For more information, see: Remarketing and Audience Targeting. Available options contain only user lists of first party CRM data type. User Identifier Required. Map applicable user identifier. For additional information, see: Remarketing and Audience Targeting. Required fields depend on the list type selected, as follows: Contact Info ( CONTACT_INFO ) Minimum Required: Email, Phone Number or All Address information. Email, Phone Number, First and Last Name must be trimmed of whitespace, lowercased and SHA-256 encoded. If mapped values are plain text, check the Contact Info Hash check box in the optional section. Country Code must follow the 2-letter ISO-3166 Alpha-2 format. CRM ( CRM_ID ) Required User ID Advertiser generated and accessible to whitelisted clients only. Mobile Advertising ( MOBILE_ADVERTISING_ID ) Required Mobile ID Mobile Device ID (advertising ID/IDFA). Contact Info Hash Optional Check if mapped contact information is in plain text. Values are automatically SHA-256 hashed. ... View more

This article describes how to set up the ActiveCampaign connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add New Contact ✓ ✗ Add Tags to Contact ✓ ✗ Add Contact to Automation ✓ ✗ 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 URL Go to ActiveCampaign and click Settings > Developer. For more information, see: ActiveCampaign Documentation. API Key Go to ActiveCampaign and click Settings > Developer. 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 New Contact Parameters Parameter Description Email Email of the new contact. for example, 'test@example.com'. List ID Assign a contact to a list. Specify the integer value of the list, for example, 12345. Additional Fields Optional. Include additional data about the contact. For a list of available fields, see: https://www.activecampaign.com/api/example.php?call=contact_add. Action - Add Tags to Contact Parameters Parameter Description Email Email of the new contact, for example 'test@example.com'. Tags Tags to add to the contact. Pass a string for one tag, an array (set of strings) for multiple tags, or a comma-separated list of custom values. Action - Add Contact to Automation Parameters Parameter Description Contact Email Email of the new contact, for example, 'test@example.com'. Automation IDs The automation IDs to add the contact to. You may use multiple, comma-separated values. ... View more

This article describes how to set up the LeadSqared connector in your Customer Data Hub account. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Create or Update a Lead ✓ ✗ 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: Host Your API host is dependent on the region your account was created and could be one of the following: api.leadsquared.com (for accounts created in Singapore region) api-us11.leadsquared.com (for accounts created in US region) api-in21.leadsquared.com (for accounts created in India region) To find your API host, navigate to My Account > Settings > API and Webhooks. For more information, see: LeadSquared API Host Access key Every API call requires an access key and secret key to be passed in the API URL for authentication. Any action performed using APIs uses the credentials of the user whose keys are passed. The accessKey and secretKey can be obtained from the My Account > Settings > API and Webhooks section. For more information, see: LeadSquared Authentication 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 - Create or Update a Lead Parameters Parameter Description Attributes Pass as many lead fields (including custom fields) as you want, but be sure to pass at least one of the following: FirstName LastName EmailAddress* Phone* *These fields are unique by default. It is therefore recommended to pass at least one of them while creating a lead. If you want to change your unique field settings, navigate to My Account  >  Settings > Customization > Lead Fields and click the wheel icon beside a lead field to mark or remove uniqueness. The email address and phone fields are used as the default search criteria. If none of these match with an existing lead, a new lead will be created. You can pass the “SearchBy” attribute to search by a particular parameter. For more information, see https://apidocs.leadsquared.com/create-or-update/ ... View more

This article describes how to set up the Infobip connector in your Customer Data Hub account. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send SMS ✓ ✗ Send Push Notification ✓ ✗ 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: Your Infobip username. For more information, see: Infobip Security and Authorization Password: Your Infobip password. 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 SMS Parameters Parameter Description From Represents sender ID and it can be alphanumeric or numeric. Alphanumeric sender ID length should be between 3 and 11 characters. Example: CompanyName . Numeric sender ID length should be between 3 and 14 characters. For more information, see: https://dev.infobip.com/send-sms/single-sms-message To Message destination address. Destination addresses must be in international format. Example: 41793026727 Text Text of the message that will be sent. Action - Send Push Notification Parameters Parameter Description From PUSH Application Code you are using to send messages. Application Code is the application identifier that links your mobile application to the application profile created in Infobip Platform. It is required to insert the Application Code in Mobile Messaging SDK configuration once you implement it in your mobile application. For more information, see: Send Single Push Notification Push Registration ID Push Registration Id is a unique ID that identifies application instance and specific device. Include only one of the following: Push Registration ID External User ID Phone Number Email External User ID External user ID set in User Profile. Phone Number MSISDN in international format. Eample: 41793026727 Email Email of the user if it is provided in user profile. Text Text of the message that will be sent. Sent At Used for scheduled Push notifications. Message will be sent at scheduled time. Custom Payload Additional data that can be delivered with the Push message. Notification Options JSON object that contains notification options. Validity Period The message validity period, expressed in hours. When the period expires, it will not be allowed for the message to be sent or the message will be canceled if it is pending in Cloud (APNS or FCM). The default value is 48 hours. Minimum value is 30 seconds. Maximum value is 72 hours. Notify URL The URL on your callback server on which the Delivery report will be sent. For more information, see: https://dev.infobip.com/push-messaging/delivery-reports-on-notify-url Callback Data Additional client data that will be sent on the Notify Url. The maximum value is 200 characters. Target Only Primary Devices Set to true to only send messages to push devices that are marked as primary devices. By default, messages will be sent to all targeted devices, including both primary and non-primary. ... View more

This article describes how to set up the Mocean connector in your Customer Data Hub account. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send SMS ✓ ✗ 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 Key: Your account API key. For more information, see: Mocean Authentication API Secret: Your account API secret. 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 SMS Parameters Parameter Description From SMS Sender ID (also referred as to SMS Sender Name) is the information that is displayed to the recipient as the sender of the SMS when a message is received at a mobile device. For more information, see: https://moceanapi.com/docs/?shell#sms-api To Telephone number of the receiver. To send to multiple receivers, separate each entry with white space (‘ ’) or comma (,). Telephone number must include country code, for example, a Malaysian phone number would be 60123456789 . Text Contents of the message. If you are sending binary content, this will be a hex string. User Data Header User Data Header part of the message. For example, 0605040B8423F0 . Coding Sets the coding scheme bits in DCS field. Accepts the following values: 1 for 7-bit 2 for 8-bit 3  for UCS2   If unset, the value defaults to 7 bits unless a mocean-udh is defined, which sets coding to 8 bits. If the charset is not set or is not set to UTF-8 when non-GSM character is detected, coding will set to UCS2. Delivery Report Request for delivery reports with the state of the sent message. To enable delivery reports, set this value to ‘ 1 ’. If this field is not specified, the default value will be ‘ 0 ’ and no DLR will be returned. Delivery Report URL URL to receive delivery reports. Required if DLR is requested. Schedule When this field is used, the message is sent out on the specified date time (on best effort basis due to large number of SMS is queued for scheduling). The format of the date time is YYYY-MM-DD hh:mm:ss  in 24-hours format. Example:  2007-02-11 23:30:00 The wrong date format will cause the gateway to reject the request. Use Malaysia time (or GMT +8:00) while making scheduled SMS request. Charset Indicates the character set used in the Text parameter. Supported character sets are: ISO-8859-1 ISO-8859-7 UTF-8 Windows-1252 Validity Defines the validity period of message. User has to input validity in terms of seconds. For example, if user wants a message to expire after 5 minutes upon submission, user has to configure validity value as 300 (seconds). ... View more

This article describes how to set up the Enchant connector in your Customer Data Hub account. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Create a New Customer ✓ ✗ Update a Customer ✓ ✗ Create a 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: Access token To get an access token, install the API app from the apps tab of your help desk settings. Each instance of the API application has it's own access token. For more information, see: Enchant Rest API 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 a New Customer Parameters Parameter Description First name First name of the customer. For more information on this endpoint, see: https://dev.enchant.com/api/v1#customers Last name Last name of the customer. Summary Custom summary information. Action - Update a Customer Parameters Parameter Description Customer ID ID of the customer. For more information on this endpoint, see: https://dev.enchant.com/api/v1#customers First name First name of the customer. Last name Last name of the customer. Summary Custom summary information. Action - Create a Contact Parameters Parameter Description Customer ID ID of the customer. For more information on this endpoint, see: https://dev.enchant.com/api/v1#contacts Type Either "email" or "twitter." Value Email or Twitter value. ... View more

This article describes how to set up the Facebook Conversions connector in your account. In this article: Prerequisites The Facebook Conversions connector requires: The client-side Facebook Pixel tag running in the web browser. Learn more in the Facebook Help Center. For Facebook Pixel to work with the Facebook Conversions connector, enable the Tealium partner integration in your Facebook Ads account settings as follows: Log into your Facebook Ads Manager account and click Events Manager from the menu. In the menu, select Data Sources, then select the Pixel and click the Settings tab. Scroll down to the Server-Side API section. In the Partner Integration section, click Choose a Partner. Select Authorize Tealium Connection, and click Continue to enable Tealium. If you do not see the option to toggle a partner integration, contact your Tealium Account Manager for support. API Information This connector uses the following vendor API: API Name: Facebook Graph API - Facebook Pixel API Version: v12.0 API Endpoint: https://graph.facebook.com 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: Pixel ID For your Facebook Pixel to work, ensure that you have followed the steps outlined in the Facebook Server-Side Events Connector Setup Guide to enable the partner integration for your Facebook pixel. For additional information, see the Facebook Pixel Setup Guide. Test Connection If your pixel has been whitelisted and enabled for Tealium, a TealiumTestConnector event is tracked on your pixel. Click Test Connection to send a test event named TealiumConnectorTest. Check the Facebook Events Manager Pixel Overview to confirm the event was received. If your test fails, double check the steps described in the Facebook Server-Side Events Connector Setup Guide. Action Settings - Parameters and Options Click Next or click the Actions tab. You configure connector actions in the Actions tab. This section describes how to set up parameters and options for each action. Deduplication for Facebook Pixel and Facebook Conversions API for Web Events To configure this connector action to receive event IDs from the Facebook Pixel tag in your iQ Tag Management account, look for event attributes using the following naming convention: fb_event_id_<Facebook Event>_<Tag UID> For example: fb_event_id_Purchase_32 or fb_event_id_PageView IDs were previously generated as fb_event_id_<Facebook Event> . These IDs continue to be generated but are considered legacy. The new IDs allow for use with multiple Facebook tags firing on a single page and offer a stronger tie back to the related tag. If you are using the legacy version, you must change the connector to the new ID. Use a separate action for each type of event ID. Map the event-specific event ID attribute to Event ID with the matching event name mapped to Event Name. For example: Tealium Attribute/Value Facebook Parameter fb_event_id_Purchase Event ID "Purchase" (Custom Text) Event Name See the Facebook Pixel Tag Setup Guide. Automatic Deduplication When the Automatic Deduplication value is populated, the connector will look for the corresponding variable within the UDO object. You are no longer required to add an Event ID if this section is populated and you are using Tealium iQ. However, the following approach may still be needed when using EventStream without TealiumiQ. The connector uses the following order of operations: If Automatic Deduplication is populated, and the value is found in the data layer, (for example, fb_event_id_ViewContent_30 ) this value will supersede anything mapped in Event ID If Automatic Deduplication is populated, but it can’t find the tag ID version, but can find the legacy version (with no ID attached), we will use that value (for example, fb_event_id_ViewContent ). If Automatic Deduplication is populated, but we can’t find any value, we will use the mapped Event ID, if it is populated. Action - Send Event Parameters For User Data parameters, the following table notes the level of importance for each parameter. The importance level describes the parameter's influence on your event match quality. For example, Email (em) has the Highest level of importance while Phone Number (ph) has an importance level of High. Parameter Description Event Source URL Optional. Required if the Action Source is set to website. The browser URL where the event happened. EventStream If the Action Source is set to website and this field is not mapped, it is automatically mapped to the attribute Current URL in EventStream. AudienceStream If the Action Source is set to website and this field is not mapped, it is automatically mapped to the attribute Last Event URL in AudienceStream. Test Event Code Optional. Send the test ID as a test_event_code parameter to start seeing event activity appear in the Test Events window. Events sent with test_event_code are not dropped, instead they flow into Events Manager and are used for targeting and ads measurement purposes. Data Processing Options Required. Map value to LDU to have Facebook process event with Limited Data Use restrictions. Otherwise map None to specify that the event should not be processed with Limited Data Use restrictions. For more information, see Facebook Data Processing Options. Event Name Required. A Facebook pixel standard event name. Debugging Level Optional. Specifies the trace level for the event. 1 for Error 2 for Info 3 for Debug Action Source Required. This field allows you to specify where your conversions occurred. Valid action sources are: email website app phone_call chat physical_store system_generated other Pixel ID Override Optional String Can be used to override the value used for the initial connector configuration. If not provided, the Pixel ID from the connector configuration will is used. Data Processing Options Country Required if Data Processing Options is mapped to LDU. Map country code associated with user event. Accepted code values: 1 for the United States of America 0 to request country to be geolocated by Facebook Geolocation also requires mapping the Client IP Address attribute. Event ID Optional. An ID used by Facebook to de-duplicate the same event sent from both server and browser. Verify this is an ID unique to one pair of events sent from browser and server. Event Time Optional. A Unix timestamp in seconds indicating when the actual event occurred (auto-populated at execution time if absent). Data Processing Options State Required if Data Processing Options is mapped to LDU. Map state code associated with user event. Accepted code values: 1000 for California 0 to request state to be geolocated by Facebook Geolocation also requires also mapping the Client IP Address attribute. Opt Out Optional. A flag indicating to not use this event for ads delivery optimization. Set this to true to only use the event for attribution. Zip (zip) Postal zip code. Example: 94035 Importance: Medium FB Login ID ID issued by Facebook when a person first logs into an instance of an app. This is also known as the App-Scoped ID. Do not hash. Client User Agent (ua) Optional. Required if the Action Source is set to website. The user agent for the browser corresponding to the event. Do not hash. EventStream If the Action Source is set to website and this field is not mapped, it is automatically mapped to the attribute User Agent in EventStream. AudienceStream If the Action Source is set to website and this field is not mapped, it is automatically mapped to the vistor's last User Agent in AudienceStream. Importance: High Client IP Address (ip) Do not hash. The IP address of the browser corresponding to the event. Tealium can capture the client IP address, but it is not available by default. To enable this feature contact your Customer Success Manager. For more information, see Enabling IP Address Collection in Server-Side Tealium Products. Importance: High Phone (ph) A phone number. Include only digits with country code, area code, and number. Example: 16505551212 Importance: High State (st) US State abbreviation. Example: ca Importance: Medium Email (em) Email address. Example: joe@eg.com Importance: Highest Last Name (ln) A last name in lowercase. Example: smith Importance: Medium First Name (fn) A first name in lowercase. Example: joe Importance: Medium Lead ID ID associated with a lead generated by Facebook Lead Ads. Do not hash. City (ct) A city in lower-case without spaces or punctuation. Example: menlopark Importance: Medium Country (country) A two-letter country code in lowercase. Example: us Importance: Medium External ID Do not hash. Any unique ID from the advertiser, such as loyalty membership IDs, user IDs, and external cookie IDs. Browser ID (fpb) Do not hash. The browser ID value stored in Facebook's _fbp cookie. Importance: High Subscription ID Do not hash. The subscription ID for the user in this transaction. This is similar to the order ID for an individual product. Example: anid1234 Gender Lowercase. Options are: f for female m for male Date of Birth A date of birth given as year, month, and day. Example: 19971226 for December 26, 1997. Click ID (fbc) Do not hash. The Facebook click ID value stored in Facebook's _fbc cookie. Importance: High User Data is already hashed Select this option if the Target User Identifier Data is already hashed. Currency The currency for the value specified if applicable. Currency must be a valid ISO 4217 three-digit currency code. Example: usd Content Name The name of the page or product associated with the event. Example: lettuce Number of Items Use only with InitiateCheckout events. The number of items that a user tries to buy during checkout. Example: 4 Search String A search query made by a user. Use only with Search events. Example: lettuce Status Use only with CompleteRegistration events. The status of the registration event. Example: registered Order ID The order ID for this transaction. Example: order1234 Content Type Must be either product or product_group. Set to product if the keys you send are in Content IDs or Content Product. Content Product represent products. Set to product_group if the keys you send are in Content IDs. Content Product represents product groups. Predicted Lifetime Value The predicted lifetime value of a conversion event. Example: 432.12 Content IDs The Content IDs associated with the event, such as product SKUs for items in an AddToCart event. Example: ['ABC123', 'XYZ789']. If a non-array event attribute is provided, it is converted into a single-item array. If Content Type is product; this mapped value must be a non-array event attribute or single-element array. Value A numeric value associated with this event. This may be a monetary value or a value in some other metric. Example: 142.54 Content Category The category of the content associated with the event. Example: grocery Quantities Product quantities. Prices Product individual prices. IDs Product IDs. JSON Template Variables Provide template variables as data input for templates. See the Template Variables Guide. Name nested template variables with the dot notation, for example items.name . Nested template variables are typically built from data layer list attributes. JSON Templates Provide valid JSON templates to be referenced in Custom Data section. Templates are injected by name with double curly braces into supported fields, for example: {{SomeTemplateName}} . For additional information, see the Webhook - Send Custom Request - Trimou Templating Engine Guide. Automatic Deduplication When the Tealium iQ Tag ID is provided, we will automatically look for your Event ID value that is sent from Tealium iQ. Setup There are several options available to setup and manage Tealium's server-side API partner integration with Facebook. The Facebook Partner Integration Gallery The Pixel Settings tab via the Choose Partner button: The web signal setup flow and Server-side API guidance card: Verify Events After sending your events, verify that Facebook has received them in the overview and breakdown views: Go to Business Manager > Pixels. Click on the pixel corresponding to the PIXEL_ID in your POST request. Overview Tab In the Overview tab, change the view from All to Server to see the number of events you have successfully sent. Breakdown Tab The Breakdown tab displays the breakdown of successfully sent events. Dropped events do not appear in the Server Events Received column. You can verify events within 20 minutes after sending them from your server. Validation For validation, use Facebook's Payload Helper with your data parameter fields to see how structure your payload when it's sent to Facebook from your server. See Facebook's Support page for troubleshooting issues. Learn more at Facebook's Using the Conversions API. Additional Resources Facebook for Business: About Conversions API for Web Facebook for Business: Set up Conversions API for Web through your Tealium account Facebook for Developers: Conversions API ... View more