Tealium Learning Center

This article describes how to set up the Optimizely Events connector in your Customer Data Hub account. The Beta version of this connector is currently available as an Experiment. (Learn more) 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: Account ID The Optimizely account to which the events should be attributed. Access Token Access token can be obtained by navigating to Optimizely Profile > API Access. 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 Visitor ID Required Session ID   Project ID   Anonymize IP Values are true or false Enrich Decisions Values are true or false Client Name   Client Verson   Timestamp Required UUID Required Entity ID   Key   Quantity   Revenue   Type   Value   Event Tags Additional event properties. Campaign ID Required Experiment ID Required Variation ID Required Campaign Holdback Values are true or false Type Required Can be "custom" Value Required Entity ID Required for custom attribute type. Key   ... View more

This article describes how to set up the Adobe Campaign Classic Batch connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send Custom SOAP Request ✓ ✗ 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: Server Host Either Server Host or Server Address is required. Example: For the domain, "serverURL" copy and paste serverURL  from the following example URL:  https://serverURL/nl/jsp/soaprouter.jsp For authentication, provide username and password as part of SOAP Request Body Prefix. For additional information, see Access Management in the Adobe Campaign Classic access management help documentation. Server Address Specify full URL to Adobe Campaign server. Either Server Host or Server Address is required. If the address is provided, host is ignored. 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 Custom SOAP Request Parameters Parameter Description SOAP Action SOAP Action. Example:   xtk:session#Logon This value will be assigned to SOAPAction HTTP header. SOAP Request Template Variables Provide template variables as data input for SOAP Request Body Prefix, SOAP Request Body Data and SOAP Request Body Suffix (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. SOAP Request Body Prefix Provide a template of the opening portion of SOAP Request. Example: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:xtk:session"><soapenv:Header/><soapenv:Body><urn:Logon><urn:strLogin>USERNAME</urn:strLogin><urn:strPassword>PASSWORD</urn:strPassword><urn:elemParameters> Use your Adobe username and password in place of USERNAME and PASSWORD. You can use template variables in the SOAP Request Body Prefix. For additional information, see: Templates Guide SOAP Request Body Data Provide a template for the SOAP Request batch item to be sent. You can use template variables in the SOAP Request Body Data. SOAP Request Body Joiner A character or string to use between body items when batching. If not specified, empty string will be used. SOAP Request Body Suffix Provide a template for the closing portion of SOAP Request. Example: "&lt;/urn:customerId&gt;&lt;/urn:sendCampaign&gt;&lt;/soapenv:Body&gt;&lt;/soapenv:Envelope> You can use template variables in the SOAP Request Body Suffix. SOAP Response Error Identifier If the response contains any of the error strings (OR condition) specified below, it is marked as a failure. By default, an HTTP response status outside 200-299 range is also marked as a failure. ... View more

