Tealium Learning Center

This article describes how to set up the Google Ads Enhanced Conversions - Legacy connector. This connector is now deprecated and should only be used if you are running app incrementality studies. For the current connector, see the Google Ads Enhanced Conversions for Web connector. In this article: API Information This connector uses the following vendor API: API Name: Google Enhanced Conversion API API Version: v1 API Endpoint: https://www.google.com/ads/event/api/ Connector Actions Action Name AudienceStream EventStream Send Conversion ✓ ✓ 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 - Send Conversion Parameters Parameter Description Conversion Tracking ID Required The numeric value from AW-123456789 that uniquely identifies your advertiser account. Omit AW- from the mapped value. Conversion Label Encoded conversion tracking ID and conversion type. Conversion Type Type of the conversion. Only used if you do not have access to label as the advertiser. Conversion Value The monetary value of the conversion for the advertiser. Default value is $1 (USD) Currency Code Currency associated with the conversion value. This is the ISO 4217 3-character currency code. Default value is USD . Examples: USD , EUR Conversion Time Unix time since epoch, in microseconds. The default value is now . Transaction ID Required ID that uniquely identifies a conversion event, generated by you as the advertiser. Google Click ID The Google Click ID ( gclid) that led to the user conversion, where available. User Agent User agent for the user that converted, if the data is retained by advertiser. Email User email at point of conversion. Use array type attributes to add multiple emails, phone numbers and addresses. At least one of the following must be provided: User email User full name and address Phone Number Phone may be provided in conjunction with email or full name and address. Use array type attributes to add multiple emails, phone numbers and addresses. User phone number at point of conversion. E.164 standard format: +prefix, country code, subscribe number Example: +14150000000 Address: First Name User first name. For address, all data fields must be provided (first name, last name, street address, city, region, postal code, country). Use array type attributes to add multiple emails, phone numbers and addresses. Address: Last Name User last name. For address, all data fields must be provided (first name, last name, street address, city, region, postal code, country). Use array type attributes to add multiple emails, phone numbers and addresses. Address: Street User street address. For address, all data fields must be provided (first name, last name, street address, city, region, postal code, country). Use array type attributes to add multiple emails, phone numbers and addresses. Address: City User city name. For address, all data fields must be provided (first name, last name, street address, city, region, postal code, country). Use array type attributes to add multiple emails, phone numbers and addresses. Address: Region User Province, State, or Region. For address, all data fields must be provided (first name, last name, street address, city, region, postal code, country). Use array type attributes to add multiple emails, phone numbers and addresses. Address: Postal Code User post code. For address, all data fields must be provided (first name, last name, street address, city, region, postal code, country). Use array type attributes to add multiple emails, phone numbers and addresses. Address: Country User 3-letter country code in ISO 3166-1 alpha-3 format. For address, all data fields must be provided (first name, last name, street address, city, region, postal code, country). Use array type attributes to add multiple emails, phone numbers and addresses. Customer Data Hashing Optional Check if mapped customer data (email, phone, first name, last name, street address) is already hashed using a websafe-base 64 eoncoded SHA-256 hash. This is not the same as base64 encoding a SHA-256 string. Convert any existing SHA-256 strings to binary before base64 encoding. App Conversion for Incrementality Study Optional Check if this action is related to a conversion event for an incrementality study. Conversion Data for Incrementality Study Optional Map one to many miscellaneous data fields for use in the incrementality study for this conversion event. Common Errors and Troubleshooting The following are some common error codes and resolutions: INVALID_CONVERSION_DATA: Data for the conversion is not valid. Possible action failures are: No valid conversion_type or label is provided in the url or json payload: If label is not provided, then conversion_type is required. Ensure one of these has a populated value for the mapped attribute. The conversion_time provided in the url or json payload is too old.: Ensure that the mapped timestamp is in the correct format, for example: 2022-08-01 00:06:06+00:01. Alternatively, remove the mapping and allow the connector to send the default current timestamp. INVALID_USER_CUSTOMER_AUTHORIZATION: Confirm that the customer ID in the connector configuration does not include AW- . The authenticated user must have at least read-only access to the account owning the conversion action. Invalid Parameter - Action has invalid parameter value or missing required parameter / Either Email or Full Name & Address need to be provided: Required PII for Enhanced Conversions are either of the following sets: a) customer email b) customer first name, last name, street address, city, state, country, and zip code Ensure that required field values are present in the event data. ... View more

This article describes how to set up the Acoustic Transact (formerly Silverpop Transact) connector. Connector Actions Action Name AudienceStream EventStream Send Transactional Email ✓ ✗ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: API OAuth2 Client ID Required OAuth2 Client ID Contact Acoustic Support for assistance. API OAuth2 Client Secret Required OAuth2 Client Secret Contact Acoustic Support for assistance. API OAuth2 Refresh Token Required OAuth2 Client Refresh Token Contact Acoustic Support for assistance. Transact API Pod Number Required Your transact server number, which usually matches your Acoustic Campaign Organization Pod number. Hint: In the example transact-campaign-us-X.goacoustic.com , " X " is your pod number. Contact Acoustic Support for assistance. Transact API Region Required Your server region. Hint: In the example transact-campaign-ZZ-5.goacoustic.com , " ZZ " is your region. If not provided, " us " region is used by default. Contact Acoustic Support for assistance. Action Settings - Parameters and Options Click Next or go to the Actions tab to configure connector actions. This section describes how to set up parameters and options for each action. Action - Send Transactional Email Parameters Parameter Description Campaign ID Required ID of the Transact Automated Message Group that is used for th mailing. Recipient Email Required The email address to which the transactional email is sent. Transaction ID Optional Used by the sender to uniquely identify a transaction. The value that is specified is returned in the Response Document if used in the original request. Save Column(s) Optional A list of column names from the recipient elements to save to the database in Acoustic Campaign. The column names are case sensitive and must match what was specified in Acoustic Campaign. If you do not use this element, Acoustic Campaign will not save any column names. Content/Body Type Required Parameter to define if the content body is HTML only or TEXT only. Content Personalization (Map TAG Value to TAG Name) Required At least one personalization block is required for providing the content for the email to be sent. Each Personalization element contains one Name/Value pair. Map Tag Value to Tag Name Where: Tag Name specifies the name of the personalization string used in the body of the mailing template for the mailing, and Tag Value specifies the value of the corresponding TAG_NAME element. Tag Names must exactly match the fields used in Acoustic Campaign. Boolean values (true, false) must be in lowercase. The Transact server does not process any code (logic or transformation) placed in text or CDATA content, including anything inserted by Template fields. If the text contains angle brackets ( < or > ), you must enclose it within a CDATA section. ... View more

