Tealium Learning Center

The following topics describe Tealium Consent Management tools designed to simplify GDPR compliance. Consent Management - Global Consent Parameters Learn how to use consent parameter variables to generate the consent prompt and preferences pop-ups.  Explicit Consent Prompt Manager Learn how to deploy a prompt to your website that allows users to opt-in or opt-out of tracking. This tool offers full access to customize the code behind the scenes and options for translated content.  Consent Preferences Manager Learn how to deploy a tracking preferences option to your website that will allow customers to specify which categories of tags they allow. This tools offers full access to customize the code that generates the preferences pop-up and the ability to translate content for your global customers. ... View more

Anura is an ad fraud detection solution that analyzes your traffic to identify real users versus bots, malware, and fraudulent human users. This article describes how to configure the Anura marketplace tag for Tealium iQ Tag Management (TiQ). In this article: Table of Contents Placeholder How it Works The Anura tag places your basic Anura response, such as "good", "suspect", etc. Response Variable Name in your requested Response Location. If you are using Script Response the Response Object Variable Name will be available in the default Anura window object. Tag Configuration First, go to Tealium's tag marketplace and add the Anura tag to your profile (Learn more about how to add a tag). After adding the tag, configure the following settings: Title The default is Anura. You may replace it with a custom name of choice. Assign a unique name when using multiple tags by the same vendor. Instance ID The Instance ID assigned by your account representative. Source Tracking ID A variable that you declare to identify traffic within the Anura interface. Campaign Tracking ID A subset variable of the Source Tracking ID that you declare to help identify traffic within the Anura interface. Response Object Variable Name The variable name of the JavaScript object that initial response data will be assigned to. Result Method The method used to query for results. Options are Script Response or Direct Response. Response Location The location to put the results in. Options are Window Variable, Session Storage, or Local Storage. Response Variable Name The name of the Response Location variable in which to place the final Anura response. Load Rules Load Rules determine when and where to load an instance of this tag on your site. Recommended Load Rule: Load on All Pages Data Mappings Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see Data Mappings. The destination variables for the Anura tag are built into its Data Mapping tab. Available categories are: Standard Tag Destination Description Variable Instance Required. Your instance ID. instance Source Tracking ID Optional. A variable, declared by you, to identify source traffic within the Anura dashboard. Maximum of 128 characters. M ay not equal the following values: "all sources", "all campaigns", "&", "*", "?", "%". Allowed to start with: "$", "_", or "a-z" characters, followed by "a-z" and "0-9" characters. source Campaign Tracking ID Optional. A subset of the source variable, declared by you, to identify campaign traffic within the Anura dashboard. Maximum of 128 characters. M ay not equal the following values: "all sources", "all campaigns", "&", "*", "?", "%". campaign Unique External ID Optional. A unique external tracking ID, declared by you, that is used to query the result from Anura servers. Maximum of 128 characters. exid Response Object Variable Name Optional. The variable name of the JavaScript object that response data will be assigned to. This variable contains the response ID, in addition to other data, that allows you to make real-time decisions. Maximum of 128 characters. variable Result Method Optional. The result method. result_method Result Location Optional. The result location. result_location Response Variable Name Optional. The Response Variable Name. response_variable Visitor IP Address Required. The IP address of your visitor. IPv6 addresses are also supported. ip Visitor User Agent Optional. The user agent string of your visitor. ua E-Commerce Since the Anura tag is e-commerce enabled, it will automatically use the default E-Commerce extension mappings. Manually mapping in this category is generally not needed unless you want to override extension mappings or your desired e-commerce variable is not offered in the extension. Destination Description E-Commerce Extension Variable Order ID Unique identifier assigned to the final order. _corder Sub Total Sub total amount of the final order. _csubtotal Currency Currency used in the payment. _ccurrency List of Product IDs Unique identifier of each product in the product array. _cprod List of Product Names Name of each product in the product array. _cprodname List of Brand Brand of each product in the product array. _cbrand List of Categories Name of each product in the product array. _ccat List of Quantities Quantity of each product in the product array. _cquan List of Prices Unit price of each product in the product array. _cprice e-comm destination name Insert description. N/A Vendor Documentation Anura Docs ... 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 Changed branding for Xiti name, logos, and QuickBase to AT Internet. (Learn more) Updated the Adobe Target tag to support Versions 1.7 and 2.0 and updated tool tips to explain that unbundling is not supported and will be overwritten at publish if the bundled flag is turned off. (Learn more) Updated the Clicktale tag to send audiences and badges to Clicktale. Updated the Clicktale tag to send replay links to Tealium Collect. Fixes Corrected Promo ID drop-down list for the Conversant Media - Direct to Brands tag. Corrected gtag.js issue for pages manually tagged with GTM. Updated the Google Analytics (gtag.js) connector to add support for event-scoped content groups. Connectors New/Cool Stuff New marketplace connector: Adobe Campaign Standard, Experiments - Beta (Learn more) New marketplace connector: Chameleon (Learn more) New marketplace connector: Criteo Audience Match (Learn more) New marketplace connector: Domo JSON Webhook (Learn more) New marketplace connector: Emailicious (Learn more) New marketplace connector: Flashtalking User Segments, Experiments - Beta (Learn more) New marketplace connector: iSpot TV (Learn more) New marketplace connector: Klenty (Learn more) New marketplace connector: Mailrelay (Learn more) New marketplace connector: Retently (Learn more) New marketplace connector: SmartSurvey (Learn more) New marketplace connector: Tamber (Learn more) New marketplace connector: Userlist.io (Learn more) Added Delete User action for the Braze connector. (Learn more) Added support for integer type number attribute. (Learn more) Updated the Optimizely Events connector to latest version. (Learn more) Fixes Corrected error with the Send a Custom App event for the Facebook Server-Side Events (BETA) connector. (Learn more) Corrected issue causing the AppsFlyer App Events connector to not send successful requests via Postman. (Learn more) Corrected issue with the Create or Update Contact actions for the Listrak connector passing wrong key. (Learn more) Corrected issue with the timestamp format for the date attribute when using the Responsys connector. (Learn more) Corrected issue with the "Subscribe User to List" action for the Iterable connector. (Learn more) Corrected XML structure issue with the SmartFocus connector. (Learn more) Corrected issue with select connectors causing the Active Campaign List ID to not send. iQ Tag Management New/Cool Stuff Introduced the Load Order Manager interface for tags and extensions under Experiments: BETA. (Learn more) Fixes Applied various security fixes. Universal Data Hub New/Cool Stuff Added missing us-east-2 (Ohio) Amazon Web Services (AWS) S3 bucket region for use with the File Import feature. Added the "Remove a String from the array" enrichment to the Array of Strings attribute. Fixes Corrected a text wrapping issue in the Trace window. Corrected issue causing console error when using the Timeline attribute in a rule. Corrected issue causing Visitor Profile Sampler charts to not update properly for specific profiles. (Learn more) Installations New/Cool stuff Introduced Tealium remote command integration for Braze on Android and Swift/iOS. (Learn more) Updated iOS library to support WKWebView for tag management for devices running iOS 11.0 or greater. (iOS Learn more, Swift Learn more) ... View more