This article describes how to set up the Branch Events connector in your Customer Data Hub account. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Log Commerce Event ✓ ✓ Log Content Event ✓ ✓ Log Lifecycle Event ✓ ✓ Log Custom 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: Branch Key This value is found on the Profile page of the Branch Account Manager. 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 - Log Commerce Event Parameters Parameter Description Event Type Required. Select a type of commerce event. OS Type Required. Select a type of operating system on the mobile device. Device ID Required. Specify one or two device IDs. Different IDs can be selected depending on the OS type. User Data Optional. Specify as many device-identifying parameters as desired: OS Version Number. Version of the operating system. Specific to Android and iOS. Environment String. Usually "FULL_APP". User Agent String. User agent of the browser or app where the event occurred. HTTP Origin String. Current page URL where Web SDK logged web session start. HTTP Referrer String. Referral URL that led to the current page where the Web SDK logged web session started. Local IP String. Local IP of the device (Android only). Country String. Country code of the user, usually based on device settings or user agent string. Language String. Language code of the user, usually based on device settings or user agent string. Brand String. Brand of the device. Model String. Model of the device. App Version String. App version downloaded by the user. Screen DPI Number. Screen DPI. Screen Height Number. Height of the screen. Screen Width Number. Width of the screen. Developer Identity String. Developer-specified identity for a user. Device Fingerprint ID Branch internal-only field for tracking devices. Browser Fingerprint ID Branch internal-only field for tracking browsers. Limit Ad Tracking Value is True if the partner has opted to not be tracked by advertiser. Event Data Optional. Data specific for the event. Transaction ID String. Partner-specified transaction ID for the partner's internal use. Currency String. Currency that revenue, price, shipping, and tax were originally reported in by the partner. Revenue Number. Partner-specified reported revenue for the event. Shipping Number. Shipping cost associated with the transaction. Tax Number. Total tax associated with the transaction. Coupon String Transaction coupon redeemed with the transaction. Example: "SPRING2017". Affiliation String. Store or affiliation from which this transaction occurred. Example: "Google Store". Description String. Description associated with the event, not necessarily specific to an individual content item. Custom Data Optional. Specify additional data with arbitrary property names and values. Content Items Optional. Specify properties for content items either as array-type values of equal lengths, or as a single value, which will apply to all items. Content Schema Category or schema for a piece of content, may be used in the future for analytics. One of: COMMERCE_AUCTION COMMERCE_BUSINESS COMMERCE_OTHER COMMERCE_PRODUCT COMMERCE_RESTAURANT COMMERCE_SERVICE COMMERCE_TRAVEL_FLIGHT COMMERCE_TRAVEL_HOTEL COMMERCE_TRAVEL_OTHER GAME_STATE MEDIA_IMAGE MEDIA_MIXED MEDIA_MUSIC MEDIA_OTHER MEDIA_VIDEO OTHER TEXT_ARTICLE TEXT_BLOG TEXT_OTHER TEXT_RECIPE TEXT_REVIEW TEXT_SEARCH_RESULTS TEXT_STORY TEXT_TECHNICAL_DOC Title Title for the individual content item. Description Description of the individual content item. Image URL Image URL for the individual content item. Canonical Identifier Used to allow Branch to unify content/messages for Content Analytics. Publicly Indexable If value is true, content can be viewed by anyone. If value is false, cannot index for public use. Locally Indexable If value is true, content can be indexed for local (device) use. If value is false, cannot index for local use. Price Price for the product/content. Quantity Quantity of the item to be ordered. Example: for PURCHASE , ADD_TO_CART SKU Product SKU or product ID. Product Name Name of the product. Product Brand Brand of the product. Product Category Category of a product. if applicable. One of: ANIMALS_AND_PET_SUPPLIES APPAREL_AND_ACCESSORIES ARTS_AND_ENTERTAINMENT BABY_AND_TODDLER BUSINESS_AND_INDUSTRIAL CAMERAS_AND_OPTICS ELECTRONICS FOOD_BEVERAGES_AND_TOBACCO FURNITURE HARDWARE HEALTH_AND_BEAUTY HOME_AND_GARDEN LUGGAGE_AND_BAGS MATURE MEDIA OFFICE_SUPPLIES RELIGIOUS_AND_CEREMONIAL SOFTWARE SPORTING_GOODS TOYS_AND_GAMES VEHICLES_AND_PARTS Product Variant Variant of the product. Example: red Rating Average Average rating of the item. Rating Count Number of ratings for the item. Rating Max Maximum possible rating for the item. Example: 5.0 if 5 stars is highest possible rating. Creation Timestamp Time the content was created. Exp Date The last time after which this content is no longer valid. Null / 0 mean no limit. Should rarely be set. Condition For auctions, whether the item is new, good, acceptable, etc. One of: OTHER NEW EXCELLENT GOOD FAIR POOR USED REFURBISHED Keywords Keyword. Image Captions String with comma-separated values. Captions associated with the image. Latitude Latitude for a restaurant, business, room (hotel), etc. Longitude Longitude for a restaurant, business, room (hotel), etc. Postal Code Postal/zip code for a restaurant, business, room (hotel), etc. Country Country code for a restaurant, business, room (hotel), etc. Region State or region for a restaurant, business, room (hotel), etc. City City for a restaurant, business, room (hotel), etc. Street Street address for a restaurant, business, room (hotel), etc. Custom Fields Key-value pairs that the app developer would like attached to the content item. Action - Log Content Event Parameters Parameter Description Event Type Required. Select a type of commerce event. OS Type Required. Select a type of operating system on the mobile device. Device ID Required. Specify one or two device IDs. Different IDs can be selected depending on the OS type. User Data Optional. Specify as many device-identifying parameters as desired: OS Version Number. Version of the operating system. Specific to Android and iOS. Environment String. Usually "FULL_APP". User Agent String. User agent of the browser or app where the event occurred. HTTP Origin String. Current page URL where Web SDK logged web session start. HTTP Referrer String. Referral URL that led to the current page where the Web SDK logged web session started. Local IP String. Local IP of the device (Android only). Country String. Country code of the user, usually based on device settings or user agent string. Language String. Language code of the user, usually based on device settings or user agent string. Brand String. Brand of the device. Model String. Model of the device. App Version String. App version downloaded by the user. Screen DPI Number. Screen DPI. Screen Height Number, Height of the screen. Screen Width Number. Width of the screen. Developer Identity String. Developer-specified identity for a user. Device Fingerprint ID Branch internal-only field for tracking devices. Browser Fingerprint ID Branch internal-only field for tracking browsers. Limit Ad Tracking Value is True if the partner has opted to not be tracked by advertiser. Event Data Optional. Data specific for the event. Search Query String. Search query associated with the event. Description String. Description associated with the event, not necessarily specific to individual content items. Custom Data Optional. Specify additional data with arbitrary property names and values Content Items Optional. Specify properties for content items either as array-type values of equal lengths, or as a single value, which will apply to all items. Content Schema Category or schema for a piece of content, may be used in the future for analytics. One of: COMMERCE_AUCTION COMMERCE_BUSINESS COMMERCE_OTHER COMMERCE_PRODUCT COMMERCE_RESTAURANT COMMERCE_SERVICE COMMERCE_TRAVEL_FLIGHT COMMERCE_TRAVEL_HOTEL COMMERCE_TRAVEL_OTHER GAME_STATE MEDIA_IMAGE MEDIA_MIXED MEDIA_MUSIC MEDIA_OTHER MEDIA_VIDEO OTHER TEXT_ARTICLE TEXT_BLOG TEXT_OTHER TEXT_RECIPE TEXT_REVIEW TEXT_SEARCH_RESULTS TEXT_STORY TEXT_TECHNICAL_DOC Title Title for the individual content item. Description Description of the individual content item. Image URL Image URL for the individual content item. Canonical Identifier Used to allow Branch to unify content/messages for Content Analytics. Publicly Indexable If value is true, content can be viewed by anyone. If value is false, cannot index for public use. Locally Indexable If value is true, content can be indexed for local (device) use. If value is false, cannot index for local use. Price Price for the product/content. Quantity Quantity of the item to be ordered. Example: for PURCHASE , ADD_TO_CART SKU Product SKU or product ID. Product Name Name of the product. Product Brand Brand of the product. Product Category Category of a product. if applicable. One of: ANIMALS_AND_PET_SUPPLIES APPAREL_AND_ACCESSORIES ARTS_AND_ENTERTAINMENT BABY_AND_TODDLER BUSINESS_AND_INDUSTRIAL CAMERAS_AND_OPTICS ELECTRONICS FOOD_BEVERAGES_AND_TOBACCO FURNITURE HARDWARE HEALTH_AND_BEAUTY HOME_AND_GARDEN LUGGAGE_AND_BAGS MATURE MEDIA OFFICE_SUPPLIES RELIGIOUS_AND_CEREMONIAL SOFTWARE SPORTING_GOODS TOYS_AND_GAMES VEHICLES_AND_PARTS Product Variant Variant of the product. Example: red Rating Average Average rating of the item. Rating Count Number of ratings for the item. Rating Max Maximum possible rating for the item. Example: 5.0 if 5 stars is highest possible rating. Creation Timestamp Time the content was created. Exp Date The last time after which this content is no longer valid. Null / 0 mean no limit. Should rarely be set. Condition For auctions, whether the item is new, good, acceptable, etc. One of: OTHER NEW EXCELLENT GOOD FAIR POOR USED REFURBISHED Keywords Keyword. Image Captions String with comma-separated values. Captions associated with the image. Latitude Latitude for a restaurant, business, room (hotel), etc. Longitude Longitude for a restaurant, business, room (hotel), etc. Postal Code Postal/zip code for a restaurant, business, room (hotel), etc. Country Country code for a restaurant, business, room (hotel), etc. Region State or region for a restaurant, business, room (hotel), etc. City City for a restaurant, business, room (hotel), etc. Street Street address for a restaurant, business, room (hotel), etc. Custom Fields Key-value pairs that the app developer would like attached to the content item. Action - Log Lifecycle Event Parameters Parameter Description Event Type Required. Select a type of commerce event. OS Type Required. Select a type of operating system on the mobile device. Device ID Required. Specify one or two device IDs. Different IDs can be selected depending on OS type. User Data Optional. Specify as many device-identifying parameters as desired: OS Version Number. Version of the operating system. Specific to Android and iOS. Environment String. Usually "FULL_APP". User Agent String. User agent of the browser or app where the event occurred. HTTP Origin String. Current page URL where Web SDK logged web session start. HTTP Referrer String. Referral URL that led to the current page where the Web SDK logged web session started. Local IP String. Local IP of the device (Android only). Country String. Country code of the user, usually based on device settings or user agent string. Language String. Language code of the user, usually based on device settings or user agent string. Brand String. Brand of the device. Model String. Model of the device. App Version String. App version downloaded by the user. Screen DPI Number. Screen DPI. Screen Height Number. Height of the screen. Screen Width Number. Width of the screen. Developer Identity String. Developer-specified identity for a user. Device Fingerprint ID Branch internal-only field for tracking devices. Browser Fingerprint ID Branch internal-only field for tracking browsers. Limit Ad Tracking Value is True if the partner has opted to not be tracked by advertiser. Event Data Optional. Data specific for the event. Description: string, description associated with the event, not necessarily specific to any individual content items. Custom Data Optional. Specify additional data with arbitrary property names and values. Action - Log Custom Event Parameters Parameter Description Event Type Required. Select a type of commerce event. OS Type Required. Select a type of operating system on the mobile device. Device ID Required. Specify one or two device IDs. Different IDs can be selected depending on the OS type. User Data Optional. Specify as many device-identifying parameters as desired: OS Version Number. Version of the operating system. Specific to Android and iOS. Environment String. Usually "FULL_APP". User Agent String. User agent of the browser or app where the event occurred. HTTP Origin String. Current page URL where Web SDK logged web session start. HTTP Referrer String. Referral URL that led to the current page where the Web SDK logged web session started. Local IP String. Local IP of the device (Android only). Country String. Country code of the user, usually based on device settings or user agent string. Language String. Language code of the user, usually based on device settings or user agent string. Brand String. Brand of the device. Model String. Model of the device. App Version String. App version downloaded by the user. Screen DPI Number. Screen DPI. Screen Height Number, Height of the screen. Screen Width Number. Width of the screen. Developer Identity String. Developer-specified identity for a user. Device Fingerprint ID Branch internal-only field for tracking devices. Browser Fingerprint ID Branch internal-only field for tracking browsers. Limit Ad Tracking Value is True if the partner has opted to not be tracked by advertiser. Custom Data Optional. Specify additional data with arbitrary property names and values Vendor Documentation Branch Docs: Events Branch API: Logging Commerce, Content, Lifecycle and Custom Events ... View more