This article describes how to set up the Insightly CRM connector. In this article: Supported Actions Action Name Trigger on Audience Trigger on Streams Add a Contact ✓ ✓ Update a Contact ✓ ✓ Add a Lead ✓ ✓ Update a Lead ✓ ✓ API Information This connector uses the following vendor API: API Name: Insightly API API Version: v3.1 API Endpoint: https://api..insightly.com/ Documentation: Insightly API Configure Settings Go to the Connector Marketplace and add a new Insightly Connector. Read the Connector Overview article for general instructions on how to add a connector. To configure the connector, follow these steps: In the Configure tab, provide the API Pod and the API Key for your Insightly account. To obtain this information, log in to your Insightly account and select the User Settings section. In the API sub-section, find the API Key and the API URL. The API URL has the following format: https://api.{pod}.insightly.com/v3.1/ Example: If your API URL is https://api.na1.insightly.com , the API Pod is na1 . For more information, see: Insightly: Finding Your API key or URL and resetting your key. 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: Add a Contact This action allows you to create a new contact in the Insightly CRM. Parameters Attributes Required Contact attributes. First Name is required, other attributes are optional. Custom Fields Optional If provided, these fields are sent as a list of CUSTOMFIELDS objects. Tags Optional If provided, these fields are sent as a list of TAGS objects. Action: Update a Contact This action allows you to update an existing contact in the Insightly CRM. Parameters Attributes Required Contact attributes. Contact ID is required, other attributes are optional. Custom Fields Optional If provided, these fields are sent as a list of CUSTOMFIELDS objects. Tags Optional If provided, these fields are sent as a list of TAGS objects. Action: Add a Lead This action allows you to create a new lead in the Insightly CRM. Parameters Attributes Required Lead attributes. Last Name is required, other attributes are optional. Custom Fields Optional If provided, these fields are sent as a list of CUSTOMFIELDS objects. Tags Optional If provided, these fields are sent as a list of TAGS objects. Action: Update a Lead This action allows to update an existing lead in the Insightly CRM. Parameters Attributes Required Lead attributes. Lead ID is required, other attributes are optional. Custom Fields Optional If provided, these fields are sent as a list of CUSTOMFIELDS objects. Tags Optional If provided, these fields are sent as a list of TAGS objects. Vendor Documentation Insightly Homepage Insightly API Documentation ... View more