The BETA version of our new client-side feature called Load Order Manager is now available. Using this feature, you can now control the order of operations for the Universal Tag (utag.js) to simplify the way you view and manage extensions and tag ordering. In this article: Table of Contents Placeholder Reasons for the Change Until now, the ability to reorder extensions and tags was limited and could only be performed on one extension or tag at a time by dragging and dropping the execution order from the main extensions and tags view or using the drop-down menu. Though this process is simple, is has the following limitations: When adding or editing an extension or tag, selecting the scope from the drop-down list does not always represent the true execution order. This is because the load order for extensions and tags is dictated by both execution order and extension and tag organization. There is no option for bulk reordering. It is difficult to reorder large lists that span beyond the visible view. Searching for specific extensions and tags is difficult What Improved The new Load Order Manager feature provides a more scalable and user-friendly method to manage tag and extension ordering. The process is still simple but without the previous limitations. Using Load Order Manager you can now: Display a single view of all of your marketplace extensions and tags, in execution order. Reorder extensions and tags more efficiently using improved drag-and-drop capabilities and numeric list ordering. Use the bulk feature to simultaneously reorder and move multiple extensions and tags. Use the improved search to filter extension and tag searches by label, title, type, or UID. What Changed Extensions Screen Extensions are now sorted and grouped by scope, according to the order of operations. Tags Screen Under Tag Configuration > Advanced Settings, the Wait Flag is now called Tag Timing. This setting determines if tags fire at the DOM Ready event, or immediately when utag.js loads. The options are Prioritized or DOM Ready (the default value). Where do I get it and how do I use it? Load Order Manager is currently launched as a client-side experiment that any user can enable at the profile level. To enable the feature, click iQ Tag Management (TiQ) > Client-Side Experiments in the left sidebar. Once enabled, the profile is saved to activate the feature. Once published, the feature is available to all users of that profile. To begin using Load Order Manager , simply click the new Edit Load Order button in the list view for any extension or tag. For detailed information about using Load Order Manager, see Load Order Manager (BETA). Can I provide feedback? Yes! To provide feedback, go to TiQ: Load Order Feedback. All feedback will be reviewed during the BETA release and considered for implementation in the final release. ... View more