This article describes how to set up the Tapjoy Conversion Postbacks connector in your Customer Data Hub account. The Beta version of this connector is currently available as an Experiment. (Learn more) In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send Conversion Postback ✗ ✓ 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: Campaign ID 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 Conversion Postback Parameters Parameter Description Transaction ID The Click ID from the offer that led to the conversion. Amount Many e-commerce and similar advertisers establish offers based on percentage of sale. Use this parameter to pass a sales amount for reporting. Do not use commas or periods as thousands markers, as this can result in the ad server recording no sale value for your conversion. For more details, see HasOffers documentation. Advertiser Sub IDs Map up to five (5) parameters to include with your postback conversion. Use only parameter keys of adv_sub, adv_sub2, adv_sub3, adv_sub4 and adv_sub5. Sub IDs are typically used to help you and the advertiser quickly cross-reference conversion data to tailor a campaign. For additional information, see the HasOffers documentation for customizing conversion links. ... View more

This article describes how to set up the AppsFlyer App Events connector in your Customer Data Hub account. This connector replaces the (DEPRECATED) AppsFlyer App Events Connector. This feature is currently available in as an experiment only and must enabled prior to use. (Learn more) In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Track Install ✓ ✓ Track in App Event ✓ ✓ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: App ID This is the App ID of the app for which you are passing data. Dev Key The account dev key taken from the App Settings screen in the AppsFlyer dashboard. 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 Install Parameters Parameter Description Platform The platform the event came from. Values in drop-down list are Android, Windows, or iOS. iad-adgroup-id Ad ID group ID. iad-adgroup-name Ad ID group name. iad-attribution Ad ID attribution. iad-campaign-id Ad ID campaign ID. iad-campaign-name Ad ID campaign name. iad-click-date Ad ID click date. iad-conversion-date Ad ID conversion date. iad-keyword Ad ID keyword. iad-lineitem-id Ad ID line item. iad-lineitem-name Ad ID line item name. iad-org-name Ad ID organization name. Action - Track in App Event Parameters Parameter Description Platform The platform the event came from. Values in drop-down list are Android, Windows, or iOS. Event Currency Default currency for the event Only use for ' USD ', for all else, map under the Event Properties ( event_value ) section using the af_currency key. Event Name Required. A string describing the event name. Example: ' af_purchase '. ... View more