This article describes how to set up the Amazon EventBridge connector. In this article: Connector Actions Action Name AudienceStream EventStream Send Event Data to Event Source ✗ ✓ Send Visitor Data to Event Source ✓ ✗ Send Customized Data to Event Source (Advanced) ✓ ✓ Configure Settings Navigate to the Connector Marketplace and add a new connector. For general instructions on how to add a connector, see the About Connectors article. After adding the connector, configure the following settings: Account ID Enter your Account ID. Region Required: select region. Click Done when you are finished configuring the connector. Action Settings — Parameters and Options Click Continue to configure the connector actions. Enter in a name for the action and then select the action type from the drop-down menu. The following section describes how to set up parameters and options for each action. Action — Send Event Data to Event Source Parameters Parameter Description Event Source Select partner event source to send data to. Detail Type A free-form string used to decide what fields to expect in the event detail. For more information about Detail Type, read Amazon EventBridge API PutPartnerEvents documentation. Resources AWS resources, identified by Amazon Resource Name (ARN), which the event primarily concerns. Any number, including zero, may be present. Print Attribute Names If attribute names get updated, the names in the payload will reflect the update. Action — Send Visitor Data to Event Source Parameters Parameter Description Event Source Select partner event source to send data to. Detail Type A free-form string used to decide what fields to expect in the event detail. Resources AWS resources, identified by Amazon Resource Name (ARN), which the event primarily concerns. Any number, including zero, may be present. Include Current Visit Data   Print Attribute Names If attribute names get updated, the names in the payload will reflect the update. Action — Send Customized Data to Event Source (Advanced) Parameters Parameter Description Event Source Select partner event source to send data to. Detail Type A free-form string used to decide what fields to expect in the event detail. Resources AWS resources, identified by Amazon Resource Name (ARN), which the event primarily concerns. Any number, including zero, may be present. Custom Message Definition   Message Template Variables Optional: provide template variables as data input for templates (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. Message Templates Optional: provide templates to be referenced in either URL, URL Parameter, Header or Body Data (see: Templates Guide). Templates are injected by name with double curly braces into supported fields (Example: {{SomeTemplateName}} ). ... View more

This article describes how to set up the Agillic Recipients connector. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add or Update Recipient ✓ ✓ Update Recipient Table Records ✓ ✓ Achieve 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: Client ID Required. Provide your web application client ID. For more information, see Getting Started with APIs: Authentication. Client Secret Required. Provide your web application client secret. Date Format Set the date format for the connector. If not specified, the default format dd.MM.yyyy is used. The date and timestamp format is unique to each Agillic account instance. Formats are defined in the Agillic Administration interface. For more information, see Getting Started with APIs: Dates and Time. Timestamp Format Set the timestamp format for the connector. If not specified, the default format dd.MM.yyyy is used. Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Add or Update Recipient Parameters Parameter Description Recipient ID Required. Map any unique Person Data, such as EMAIL or MOBILE. Use Recipient ID for general purpose. For more information, see APIs: Recipient API. Recipient Data Required. Map values to the Person Data fields. Action - Update Recipient Table Records Parameters Parameter Description Recipient ID Required. Map any unique Person Data, such as EMAIL or MOBILE. Use Recipient ID for general purpose. For more information, see APIs: Recipient API. Table Required. Table ID of the records that will be batch updated. Table Record Required. Map one or more values to each table record field. ID or Primary Key must be specified. Action - Achieve Event Parameters Parameter Description Recipient ID Required. Map any unique Person Data, such as EMAIL or MOBILE. Use Recipient ID for general purpose. For more information, see APIs: Recipient API. Event ID Required. Event ID to be achieved. ... View more

This article describes how to set up the Snapchat Audience Match connector using Tealium-provided credentials. For information about the deprecated version of the Snapchat connector, see Snapchat Connector Setup Guide. In this article: Prerequisites After adding the connector, you must invite "asintegrations@tealium.com" to your Snapchat Business manager with the "Member" role and assign to applicable Ad Account with the "Data Manager" role. This step may take up to three (3) working days for approval. You can confirm whether the invitation has been accepted by viewing the users in your Snapchat Ads account. For additional information, see: Manage Members and Roles. Batch Limits This connector uses batched requests to support high-volume data transfers to the vendor. Requests are queued until one of the following three (3) thresholds is met: Max number of requests: 50000 Max time since oldest request: 10 minutes Max size of requests: 1 MB Connector Actions Action Name AudienceStream EventStream Add User to Segment ✓ ✓ Remove User from Segment ✓ ✓ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: Ad Account ID Required. Provide the Ad Account ID found under the Ad Accounts section of your Snapchat Business Settings. Invite "asintegrations@tealium.com" to your Snapchat Business manager with the Member role and assign to applicable Ad Account with Data Manager role. 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 Segment Target segment to add user to. User Identifier Type User Identifiers can be of type Email, Mobile Ad ID, or Phone number. User Identifier User Identifiers can be passed as plain text or already normalized and hashed. You can normalize email addresses by trimming the leading and trailing whitespace and converting all characters to lowercase before hashing. Normalize the Mobile Advertiser ID Use all lowercase letters. Do not remove hyphens. Normalize phone numbers Include the country code. Remove any double zeros (0) in front of the country code. If the number itself begins with a zero (0), this should be removed. Exclude any non-numeric characters such as whitespace, parentheses, plus signs (+), or dashes (-). User Identifier Already Hashed Only configure one user identifier. The API supports matching via email or mobile identifier. Only use one identifier (either email or mobile ad ID) per action. For more information, see Snapchat API reference. Action - Remove User from Segment Parameters Parameter Description Segment Target segment to remove user from. User Identifier Type User Identifiers can be of type Email, Mobile Ad ID, or Phone number. User Identifier User Identifiers can be passed as plain text or already normalized and hashed. You can normalize email addresses by trimming the leading and trailing whitespace and converting all characters to lowercase before hashing. Normalize the Mobile Advertiser ID Use all lowercase letters. Do not remove hyphens. Normalize phone numbers Include the country code. Remove any double zeros (0) in front of the country code. If the number itself begins with a zero (0), this should be removed. Exclude any non-numeric characters such as whitespace, parentheses, plus signs (+), or dashes (-). User Identifier Already Hashed Only configure one user identifier. The API supports matching via email or mobile identifier. Only use one identifier (either email or mobile ad ID) per action. For more information, see Snapchat API reference. ... View more

This article describes how to set up the Salesforce Standard Objects connector. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Create or Update Standard Object ✓ ✓ Delete Standard Object ✓ ✓ 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 - Create or Update Standard Object Parameters Parameter Description Update Strategy Required Select applicable update strategy. Create Only Create new Standard Object without lookup. Update Only Look up an existing Standard Object and update it. Create or Update Look up an existing Standard Object and if found, update it, otherwise create a new item. Standard Object Select the applicable Standard Object to create or update. Action - Delete Standard Object Parameters Parameter Description Standard Object Type of Standard Object instance to delete. ... View more

This article describes how to set up the Facebook App Events connector in your Customer Data Hub account. In this article: Table of Contents Placeholder API Information This connector uses the following vendor API: API Name: Facebook Graph API - Marketing API API Version: v12.0 API Endpoint: https://graph.facebook.com Connector Actions Action Name AudienceStream EventStream Send Event ✓ ✓ How it Works Report app installs and in-app conversions through this API and send data back to Facebook Analytics. Use this on mobile devices without the Facebook SDK. For detailed information, see the Facebook App Events API documentation. 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: Application ID The App ID listed on your app dashboard at Facebook for Developers. 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 Data Processing Options Required Map value to LDU to have Facebook process event with Limited Data Use restrictions. Otherwise map "None" to specify that the event should not be processed with Limited Data Use restrictions. For more information, see Facebook Data Processing Options. Advertiser ID Required. Apple IDFA or Google Advertising ID. Advertiser Tracking Enabled Required. Options are 0 for disabled; 1 for enabled. App Tracking Enabled Required. Options are 0 for disabled; 1 for enabled. Attribution Required. Mobile cookie from a device. Applies to Android and pre-iOS 6 devices. For other devices, use advertiser_id . Client IP Address Required. Device's IP address in IPv4 or IPv6 format. Event Required. Type of event being sent via the App Events API. App User ID Optional. A unique combination of letters and numbers no more than 100 characters long stored on the device of the user. Bundle ID Optional. A unique string that identifies your application to the system. Bundle Short Version Optional. The publicly visible version of your app. Bundle Version Optional. The internal version number of your app. Data Processing Options Country Required if Data Processing Options is mapped to LDU. Map country code associated with user event. Accepted code values: "1" for the United States of America "0" to request country to be geolocated by Facebook Geolocation also requires mapping the "Client IP Address" attribute. Data Processing Options State Required if Data Processing Options is mapped to LDU. Map state code associated with user event. Accepted code values: "1000" for California "0" to request state to be geolocated by Facebook. Geolocation also requires also mapping the "Client IP Address" attribute. App Package Name Required. String for the app package name. Available Storage Size Required. Integer value for the available external storage space, in GB. Carrier Name Required. String for the carrier name. If the carrier name is not available, use "NoCarrier". CPU Cores Required. Integer for the number of CPU cores. Device Locale Required. String for two letters for the locale language in lowercase, concatenated with an underscore character (_) and two letters for the country code, in uppercase. Device Model Name Required. String for the device model name. Device Timezone Required. String for the device timezone. Device Timezone Abbreviation Required. String for the device timezone abbreviation. External Storage Size Required. Integer for the total external storage size, in GB. OS Version Required. String for the operating system version. Pkg Info Version Code Required. Integer for the PackageInfo version code. Pkg Info Version Name Required. String for the PackageInfo version name. Screen Density Required. Float for the screen density in the %.2f format. The decimal separator must be a dot. Screen Height Required. Integer for the screen height, in pixels. Screen Width Required. Integer for the screen width, in pixels. Extended Info Format Optional. Extended info format version and source indicator. Default value is a2. Event Name Select event from drop-down list or create a new event. _logTime Optional. Recommended parameter to specify the time of event, specified in Unix time. _valueToSum Optional. Numeric value of individual event to be summed in reporting. See above for recommended events to attach to. fb_content_id Optional. International Article Number (EAN), when applicable, or other product or content identifiers. fb_content_type Optional. For example, a music, video, or product description. fb_currency Optional. ISO 4217 code. Examples: EUR, USD, JPY. Required when passing _valueToSum as a price or a purchase amount. fb_description Optional. A string description. fb_level Optional. Level of a game. fb_max_rating_value Optional. Upper bounds of a rating scale, Example: 5 on a 5-star scale. fb_num_items Optional. Number of items. fb_payment_info_available Optional. Values are 1 for yes, 0 for no. fb_registration_method Optional. Facebook, Email, Twitter, etc. fb_search_string Optional. The text string that was searched for. fb_success Optional. Values are 1 for yes, 0 for no. IDs Optional. Product IDs. Array values of same length only, they will be paired in order when sent to Facebook. Quantities Optional. Product Quantities. Array values of same length only, they will be paired in order when sent to Facebook. Email Optional. Email address. First Name Optional. First Name. Last Name Optional. Last Name. Phone Optional. Phone Number. External ID Optional. Any unique ID from the advertiser, such as loyalty membership ID, user ID, and external cookie ID. Gender Optional. Options are f for female, m for male. If unknown, leave blank. Birthdate Optional. Birth year, month, then date. City Optional. City Name. State or Province Optional. Two-letter state or province code. Zip or Postal Code Optional. Numeric zip or postal code. Country Optional. Lowercase two-letter country code. User Data is Already SHA256 Hashed Optional. Check box if user data is already SHA256 hashed. ... View more

This article describes how to set up the Ytel connector. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send SMS ✓ ✗ 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: Account SID Found on the Ytel dashboard For more information, see Getting Started. Token Found on the Ytel dashboard. For more information, see 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 - Send SMS Parameters Parameter Description From The 10-digit SMS-enabled Ytel number, in E.164 format, that initiated the call. For more information, see Request Format. To The 10-digit phone number (E.164 format) that will receive the message. For more information, see Request Format. Body The body message that is to be sent in the text. Maximum GSM-7 message length is 160 characters per message. Maximum Unicode message length is 70 characters per message. Additional messages are created automatically to send text beyond the maximum message length. Action - Send Email Parameters Parameter Description To A valid address that will receive the email. For more information, see Send Email. Type Specifies the type of email to be sent. Values are text or HTML. Subject The subject of the mail. Must be a valid string. Message The email message that is to be sent in the text. From A valid address that will send the email. CC Carbon copy. A valid address that will receive the email. BCC Blind carbon copy. A valid address that will receive the email. ... View more

This article describes how to set up the Responsys Marketing Cloud connector. In this article: Connector Actions Action Name AudienceStream EventStream Merge List Recipients ✓ ✓ Merge Profile Extension Recipients ✓ ✓ Merge Table Records ✓ ✓ Trigger Custom Event ✓ ✓ Batch Limits This connector uses batched requests to support high-volume data transfers to the vendor. Requests are queued until one of the following three (3) thresholds is met: Max number of requests: 100 Max time since oldest request: 60 minutes Max size of requests: 1 MB Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: API Username API Password Login 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 - Merge List Recipients Parameters Parameter Description List Name Required Default Permission Status Optional Values are Opt In or Opt Out. Match Columns Optional The column name to be used to match the recipient record to the Profile Extension records. Match Operator Optional Operator to join match column names. Update Strategy Optional Controls how the existing record should be updated. No Update When selected, if an existing record is matched, no update will happen (Insert only). Replace All When selected, if an existing record is matched, all the properties configured will be updated. HTML Value Optional Value of incoming preferred email format data. Example: H may represent a preference for HTML-formatted email. Opt In Value Optional Value of incoming opt-in status data that represents an opt-in status. Example: I may represent an opt-in status. Opt Out Value Optional Value of incoming opt-out status data that represents an opt-out status. Example: O may represent an opt-out status. Reject Record if Channel Empty Optional String containing a comma-separated channel codes that will result in record rejection when the channel address filed is null. Channel codes are: E – Email M – Mobile P – Postal Code Example" "E,M" indicates that a record that has a null value for the email or mobile number value should be rejected. Text Value Optional Value of incoming preferred email format data. Example: T may represent a preference for text-formatted email. Action - Merge Profile Extension Recipients Parameters Parameter Description List Name Required Profile Extension Table (PET) Name Profile extension table name. Update Strategy Required Controls how the existing record should be updated. No Update When selected, if an existing record is matched, no update will happen (Insert only). Replace All When selected, if an existing record is matched, all the properties configured will be updated. Match Columns The column name to be used to match the recipient record to the profile extension records. Options are: Recipient ID (RIID) Customer ID Email Address Mobile Number Email (MD5 hashed) Email (SHA 256 hashed) Map Template Name Optional Specify a mapping template configured in Responsys. Action - Merge Table Records Parameters Parameter Description Folder Name Required Table Name Required Update Strategy Required Controls how the existing record should be updated. No Update When selected, if an existing record is matched, no update will happen (Insert only). Replace All When selected, if an existing record is matched, all the properties configured will be updated. Match Columns The column name to be used to match the recipient record to the Supplemental Table records. Map Template Name Optional Specify a mapping template configured in Responsys. Action - Trigger Custom Event Parameters Parameter Description Event Name Required Custom Event Name Folder Name Required Object Name Required Profile List Name Email Format Required Values are Text or HTML. Customer ID Customer ID Email Address Email Address Mobile Number Mobile Number Mobile Number Mobile Number Number Data Mapping Optional Date Data Mapping Optional String Data Mapping Optional Optional Data Optional Vendor Documentation Oracle Marketing Cloud - Responsys API ... View more

This article describes how to set up the Twitter Campaigns connector. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add Targeting Criteria to Line Item ✓ ✗ Remove Targeting Criteria from Line Item ✓ ✗ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: Ad Account ID Required. Provide your Twitter Ad Account ID. Your Account ID can be located in your the URL for your account when logged in. Example: If the URL is https://ads.twitter.com/accounts/1234abcd/ , the account ID is 1234abcd . 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 Targeting Criteria to Line Item Parameters Parameter Description Line Item Required The line item to update. Broad Keyword Broad Keyword Exact Keyword Exact Keyword Followers of User Followers of User Interest Interest Negative Exact Keyword Negative Exact Keyword Negative Keyword Negative Keyword Negative Phrase Keyword Negative Phrase Keyword Phrase Keyword Phrase Keyword Similar to Followers of User Similar to Followers of User Action - Remove Targeting Criteria from Line Item Parameters Parameter Description Line Item Required. The line item to update. Targeting Criteria Required. Targeting Criteria to remove from Line Item. ... View more

This article describes how to set up the Sailthru connector. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add User to List ✓ ✗ Remove User from List ✓ ✗ Add User to List (Batch Job) ✓ ✗ Remove User from List (Batch Job) ✓ ✗ Send Transactional Email ✓ ✗ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: API Key API Key to access Sailthru account features. Shared Secret Sailthru account shared secret. Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Add User to List Parameters Parameter Description Sailthru List Primary or Secondary List to add User to. User Facebook ID Map to User Facebook ID Sailthru Horizon Cookie Map to Sailthru Horizon Cookie User SMS Map to User SMS User Specified Identifier Map to User-Specified Identifier User Email Map to User Email User Twitter Name Map to User Twitter Name Sailthru Identifier Map to Sailthru Identifier Action - Remove User from List Parameters Parameter Description Sailthru List Primary or Secondary List to remove User from User Facebook ID Map to User Facebook ID Sailthru Horizon Cookie Map to Sailthru Horizon Cookie User SMS Map to User SMS User Specified Identifier Map to User-Specified Identifier User Email Map to User Email User Twitter Name Map to User Twitter Name Sailthru Identifier Map to Sailthru Identifier Action - Add User to List (Batch Job) Batch Limits This action uses batched requests to support high-volume data transfers to the vendor. Requests are queued until one of the following three (3) thresholds is met: Max number of requests: 10000 Max time since oldest request: 10 minutes Max size of requests: 10 MB Parameters Parameter Description Sailthru List Select one or more lists to add user to. User Facebook ID Map to User Facebook ID Sailthru Horizon Cookie Map to Sailthru Horizon Cookie User SMS Map to User SMS User Specified Identifier Map to User-Specified Identifier User Email Map to User Email User Twitter Name Map to User Twitter Name Sailthru Identifier Map to Sailthru Identifier User Custom Variables Set custom variables on the user. Opt Out Must be one of the following: all, basic, blast or none Signup date User signup date. Action - Remove User from List (Batch Job) Batch Limits This action uses batched requests to support high-volume data transfers to the vendor. Requests are queued until one of the following three (3) thresholds is met: Max number of requests: 10000 Max time since oldest request: 10 minutes Max size of requests: 10 MB Parameters Parameter Description Sailthru List Select one or more lists to remove user from. User Facebook ID Map to User Facebook ID Sailthru Horizon Cookie Map to Sailthru Horizon Cookie User SMS Map to User SMS User Specified Identifier Map to User-Specified Identifier User Email Map to User Email User Twitter Name Map to User Twitter Name Sailthru Identifier Map to Sailthru Identifier User Custom Variables Set custom variables on the user. Opt Out Must be one of the following: all, basic, blast or none. Signup date User signup date. Action - Send Transactional Email Parameters Parameter Description To Email address of user to receive this email Email Template Email to send to user Email Variable Substitutions Replace variables in the provided email template with your Tealium data. This will overwrite vars stored on the user. Conversely, a var that is not assigned defaults to what is stored on the user. Email List Substitutions Requires array type in data layer. The data is formatted correctly to be passed. Replace list variables in the provided email template with your Tealium data. This will overwrite vars stored on the user. Conversely, a var that is not assigned defaults to what is stored on the user. ... View more

This article describes how to set up the Sendwithus connector. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send an Email ✓ ✗ Create a New Customer ✓ ✗ Delete a Customer ✓ ✗ Activate a Drip Campaign for a 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 Sendwithus account. For more information, see Sendwithus 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 an Email Parameters Parameter Description Template The ID of the template to send. For more information, see: Send API. Recipient Address The recipient's email address Recipient Name The recipient's name. Sender Address The sender's email address. Reply To The sender's reply-to address. Sender Name The sender's name. Template Data Email template data. ESP Account ID of the ESP Account to send this email through. Locale Template locale to send. Version Name Name of the template version to send. Overrides A/B tests. Action - Create a New Customer Parameters Parameter Description Email The email address of the customer. For more information, see: Customers API. Locale A locale for the customer. Action - Delete a Customer Parameters Parameter Description Email Email address of the customer to be deleted. For more information, see: Customers API. Action - Activate a Drip Campaign for a Customer Parameters Parameter Description Drip Campaign ID The ID of the drip campaign to be activated for the customer. For more information, see: Customers API. Recipient Address The recipient's email address. Recipient Name The name of the recipient. Sender Address The sender's email address. Reply To The sender's reply-to address. Email Data Email template data. ESP Account ID of the ESP Account to send this email through. Locale Locale to send emails with. ... View more

This article provides best practices and recommendations for retraining a model. In this article: Table of Contents Placeholder About Retraining Although machine learning and statistics tools are not designed to guarantee future performance, following simple guidelines can improve performance results and reduce potential clutter from attempting to create more models instead of retraining those already in place. The following sections provide general guidelines and best practices about retraining both trained and deployed models. For information about how to retrain a model, see Retraining a Model. Estimating the Number of Trainings Needed Estimating the number of trainings a model may need is more of a machine learning art than a science. Fine tuning a model requires multiple trainings (1 to 3 is normal) and adjustments to the attributes to exclude. When a model starts to degrade, a retraining produces a better result at first, but then slowly begins to degrade again as time elapses. Typically, each trained version of a model takes longer to degrade as the training date range gets longer. Identifying a Degraded Model There are two main factors that contribute to model degradation: the amount of time since the last training and the volume of new data received by the model. A model in training is only a snapshot, whereas a deployed is model is live. If the score for a deployed model is lower than the score for the trained model, this indicates that the model has degraded and needs retraining. Deploying a Newly-Trained Version with a Higher Score When the current deployed version of a model has a low performance score and you retrain it to create a new version with a higher score, deploy the retrained version to ensure that the best version of the model is deployed. It is not recommended to recreate a second similar model in an attempt to achieve a higher score. A second model is not likely to provide any additional benefit and it can add clutter to your implementation. When a Retrained Version has a Lower Score A lowered score for a deployed model makes it evident that the model is starting to degrade and needs to be retrained to improve performance. However, sometimes a model that has begun to degrade, and is retrained, will have a lower score than the deployed model. In this scenario, the newly trained model should not be deployed in place of the current model. Adjustments and retraining should continue until the score for the retrained model is higher than the initial degraded model score. Only when the score is higher should the new model be deployed. Low F1 Scores and Rapid Degradation If a model has a low F1 score after being trained, and it degrades rapidly, one or both of the following issues: Inconsistent Data The behavior of your visitors is changing or inconsistent within the timeframe used for training the model as compared to the present. Incomplete Data You might need additional visitor attributes for a more complete view of visitor behavior. Retraining Frequency The need to retrain models is not specific to the Tealium Predict product, but to machine learning in general. The frequency that you retrain depends on your data, which differs greatly between businesses. In general, longer training date ranges most often create models that degrade more slowly. Retraining is typically needed when a model quality degrades below a predetermined score that is acceptable to your organization. Retraining vs. Deleting Consider retraining a model before deleting it. When you delete a model, you lose the training history. When you retrain, each training can have a different configuration in terms of time frame, excluded attributes, and data added over time. You can then view the differences between versions (individual trainings) to decide which version to deploy. External Impacts on Model Training When the world, businesses, and visitor behavior shift rapidly, a model that normally takes months to degrade can degrade more rapidly than expected. The following external issues can potentially impact model training and results. Global Issues Global issues that impact markets, such as the COVID-19 pandemic of 2020, do impact models to some extent. Though these types of issues can make it difficult to get a clear picture of your visitor behavior, it is easy to retrain a new version and then seamlessly deploy it without the manually intensive process of retuning over and over using valuable engineering and data staff resources. Marketing Campaigns Models are sometimes trained simultaneously with other activities, such as an ad campaign, a major holiday, unseasonable heat, mass riots, or political upheavals. When activity ceases or no longer applies, your current model may not function as well as it did during training. In addition to retraining your models, you can include attributes in your models that represent these events. Data Distribution Considerations For a model to accurately predict, the data for the basis of the predictions must have a similar distribution to the data on which the model was trained. As data distribution drifts over time, model deployment is not a one time task, but a continuous process. It is a best practice to continuously monitor your incoming data and retrain your model on newer data when you know that your data distribution has deviated from the original training data distribution. If monitoring data to detect changes in data distribution has a high overhead, you can simply retrain your model periodically, such as daily, weekly, or monthly. Additional Information For information about how to retrain a model, see Retraining a Model. ... View more

This article describes how to set up the Reply.ai connector. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add or Update 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 Token Your Reply.ai API Token found in your 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 or Update Contact Parameters Parameter Description URN A Uniform Resource Name (URN) you want associated with the new contact (Optional), or The URN of the contact you want updated (required). Name The name of the contact. Contact UUID Optional. The Universally Unique Identifier (UUID) of the contact to update, in string format. If not present, a new contact will be created. For more information, see: https://www.reply.ai/api/v1/contacts. Language Optional. The preferred language for the contact, in 3-letter ISO format. Group UUID The UUID of any groups this contact is part of. Fields The contact fields you want to set or update on this contact. ... View more

This article describes how to set up the New Relic Mobile connector. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send Mobile Application Metrics ✓ ✓ 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: New Relic Account ID See How to Register a New Relic Insights API Key for information about how to retrieve a New Relic account ID. New Relic REST API Key The REST API key is used to get information on available metrics, applications, and other account information. See How to Register a New Relic Insights API Key for information about how to retrieve a New Relic REST API Key. New Relic Insights API Key The Insights API key is used to insert data into New Relic Insights. See How to Register a New Relic Insights API Key for information about how to retrieve a New Relic Insights API Key. Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Send Mobile Application Metrics Parameters Parameter Description Mobile Application Browser Application to provide metrics on.  Provide a custom name if the application is not yet in New Relic Insights, or it will not be created. This will not create the application in the New Relic system, but will provide the ability to query the application in New Relic Insights. Event Category Event Category Event Type Optional The type of event this data will be saved under. The default value is Mobile Event Application Build Number Application Build Number New Relic Agent Version Number New Relic Agent Version Number City App is Located City App is Located Country App is Located Country App is Located Region App is Located Region App is Located Device Category Device Category Device Manufacturer Device Manufacturer Device Model Number Device Model Number Interaction Duration Interaction Duration Fresh App Install Fresh App Install Last Application Interaction Last Application Interaction Application Memory Usage Application Memory Usage User Session Duration User Session Duration User Session ID User Session ID Time Since Last Interaction Time Since Last Interaction Time Since Load Time Since Load Upgrade from Version Upgrade from Version New Relic Agent Version Number New Relic Agent Version Number Name of Interaction Name of Interaction ... View more

This article describes how to set up the New Relic Browser connector. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send Browser Application Metrics ✓ ✓ 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: New Relic Account ID See How to Register a New Relic Insights API Key for information about how to retrieve a New Relic account ID. New Relic REST API Key The REST API key is used to get information on available metrics, applications, and other account information. See How to Register a New Relic Insights API Key for information about how to retrieve a New Relic REST API Key. New Relic Insights API Key The Insights API key is used to insert data into New Relic Insights. See How to Register a New Relic Insights API Key for information about how to retrieve a New Relic Insights API Key. Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Send Browser Application Metrics Parameters Parameter Description New Relic Browser Application Browser Application to provide metrics on.  Provide a custom name if the application is not yet in New Relic Insights, or it will not be created. This will not create the application in the New Relic system, but will provide the ability to query the application in New Relic Insights. Event Category Event Category New Relic Application ID New Relic Application ID Server Side Application Name Server Side Application Name Autonomous System Number Autonomous System Number Autonomous System Number Latitude Autonomous System Number Latitude Autonomous System Number Longitude Autonomous System Number Longitude Autonomous System Number Organization Autonomous System Number Organization Backend Response Time Backend Response Time Transaction Name Transaction Name City City Time to Establish Server Connection Time to Establish Server Connection Country Code Country Code Device Type Device Type Time to Resolve Top-Level DNS Time to Resolve Top-Level DNS Time to Process Page Time to Process Page Front-end Browser Response Time Front-end Browser Response Time Name of Server Side Transaction Name of Server Side Transaction Total Network Wait Time Total Network Wait Time Time to Render Page Time to Render Page Original PageView URL Original PageView URL Time Waiting for Service Initiation Time Waiting for Service Initiation Region Code Region Code Time to Setup TLS Time to Setup TLS Session ID Session ID User Agent Name User Agent Name User Agent Version User Agent Version User Agent OS User Agent OS Name of Interaction Name of Interaction Name of Page Action Name of Page Action Browser Height Browser Height Browser Width Browser Width Current URL Current URL Referrer URL Referrer URL Time between Page Requested and PageAction Time between Page Requested and PageAction ... View more

This article describes how to set up the FullStory connector. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Delete 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 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 - Delete User Parameters Parameter Description User ID User ID is your application-specific ID you have given to the user that will have been passed through the FullStory tag. Use this feature to comply with Right to be Forgotten / Right to Erasure requests from your end users. For more information on this endpoint, see: https://help.fullstory.com/develop-rest/deleteindividual-api. Recommended best practice: Select hashed email as the identifier to be mapped to User ID in the FullStory tag. For more information on this recommendation or alternate approaches to selecting the User ID, contact your Tealium or FullStory representative. ... View more

This article describes how to get the most out of Tealium and Braze. In this article: Table of Contents Placeholder How it Works Braze is a comprehensive customer engagement platform for email, mobile, and web that powers relevant and memorable experiences between consumers and the brands they love. In 2019, Braze sent over 600 billion personalized emails, push notifications, in-app messages, SMS messages, and more to billions of consumers for leading brands like HBO, Walmart, and Postmates. Client-Side Integration The following table lists descriptions and prerequisites for the client-side Braze integration types and provides links to detailed setup documentation. Integration Type What to Expect from this Integration Product Requirements Setup Guides Braze Web SDK Tag With the Braze Web SDK, you can: Collect session data Identify users (with the Tealium unified data layer) Record purchases and custom events via a web/mobile browser. Implementing the Braze Web SDK enables you to create a more complete view of your users across web and mobile channels. You can also use the Web SDK to engage with your users by sending in-app web messages and web push notifications. Tealium iQ Tag Management Braze Web SDK Tag Setup Guide Server-Side Integration The following table lists descriptions and prerequisites for the server-side Braze integration types and provides links to detailed setup documentation. Integration Type What to Expect from this Integration Product Requirements Setup Guides Braze Connector This Braze integration allows you to further enrich your Braze data through AudienceStream and/or EventStream in order to build real-time, personalized, omnichannel experiences with your customers. The Track User action contains functionality that is the same for AudienceStream and EventStream. As a best practice, Tealium recommends using User Attribute features with AudienceStream and Event and Purchase features with EventStream. Use cases that do not fit these criteria may ignore this best practice. Tealium EventStream and/or Tealium AudienceStream Braze Connector Setup Guide Mobile Integration The following table lists descriptions and prerequisites for mobile Braze integration types and provides links to detailed setup documentation. Integration Type What to Expect from this Integration Product Requirements Setup Guides Braze Remote Commands This Braze integration uses the following: Native Braze SDK A remote command module that wraps the Braze methods. Braze Remote Command Tag A tag that translates event tracking into native Braze calls. This solution leverages the convenience of Tag Management to configure a native Braze implementation without having to add vendor-specific code to your app. Adding the Braze remote command module to your app automatically installs and builds the required Braze libraries. If you are using a dependency manager installation, there is no need to install the Braze SDK separately. Tealium iQ Tag Management Remote Command: Braze ... View more

This article describes how to get the most out of Tealium and Optimizely and enable the transmission of Tealium audiences and audience badges to Optimizely. In this article: Table of Contents Placeholder How it Works The Optimizely platform includes technologies for modern software development, such as feature flags, A/B testing at scale, AI-powered personalization, and streaming analytics. Experiments and feature flags are run on the Optimizely platform to assist in understanding what works and what does not work, thus eliminating guesswork. See the Tealium + Optimizely Technology Partnership Overview for more information. Client-Side Integrations The following table lists the description and prerequisites for client-side integrations of the Optimizely tag and provides links to detailed setup documentation: Integration Type What to Expect from this Integration Product Requirements Setup Guides Optimizely Tag Asynchronous Synchronous Tealium Optimizely Asynchronous and Synchronous tag integrations allow you to quickly and easily deploy Optimizely web projects by configuring Optimizely in Tealium iQ Tag Management. Asynchronous tags are loaded simultaneously, whereas synchronous tags are loaded sequentially, one after another. Tealium Tealium iQ Tag Management (Required) Optimizely Optimizely Account (Required) See the following setup guides: Asynchronous Synchronous Server-Side Integrations The following table lists descriptions and prerequisites for the server-side Optimizely Integration types and provides links to detailed setup documentation. Integration Type What to Expect from this Integration Product Requirements Setup Guides Optimizely Events Integrating with Tealium Optimizely Events allows you to send online and offline event data to Optimizely through Tealium EventStream. This method benefits all Optimizely products by allowing a comprehensive view of the customer for improved insights into conversions and campaign analytics that can be used to benefit the entire customer lifecycle experience. Tealium EventStream and/or AudienceStream (Required) Optimizely Optimizely Web or Full Stack (Required) See the following setup guide: Optimizely Events Connector Setup Guide (BETA)   Optimizely Dynamic Customer Profiles Integrating with Optimizely Dynamic Customer Profiles creates a single, actionable view of the customer by providing Optimizely with online and offline first-party data. By leveraging the Tealium AudienceStream Customer Data Platform (CDP), you can build profiles and audiences within Tealium that Optimizely and other channels can take action on. This integration allows mutual Tealium and Optimizely customers to deliver consistent, personalized web and mobile experiences for their most valuable customers, and measure the impact of the resulting experiences. Tealium EventStream and/or AudienceStream (Required) Optimizely Optimizely Web or Full Stack (Required)   See the following setup guide: Optimizely DCP Connector Setup Guide Additional Resources Optimizely Event API: Getting Started Optimizely: Create Audiences with Dynamic Customer Profiles Optimizely Integration with Tealium AudienceStream Integrating AudienceStream and Optimizely Full Stack Tealium Tool: Optimizely Helper ... View more

This article describes how to set up the Close.io connector. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Create a New Contact ✓ ✓ Update an Existing 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 The API key acts as the username. API keys are per organization and can be generated and deleted from the Close.io Settings page. Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Create a New Contact Parameters Parameter Description Lead ID The Lead ID can be found in the URL of the lead. For more information on this endpoint, see https://developer.close.io/#contacts. Name The name of the contact. Title The title of the contact. Phone The phone number of the contact. Phone Type The phone type. Example: office, mobile Email The email of the contact. Email Type The email type. For example: office, home URL Example: http://twitter.com/google/ URL Type Example: url Action - Update an Existing Contact Parameters Parameter Description Contact ID The Contact ID is assigned when the contact is created and is prefaced with cont_ . Example: cont_y7YAwBXugpmy4YEnmCJPnOTFHLLOnn6gDfoeNTOBp8T For more information on this endpoint, see https://developer.close.io/#contacts-update-an-existing-contact. Attributes Contact attributes you want to update. Action - Delete a Contact Parameters Parameter Description Contact ID The Contact ID is assigned when the contact is created and is prefaced with cont_ . Example: cont_y7YAwBXugpmy4YEnmCJPnOTFHLLOnn6gDfoeNTOBp8T For more information on this endpoint, see https://developer.close.io/#contacts-delete-a-contact. ... View more

This article describes how to set up the Campayn connector. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Basic Signup ✓ ✗ Unsubscribe 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 Your API key can be found in your Campayn account. For more information, see: Campayn API on GitHub. 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 - Basic Signup Parameters Parameter Description List ID ID of the list you are adding to. For more information, see: Campayn API Contacts on GitHub Email Email address of the user to be signed up. Fail On Duplicate Values are true or false. If true, the call will fail when user already exists. Action - Unsubscribe Contact Parameters Parameter Description List ID ID of the list the contact will be unsubscribed from. For more information, see: Campayn API Lists on GitHub Email Email address of the contact to be unsubscribed. ... View more

This article describes how to set up the Appcues connector. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Update User Profile ✓ ✗ Record User 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 Your Appcues Account ID. Found on the account settings page. Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Update User Profile Parameters Parameter Description User ID The end user ID of the profile to update. Properties Object containing arbitrary key-value data to update in the user's stored profile. For more information, see: Appcues HTTP API (Developer). Action - Record User Event Parameters Parameter Description User ID The end user ID of the profile to update. Event Name Event name. Maximum of 127 characters. This is the main mechanism for grouping and targeting on specific events. For more information, see: Appcues HTTP API (Developer). Timestamp Time at which the event occurred. Either integer format (as Unix time) or string format (as ISO-8601 compliant date, for example 2016-01-13T13:05:22.000Z). Event Attributes Event attributes ... View more

This article describes how to set up the Swrve App Events connector. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send Event ✓ ✓ 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: Application ID Required. Can be viewed on the Integration Settings screen of your Swrve application. API Key Type Required. Select applicable API key type. For more information, see: Managing your API Keys . API Key Required. Provide API key value. Region Required. Select applicable data center region. 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 ID Required Unique user identifier the event relates to. Event Name Required String The name of the event. Example: app_started The name can use dot notation to indicate a hierarchy. The name must contain only letters, numbers, dashes, underscores, and dots. The first string of valid characters is taken as the event name. For example, if the name level.start/ is supplied, it is interpreted as level.start . App Version The version of the application that the user is currently using. Custom Payload Map attributes to Custom Payload pairs. For more information, see: Custom Payload Guide. Action - Update User Parameters Parameter Description User ID Required Unique user identifier the event relates to. User Initiated If specified as false, then event does not count towards some performance indicators. If property has any other value or is not specified, then event counts towards all performance indicators as normal. App Version The version of the application that the user is currently using. Custom Payload Map attributes to Custom Payload pairs. For more information, see: Custom Payload Guide. ... View more

This article describes how to set up the Google Ads Conversions connector. In this article: Connector Actions Action Name AudienceStream EventStream Upload Call Conversion ✓ ✓ Upload Click Conversion ✓ ✓ Conversion Restatement ✓ ✓ Conversion Retraction ✓ ✓ API Information This connector uses the following vendor API: API Name: Google Ads API API Version: v9 API Endpoint: https://developers.google.com/google-ads/api/rest/overview Batch Limits This connector uses batched requests to support high-volume data transfers to the vendor. Requests are queued until one of the following 3 thresholds is met: Max number of requests: 2000 Max time since oldest request: 10 minutes Max size of requests: 2 MB Delayed Actions Actions are delayed for 30 minutes to accommodate uploading offline conversions, as per Google’s best practices. For more information about delayed actions using the Google Campaign Manager 360 Floodlight connector, see Google's Best practices for uploading offline conversions documentation. Actions are not delayed when using trace in EventStream or AudienceStream. 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 - Upload Call Conversion Parameters Parameter Description Customer ID Select customer account ID. Available options reflect accessible customer accounts for authenticated user. Conversion Action Select existing conversion action. For more information, see Google Ads Conversion Tracking. Caller ID Required The called ID from which this call was placed. Caller ID is expected in E.164 format and preceded by the plus ( + ) character. Example: +16502531234 Call Start Datetime Required The date time at which the call occurred. The timezone must be specified. The format is yyyy-mm-dd hh:mm:ss Example: 2020-01-01 12:32:45-8:00 . Conversion Datetime Required The date time at which the conversion occurred. Must be after the call time. The timezone must be specified. The format is yyyy-mm-dd hh:mm:ss Example: 2020-01-01 12:32:45-8:00 . Conversion Value The value of the conversion for the advertiser. Currency Code Currency associated with the conversion value. This is the ISO 4217 3-character currency code. Examples: USD , EUR Action - Upload Click Conversion Parameters Parameter Description Customer ID Select customer account ID. Available options reflect accessible customer accounts for authenticated user. Conversion Action Select existing conversion action. For more information, see: Google Ads Conversion Tracking. Google Click ID Required The Google Click ID ( gclid) associated with this conversion. Conversion Datetime Required The date time at which the conversion occurred. Must be after the click time. The timezone must be specified. The format is yyyy-mm-dd hh:mm:ss Example 2020-01-01 12:32:45-8:00 . Conversion Value The value of the conversion for the advertiser. Currency Code Currency associated with the conversion value. This is the ISO 4217 3-character currency code. Examples: USD , EUR Order ID Required The Order ID associated with the conversion. An Order ID can only be used for one conversion per conversion action. External Attribution Credit Represents the fraction of the conversion that is attributed to the Google Ads click. External Attribution Model Specified the attribution model name. For more information, see Google Ads API Click Conversion. Merchant ID The Merchant Center ID where the items are uploaded. Feed Country Code The country code associated with the feed where the items are uploaded. Feed Language Code The language code associated with the feed where the items are uploaded. Local Transaction Sum of all transaction level discounts, such as free shipping and coupon discounts for the whole cart. The currency code is the same as that in the ClickConversion message. Product ID The shopping ID of the item. Must be equal to the Merchant Center product identifier. Use an array to add multiple items. Array type attributes must be of equal length. Quantity Number of items sold. Use an array to add multiple items. Array type attributes must be of equal length. Unit Price Unit price excluding tax, shipping, and any transaction level discounts. The currency code is the same as that in the ClickConversion message. Use an array to add multiple items. Array type attributes must be of equal length. Action — Conversion Restatement Wait 24 hours after a conversion is reported before adjusting it to avoid a CONVERSION_NOT_FOUND or TOO_RECENT_CONVERSION error. Parameters Parameter Description Conversion Action Select existing conversion action. For more information, see: Google Ads Conversion Adjustments. Restatement Value (Required) The value of the conversion after restatement. Restatement Date Time (Required) The date time at which the adjustment occurred. The format is yyyy-mm-dd hh:mm:ss+|-hh:mm . Date attributes will be converted to the format Google expects. Order ID Either Order ID or Google Click ID with Conversion Date Time must be provided. If the conversion was reported with an order ID specified, that order ID must be used. Google Click ID Either Order ID or Google Click ID with Conversion Date Time must be provided. If the conversion was reported with an order ID specified, that order ID must be used. Conversion Date Time If used, should be in the format yyyy-mm-dd hh:mm:ss+|-hh:mm . Date attributes will be converted to the format Google expects. Currency Code The currency of the restated value. If not provided, then the default currency from the conversion action is used. Action — Conversion Retraction Wait 24 hours after a conversion is reported before adjusting it to avoid a CONVERSION_NOT_FOUND or TOO_RECENT_CONVERSION error. Parameters Parameter Description Conversion Action Select existing conversion action. For more information, see: Google Ads Conversion Adjustments. Retraction Date Time (Required) The date time at which the retraction occurred. The format is yyyy-mm-dd hh:mm:ss+|-hh:mm . Date attributes will be converted to the format Google expects. Order ID Either Order ID or Google Click ID with Conversion Date Time must be provided. If the conversion was reported with an order ID specified, that order ID must be used. Google Click ID Either Order ID or Google Click ID with Conversion Date Time must be provided. If the conversion was reported with an order ID specified, that order ID must be used. Conversion Date Time If used, should be in the format yyyy-mm-dd hh:mm:ss+|-hh:mm . Date attributes will be converted to the format Google expects. Considerations for Real-Time Web Traffic A click-through associated with a Google Click ID must have occurred at least 6 hours prior to activating the connector, otherwise Google will reject the request. Tealium recommends additional consideration when using this connector for the activation of real-time web traffic due to the fact that many of the Google Click IDs are associated with clicks that occurred less than 6 hours before the conversion event. Consider one of the following strategies to use the connector in this manner: Upload historical conversion data using a file import or the Collect API. Send the data to a Google Sheet and manually upload the data to Google Ads. ... View more