This article describes how to set up the Mailrelay connector in your Universal Data Hub (UDH) account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add Subscriber ✓ ✗ 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 Subscriber Parameters Parameter Description Your Account Your Mailrelay address or account name. For more information, see: https://mailrelay.com/en/api-documentation API key Your API key. Found in your account under settings. Email Email address of the subscriber. Name Name of the subscriber. ... View more

This article describes how to set up the SmartSurvey connector in your Universal Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add Contact to 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: API Token The API token and token secret must be passed with each request. \ For more information, see: SmartSurvey: Getting Started API Token Secret The API token and token secret must be passed with each request. For more information, see: SmartSurvey: 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 - Add Contact to List Parameters Parameter Description Contact list ID The unique ID for the contact list. For more information, see: https://docs.smartsurvey.io/v1/reference#contactlists_contacts_insert Email The email address for the contact. Name The name of the contact. Custom Fields Custom data fields pertaining to the contact. ... View more

This article describes how to set up the Emailicious connector in your Universal Data Hub account. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Create Subscriber and Add Them to 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: Username The username for your Emailicious account. For more information, see: https://emailicious-api.readthedocs.io/en/latest/topics/authentication.html Password The password for your Emailicious account. 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 Them to List Parameters Parameter Description Account Name The name of your Emailicious account. For more information, see: https://emailicious-api.readthedocs.io/en/latest/topics/introduction.html List ID The unique identifier for the list the subscriber will be added to. For more information, see: https://emailicious-api.readthedocs.io/en/latest/resources/subscribers.html#post--api-v1-lists-(int-list_id)-subscribers Email The subscriber's email. First Name The subscriber's first name. Last Name The subscriber's last name. Gender The subscriber's gender. Date of Birth The subscriber's date of birth. Language The subscriber's language. Region The subscriber's region. ... View more

This article describes how to set up the Retently connector in your Universal Data Hub (UDH) account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Create or Update Customer ✓ ✗ Send Survey ✓ ✗ Unsubscribe Customer ✓ ✗ Delete Customer ✓ ✗ 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 API key can be found in your Retently account under 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 - Create or Update Customer Parameters Parameter Description Email Email address of the customer. For more information, see: https://www.retently.com/api/#api-create-or-update-customers-post First Name First name of the customer. Last Name Last name of the customer. Company Company name assigned to the customer. Tag A tag to be assigned to the customer. Action - Send Survey Parameters Parameter Description Campaign The campaign identifier. Must be a transactional campaign type. For more information, see: https://www.retently.com/api/#api-send-survey-post Email Email address of the customer. For more information, see: https://www.retently.com/api/#api-create-or-update-customers-post First Name First name of the customer. Last Name Last name of the customer. Company Company name assigned to the customer. Tag A tag to be assigned to the customer. Action - Unsubscribe Customer Parameters Parameter Description Email Email address to be unsubscribed. For more information, see: https://www.retently.com/api/#api-unsubscribe-customers-post Message Opt out message. Action - Delete Customer Parameters Parameter Description Email Email address of the customer to be deleted. For more information, see: https://www.retently.com/api/#api-delete-customers-delete ... View more