This article describes how to set up the Flashtalking User Segments connector in your Customer Data Hub account. This connector is currently available as an Experiment. (Learn more) In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add User to Segment ✓ ✓ Remove User from Segment ✓ ✓ Remove User from All Segments ✓ ✓ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: Advertiser ID Find your Advertiser ID within the Flashtalking Pixel Manager. Username Enter the username you use to log into Flashtalking hub. Password Enter the password you use to log into Flashtalking hub. Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Add User to Segment Parameters Parameter Description DAID Android advertising ID. IDFA Apple advertising ID. UID Unique ID from cookie sync. Segment(s) Identify the target segments by the segment string. Pass either a single segment or a comma separated list of segments. If you pass a list of segments, do not include brackets " [] ". Action - Remove User from Segment Parameters Parameter Description DAID Android advertising ID. IDFA Apple advertising ID. UID Unique ID from cookie sync. Segment(s) Identify the target segment(s) by the Segment String. Pass either a single segment or a comma separated list of segments. If you pass a list of segments, do not include brackets " [] ". Action - Remove User from All Segments Parameters Parameter Description DAID Android advertising ID. IDFA Apple advertising ID. UID Unique ID from cookie sync. ... View more

This article describes how to set up the Domo JSON Webhook connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send Event Data ✗ ✓ Send Visitor Data ✓ ✗ Send Customized Data (Advanced) ✓ ✓ 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: Webhook URL Paste the URL provided in the Details section of your Domo connector setup. If you specify a URL endpoint here, it will be applied to all actions in the connector, but may be overridden in the action. Webhook Secret Optional. Enter a Webhook Secret if desired. For additional information, see Domo: JSON Webhook Connector 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 Data Parameters Parameter Description Webhook URL Required only if not provided in the Configuration tab. Overwrites the value defined in the Configuration tab if a value is provided. Print Attribute Names If attribute names get updated, the names in the payload will reflect the update. Action - Send Visitor Data Parameters Parameter Description Webhook URL Required only if not provided in the Configuration tab. Overwrites the value defined in the Configuration tab if a value is provided. Include Current Visit Data Check this box if current visit data is to be included. Print Attribute Names If attribute names get updated, the names in the payload will reflect the update Action - Send Customized Data (Advanced) Parameters Parameter Description Webhook URL Required only if not provided in the Configuration tab. Overwrites the value defined in the Configuration tab if a value is provided. Custom Message Definition Map values to names for simple one level JSON format, otherwise reference template name, select only the Custom Message Definition option, and ensure your template is valid JSON. For template support, reference the template name to generate message data from a template. Template Variables Optional. Provide template variables as data input for templates. (Learn more) 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 message data. (Learn more) Templates are injected by name with double curly braces into supported fields. Example: {{SomeTemplateName}} ... View more

This article describes how to set up the Adobe Campaign Standard connector in your Customer Data Hub account. This connector is currently available as an Experiment. (Learn more) In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send Transactional Event ✓ ✗ Trigger Signal Activity ✓ ✗ 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: Technical Account ID The Technical Account ID can be found in the Adobe I/O Console. For more information see Authenticating and accessing Adobe Experience Platform APIs. Organization ID The Organization ID can be found in the Adobe I/O Console. Tenant ID The Tenant ID can be found in your Adobe Marketing Cloud URL. Example: https://yourtenantid.experiencecloud.adobe.com/campaign.html API Key The API Key (Client ID) can be found in the Adobe I/O Console. Secret Key The Client Secret can be found in the Adobe I/O Console. Private Key The Private Key is generated as part of creating an integration in the Adobe Console. For more information see: Authenticating and accessing Adobe Experience Platform APIs . 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 Transactional Event Parameters Parameter Description Email Required. The email address of the recipient. Event ID Required. The type of event you want to send. This ID is generated when creating the event definition. For additional information, see the Adobe Campaign Documentation . Expiration Date Optional. The sending of the transactional event will be cancelled after this date. Scheduled Send Date Optional. The transactional event will be processed and the transactional message will be sent at this date. Template Name If using a template to pass data, input with "Transactional Message Content Template" and enter name of main template. Do not include double curly braces in name, for example, use  SomeTemplateName not {{SomeTemplateName}} . Template Variables Provide template variables as data input for "Transactional Message Content Template". For additional 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. Transactional Message Content Template Template describing enriched transactional message content. Templates are injected by name with double curly braces into supported fields. Example: {{SomeTemplateName}} For additional information about using enriched message content, see Adobe's Campaign Documentation. Action - Trigger Signal Activity Parameters Parameter Description Workflow ID The ID of the workflow configured in your Adobe console. Source Used to indicate the triggering request source. Parameter Map It is possible to call a workflow with parameters. Map a parameter's value to it's name. String, Number, Boolean, and Date/Time types are supported. ... View more