This article describes how to set up the Chameleon connector in your Universal Data Hub account. 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 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: https://help.trychameleon.com/articles/1229862-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: https://help.trychameleon.com/articles/1229862-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 Universal Data Hub (UDH) 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 Universal Data Hub (UDH) 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.io connector in your Universal Data Hub (UDH) account. 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.io, 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: https://docs.userlist.io/article/15-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: https://docs.userlist.io/article/15-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: https://docs.userlist.io/article/15-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 Universal Data Hub (UDH) 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 Braze connector in your Universal Data Hub  (UDH) account. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Track User by External ID ✓ ✗ Track User by User Alias ✓ ✗ Delete User by External ID or Braze ID ✓ ✗ Delete User by User Alias ✓ ✗ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: REST API Key API Keys are used to authenticate an API call. When you create a new REST API Key, you need to give it access to specific endpoints. By assigning specific permissions to an API Key, you can limit exactly which calls an API Key is able to authenticate. For more see https://www.braze.com/documentation/REST_API/#app-group-rest-api-keys This connector requires an API Key that has the User Data (users.track) permission ) to record user attributes, custom events, and purchases. For more see: https://www.braze.com/documentation/REST_API/#user-track-endpoint 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 by External ID Parameters Parameter Description Endpoint URL Required. Your endpoint will correspond to your Braze instance. This endpoint can be used to record custom events, user attributes, and purchases for users, see: https://www.braze.com/documentation/REST_API/#user-track-endpoint External ID The External ID serves as a unique user identifier for whom you are submitting data. This identifier should be the same as the one you set in the Braze mobile SDK in order to avoid creating multiple profiles for the same user. External IDs that Braze is unaware of will return a non-fatal error. See Server Responses for details. User Attributes An API request with any fields in the Attributes Object will create or update an attribute of that name with the given value on the specified user profile. Use the Braze User Profile Field names or your own custom attribute data. For more Information, see: https://www.braze.com/documentation/REST_API/#user-track-request. Action - Track User by User Alias Parameters Parameter Description Endpoint URL Required. Your endpoint will correspond to your Braze instance. This endpoint can be used to record custom events, user attributes, and purchases for users, see: https://www.braze.com/documentation/REST_API/#user-track-endpoint User Alias Value Map the actual identifier value for the alias. Example: "Bobby". An alias serves as an alternative unique user identifier. Use aliases to identify users along different dimensions than your core user ID. When using a User Alias, the "Update Only" mode is always true. For more detail on definitions, see: https://www.braze.com/documentation/REST_API/#basics User Alias Label The label for the Alias. Example" "my_internal_ids". An alias serves as an alternative unique user identifier. Use aliases to identify users along different dimensions than your core user ID. When using a User Alias, "Update Only" mode is always true. For more detail on definitions, see: https://www.braze.com/documentation/REST_API/#basics. User Attributes An API request with any fields in the Attributes Object will create or update an attribute of that name with the given value on the specified user profile. Use the Braze User Profile Field names or your own custom attribute data. For more information, see: https://www.braze.com/documentation/REST_API/#user-track-request Action - Delete User by External ID or Braze ID Parameters Parameter Description Endpoint URL Required. Your endpoint will correspond to your Braze instance. This endpoint can be used to record custom events, user attributes, and purchases for users, see: https://www.braze.com/documentation/REST_API/#user-track-endpoint External ID External ID of the user to delete. Must include either External ID or Braze ID For more information, see: https://www.braze.com/docs/api/endpoints/user_data/#user-delete-request Braze ID Braze ID of the user to delete. Must include either External ID or Braze ID. Action - Delete User by User Alias Parameters Parameter Description Endpoint URL Required. Your endpoint will correspond to your Braze instance. This endpoint can be used to record custom events, user attributes, and purchases for users, see: https://www.braze.com/documentation/REST_API/#user-track-endpoint Alias Name The alias name of the user to be deleted. For more information, see: https://www.braze.com/docs/api/endpoints/user_data/#user-delete-request Alias Label The alias label of the user to be deleted. ... View more