This article describes how to set up the Criteo Audience Match (Customer-Provided Credentials) connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add User to Audience ✓ ✓ Remove User from 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: Advertiser ID Your Advertiser ID associated with an integration in your Criteo account. Client ID Your Client ID associated with an integration in your Criteo account. Client Secret Your Client Secret associated with an integration in your Criteo 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 - Add User to Audience Parameters Parameter Description Audience Select an audience to add user to, or provide an audience ID directly. Email (Plain/As is) Plain email, as-is Email (MD5) Email as an MD5 hash Email (SHA256 of MD5) Email as a SHA256 hash of MD5 Mobile ID Mobilie ID Identity Link Identity Link Gum ID Gum ID Action - Remove User from Audience Parameters Parameter Description Audience Select an audience to remove user from. Email (Plain/As is) Plain email, as-is Email (MD5) Email as an MD5 hash Email (SHA256 of MD5) Email as a SHA256 hash of MD5 Mobile ID Mobile ID Identity Link Identity Link Gum ID Gum ID ... View more

This article describes how to set up the Adestra connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Create or Update Contact ✓ ✓ Add Contact To List ✓ ✓ Remove Contact From List ✓ ✓ Send Email ✓ ✓ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: API Key: Required: Adestra account API key, see: Create API Token Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Create or Update Contact Parameters Parameter Description Update Strategy Required. Select applicable update strategy. Create Only Look up an existing contact and if not found, create a new contact. Update Only Look up an existing contact and update it. Create or Update Look up an existing contact and if found, update it, otherwise create a new contact. Core Table Required. Select the core table to create or update the contact in. Contact Lookup Email Address Required. Email address to lookup contact. Action - Add Contact To List Parameters Parameter Description Core Table Required. Select the core table the contact belongs to. Contact Lookup Email Address Required. Email address to lookup contact. List Required. List to add the contact to. Action - Remove Contact From List Parameters Parameter Description Core Table Required. Core tables store contacts in Adestra. Select the core table the contact belongs to. Contact Email Address Required. Email address to lookup contact. List Required. List to remove the contact from. Action - Send Email Parameters Parameter Description Email Campaign Required. Select the campaign to be launched. Contact Email Address Required. Email address to send email to. Transaction Data Required. Template data to set within the email campaign. ... View more

This article describes how to set up Oracle's Eloqua Custom Object (Bulk) connector service in your Customer Data Hub account. In this article: Table of Contents Placeholder Requirements Eloqua account Company name for your Eloqua account Username for your Eloqua account Password for your Eloqua account Supported Actions Action Name AudienceStream EventStream Import Custom Objects ✓ ✗ 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 required settings: Company Username 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 - Import Custom Objects Parameters Parameter Description Action Name The name for this specific action Action Categories Example: Email These categories are presented to your users via the consent prompt and consent preferences feature. Users can opt-in or opt-out of tracking based on these categories Source Select data source Custom Object Required. Select custom object. ... View more

This article describes how to set up the Webtrekk 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: Track Domain Required. Defined by Webtrekk, for example: track.webtrekk.net Webtrekk Tracking ID Required. Defined by Webtrekk, for example:  111111111111111 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 Client Time   Color Depth   Content ID   Cookies Activated   Java Activated   Javascript Enabled   Monitor Resolution   Referrer URL   Version   Window Size   Custom Ever-ID   Ever-ID   Referer   User Agent   User IP   E-Commerce Product Parameters Map array and list values to keys to be passed to Webtrekk. All arrays and lists should be of equal length. Single value attributes will be expanded to an array which is the same length as all other arrays, repeating the value. For a list of parameters that can be sent to Webtrekk. See Which parameters can be sent to Webtrekk Template Variables Provide template variables for message data. See: 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 Templates Optional: provide templates to be referenced in query parameters. See: Templates Guide Templates are injected by name with double curly braces into supported fields, for example: {{SomeTemplateName}})   ... View more

BlueKai allows creating audiences across hundreds of data sources, so you can activate it on any channel, including display, social, and mobile. This article describes how to set up the Oracle BlueKai Mobile connector in your Customer Data Hub account. 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: Provided by your BlueKai container, associating your desktop and mobile sites in the BlueKai platform. 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 User Agent If provided, the value will be used in "User-Agent" header If not specified, defaults to "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36" User ID Type Type of user identifier See ID Swapping guidelines on BlueKai website User ID Value Value of user identifier ID Hashing Check to hash the user ID Email and phone number must be hashed Hash Type Choose hashing algorithm Email address and phone number must be hashed with either MD5 or SHA256 ANDROIDID must be hashed with either with MD5 or SHA1 ADID and IDFA must be hashed with either with MD5 or SHA1 or not hashed at all Phints Provide phints as key-value pairs values on the left will be assigned to the keys on the right Additional Data Provide additional data as key-value pairs No additional processing will be used for this data ... View more