This article describes how to set up the Sizmek connector in your Universal 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

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 Universal 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 Universal Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Create Subscriber ✓ ✗ Update Subscriber ✓ ✗ Send Transactional Email ✓ ✗ Create Subscriber with Double Opt-in ✓ ✗ Delete Single Subscription ✓ ✗ Create Single Subscription ✓ ✗ 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 Parameters Parameter Description Mailing List ID The ID of the list the subscriber should be added to. For more information, see: http://se.apidoc.anpdm.com/Browse/Method/SubscriberService/CreateSubscriber Update If Exists If the email address already exists on the account and this parameter is true, then the subscriber data will be updated. Otherwise, an error is returned. Email The subscriber's email address. Password The subscriber's password. Name The name of the subscriber. Format The subscriber's desired format. Country Code The subscriber's country code. Phone Number The subscriber's phone number. External ID The subscriber's external ID. Demographic Data Fields The subscriber's list of demographic data fields. Action - Update Subscriber Parameters Parameter Description Subscriber ID The subscriber's ID. For more information, see: http://se.apidoc.anpdm.com/Browse/Method/SubscriberService/UpdateSubscribers Email The subscriber's email address. Password The subscriber's password. Name The name of the subscriber. Format The subscriber's desired format. Country Code The subscriber's country code. Phone Number The subscriber's phone number. Demographic Data Fields The subscriber's list of demographic data fields. Action - Send Transactional Email Parameters Parameter Description Project ID ID of the project. For more information, see: http://se.apidoc.anpdm.com/Browse/Method/TransactionalService/SendTransactionalEmail Send Date Send date. Allow Inactive Projects True or false indicating if sending should be allowed when project is inactive Default value is true. Email The subscriber's email address. Name The name of the subscriber. Format The subscriber's desired format. External ID The subscriber's external ID. Country Code The subscriber's country code. Demographic Data Fields The subscriber's list of demographic data fields. Sending Type Possible values: m - marketing t - transactional (default) Action - Create Subscriber with Double Opt-in Parameters Parameter Description Mailing List ID ID of the mailing list to which the subscriber will be added. For more information, see: http://se.apidoc.anpdm.com/Browse/Method/SubscriberService/CreateSubscriberWithDoubleOptIn Email The subscriber's email address. Password The subscriber's password. Name The name of the subscriber. Format The subscriber's desired format. Country Code The subscriber's country code. Phone Number The subscriber's phone number. External ID The subscriber's external ID. Demographic Data Fields The subscriber's list of demographic data fields. Action - Delete Single Subscription Parameters Parameter Description Mailing List ID The mailing list from which to delete the subscriber. For more information, see: http://se.apidoc.anpdm.com/Browse/Method/MailingListService/DeleteSingleSubscription Subscriber ID The ID of the subscriber to be removed from the list. Action - Create Single Subscription Parameters Parameter Description Mailing List ID The Mailing List ID to which the subscription should be created. For more information, see: http://se.apidoc.anpdm.com/Browse/Method/MailingListService/CreateSingleSubscription Subscriber ID The ID of the subscriber to be added to the list. ... View more

This article describes how to set up the ONTRAPORT connector in your Universal 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: https://api.ontraport.com/doc/#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: https://api.ontraport.com/doc/#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: https://api.ontraport.com/doc/#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: https://api.ontraport.com/doc/#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: https://api.ontraport.com/doc/#delete-a-specific-contact ... View more

This article describes how to set up the Sarbacane connector in your Universal 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