Amazon Kinesis Data Firehose (also known as Amazon Firehose) provides a simple way to capture, transform, and load streaming data with just a few clicks in the AWS Management Console. This article describes how to configure Amazon Firehose in your Customer Data Hub account. Table of Contents Placeholder Requirements An AWS account. Required: firehose:PutRecord permission. Optional: firehose:ListDeliveryStreams permission. Delivery stream to send data to. Supported Actions Action Name Trigger on Audience Trigger on Streams Send Event Data to Delivery Stream ✗ ✓ Send Visitor Data to Delivery Stream ✓ ✗ Send Customized Data to Delivery Stream ✓ ✓ Configure Settings Go to the Connector Marketplace and add a new Amazon Firehose Connector. See the Connector Overview article for general instructions on how to add a connector. To configure your vendor, follow these steps: In the Configure tab, provide a title for the connector instance. Provide your IAM user access and secret key. The policy statement attached to your IAM user instance must include the firehose:PutRecord permission. For more details on policies for Firehose, see: Access Control for Amazon Firehose. Select the region where you want to make the API calls. Assume Role Parameters: Required only if your IAM User is not setup with all necessary permissions. For more information, see: Switching to an IAM Role. ARN (Required): Amazon Resource Name assigned to the role to assume. Session Name (Required): Unique identifier of the assumed role session. External ID (Optional): Unique identifier used by third parties when assuming roles in their customers' accounts. For more information, see: How to Use an External ID. Click Test Connection to verify API connectivity with the provided credentials. Action Settings: Parameters and Options Click Next or go to the Actions tab. It's where you'll set up actions to trigger. This section describes how to set up parameters and options for each action. Action: Send Event Data to Delivery Steam Parameters Delivery Stream (Required): Select delivery stream to send data to. In order to see available streams, the firehose:ListDeliveryStreams permission must be granted. Record Suffix: Select a value to append to the visitor data for the purposes of identifying individual records. Print Attribute Names: Checking this box will display names for each event data attribute in the message payload. Options: Record Suffix Option Description Newline (\n) Adds a return character to the end of the visitor data object. No Delimiter When selected, nothing is added to the visitor data object. Action: Send Visitor Data to Delivery Steam Parameters Delivery Stream (Required): Select delivery stream to send data to. In order to see available streams, the firehose:ListDeliveryStreams permission must be granted. Record Suffix: Select a value to append to the visitor data for the purposes of identifying individual records. Include Current Visit Data: Checking this box will include current visit data in the message payload. Print Attribute Names: Checking this box will display names for each visitor data Attribute in the message payload. Options: Record Suffix Option Description Newline (\n) Adds a return character to the end of the visitor data object. No Delimiter When selected, nothing is added to the visitor data object. Action: Send Customized Data to Delivery Steam (Advanced) Parameters Delivery Stream (Required): Select delivery stream to send data to. In order to see available streams, the firehose:ListDeliveryStreams permission must be granted. Record Suffix: Select a value to append to the visitor data for the purposes of identifying individual records. Message Data (Required): Construct a custom message body. Map attribute(s) to names for simple one level JSON format, or reference a template name (surrounded in double curly braces) and select the Custom Message Definition option. Message Template Variables: Map attribute(s) to template variable names. Template variables are available for substitution and rendering of all templates. Refer to our Template Variables Guide for details. Message Templates: Provide one or more template to render. Typically, a single template is used to construct a message data. Refer to our Templates Guide for common syntax and extensions. Options: Record Suffix Option Description Newline (\n) Adds a return character to the end of the visitor data object. No Delimiter When selected, nothing is added to the visitor data object. Vendor Documentation What Is Amazon Kinesis Data Firehose? Amazon Kinesis Data Firehose Limits Access Control for Amazon Kinesis Firehose Switching to an IAM Role How to Use an External ID ... View more