Tealium Learning Center

This article describes how to set up the Sizmek connector in your Universal Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add User To Sizmek Segment(s) ✓ ✓ Remove User From Sizmek Segment(s) ✓ ✓ Replace all Sizemek Segments for User ✓ ✓ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Add User To Sizmek Segment(s) Parameters Parameter Description   cookie_id Required. Obtain the value from the visitor's browser.   segments Required. Pipe-separated list of segment IDs. If you pass an array type, Tealium will correctly format the data to be passed.   advertiser_id Optional. Sizmek Advertiser ID.  Set advertiser_id to zero ( 0 ) for a third-party advertiser.   account_id Optional. Account ID   adid Optional. Android ID used for mobile users.   idfa Optional. Apple IDFA used for mobile users. Additional Information This action is an incremental update of the user's segments. To send any other query parameter key-value pairs, map a Custom value key to the value. Action - Remove User From Sizmek Segment(s) Parameters Parameter Description   cookie_id Required. Obtain the value from the visitor's browser.   segments Required. Pipe-separated list of segment IDs. If you pass an array type, Tealium will correctly format the data to be passed.   advertiser_id Optional. Sizmek Advertiser ID.  Set advertiser_id to zero ( 0 ) for a third-party advertiser.   account_id Optional. Account ID   adid Optional. Android ID used for mobile users.   idfa Optional. Apple IDFA used for mobile users. Additional Information This action is an incremental update of the user's segments. To send any other query parameter key-value pairs, map a Custom value key to the value. Action - Replace all Sizemek Segments for User Parameters Parameter Description   cookie_id Required. Obtain the value from the visitor's browser.   segments Required. Pipe-separated list of segment IDs. If you pass an array type, Tealium will correctly format the data to be passed.   advertiser_id Optional. Sizmek Advertiser ID.  Set advertiser_id to zero ( 0 ) for a third-party advertiser.   account_id Optional. Account ID   adid Optional. Android ID used for mobile users.   idfa Optional. Apple IDFA used for mobile users. Additional Information This action is an incremental update of the user's segments. To send any other query parameter key-value pairs, map a Custom value key to the value. ... View more

This article describes how to set up the Twitter Tailored Audiences Batch Connector to control who sees your Twitter Ads. This connector is currently available as an Experiment. (Learn more) 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 account's URL 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 User to Tailored Audience Parameter Description Tailored Audience Required. Select audience from list. For more information, see Tailored Audiences. User Identifier Required. Provide user identifier value. User Identifier Hashing All user identifiers except "Partner User ID" must be hashed using SHA256 and data normalization. If the User Identifier is already hashed checkbox is unchecked, UDH will normalize the hash and the mapped value. Effective At Membership option. The UTC time at which the tailored audience associations should take effect. Expressed in ISO 8601. Defaults to the current date and time. A millisecond (ms) since epoch timestamp may be provided, and will be formatted correctly. Expires At Membership option. The UTC time at which the tailored audience associations should expire. The specified time must be later than the value of "Effective At". Expressed in ISO 8601. Defaults to your configured default expiration period, which is typically 30 days or 720 hours from the value of "Effective At". String/Property Attributes ISO 8601 format. Example: YYYY-MM-DDThh:mm:ss . Date/Number Attributes ISO 8601 format. Example: YYYY-MM-DDThh:mm:ss . Action - Remove User From Tailored Audience Parameter Description Tailored Audience Required. Select audience from list. For more information, see Tailored Audiences. User Identifier Required. Provide user identifier value. User Identifier Hashing All user identifiers except "Partner User ID" must be hashed using SHA256 and data normalization. If the User Identifier is already hashed checkbox is unchecked, UDH will normalize the hash and the mapped value. Effective At Membership option. The UTC time at which the tailored audience associations should take effect. Expressed in ISO 8601. Defaults to the current date and time. A millisecond (ms) since epoch timestamp may be provided, and will be formatted correctly. Expires At Membership option. The UTC time at which the tailored audience associations should expire. The specified time must be later than the value of "Effective At". Expressed in ISO 8601. Defaults to your configured default expiration period, which is typically 30 days or 720 hours from the value of "Effective At". String/Property Attributes ISO 8601 format. Example: YYYY-MM-DDThh:mm:ss . Date/Number Attributes ISO 8601 format. Example: YYYY-MM-DDThh:mm:ss . ... View more

View the Release Notes summary to learn about updated product features, enhancements, and fixes. To view details about how to use a new feature, click the  Learn More  link next to the description. Tags New/Cool Stuff New marketplace tag: Confirmit New marketplace tag: ContactWare for CX New marketplace tag: Jornaya New marketplace tag: LiveIntent In-App Tracking Updated the Adobe AppMeasurement for JavaScript tag to Version 2.14. (Learn more) Updated the Adobe Experience Cloud ID service tag to Version 4.3. (Learn more) Updated Facebook Pixel to support passing an event. Updated the Tealium Collect tag to capture downstream tag data. Fixes Corrected the network ID parameter name for the Adition tag. Updated the tab description for User ID and AuthState for the Adobe Experience Cloud ID Service tag. Connectors New/Cool lStuff Updated API error messaging for the Google Adwords Customer Match connector to include more detailed information. Fixes Corrected an issue with connector HTTP request retries that caused an abnormal number of reported errors (excludes SOAP and older connectors). Updated the Facebook Ads connector to remove the MULTI_HASH filter from the audience lookup options. iQ Tag Management Fixes Corrected issue causing the Go Live Notification email to be sent more than once for some accounts Updated the Tealium welcome email template to include updated links to Documentation, Forums, and Tealium Education Online. Universal Data Hub New/Cool Stuff Added rule and audience support for "matches regular expression (Regex)" for string operands. The Visitor Profile Sampler now displays a stitching distribution graph and five dashlets displaying a report of the most frequently asked questions. (Learn more) Fixes Corrected issue causing an error when selecting the Visitor ID attribute as a perspective in Audience Discovery. Corrected issue in AudienceDB to display all attributes instead of only displaying the enabled attributes. Installations Fixes Corrected issue causing Android application crashes when running multiple webviews. ... View more

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

View the Release Notes summary to learn about updated product features, enhancements, and fixes. To view details about how to use a new feature, click the  Learn More  link next to the description. Tags New/Cool Stuff New marketplace tag: Azure Application Insights Added cross-domain tracking and support for the Google Ads Conversion Tracking and Remarketing tag for renaming the (gtag.js) data layer. (Learn more) Updated the Insider InOne tag base URL for  and added support for the partner_id parameter. Updated the FullStory tag to support an event source parameter. Created new version of the Monetate tag. (Learn more) Fixes Corrected issue with event mapping in user interface when using the Facebook Pixel. Corrected rendering issue with drop-down field for the Webtrekk connector that occurred when the Publish to Prod setting was set to Off. Updated the Facebook Pixel tag to allow multiple custom tracking events on same trigger. (Learn more) Updated the Kenshoo Infinity tag base_url  and conversion code. Connectors New/Cool Stuff New marketplace connector: APSIS (Learn more) New marketplace connector: Criteo (hidden) (Learn more) New marketplace connector: Mixmax (Learn more) New marketplace connector: MoEngage (Learn more) New marketplace connector: ONTRAPORT (Learn more) New marketplace connector: Sarbacane (Learn more) New marketplace connector: SendPulse (Learn more) Updated Google DCM Floodlight Batch Connector to increase batch buffer settings to delay API calls. iQ Tag Management Fixes Corrected issue causing parameter fields in Consent Manager to not expand properly when additional fields are viewed or opened. Corrected issue causing yellow notification banner to erroneously display for a different user after switching accounts or profiles. Corrected issue where the data mapping toolbox would not load if a data layer variable was missing the Name property. Corrected issue with merge function that caused unchanged reports, tags, and extensions to display as changed. Universal Data Hub Fixes Applied further updates and enhancements to the new user interface. (Learn more) Corrected issue causing potentially inaccurate EventStream event counts to display in the interface. Corrected permission synchronization issue between TiQ and UDH user permissions. Corrected user interface issue where users could no longer view AudienceStream attributes after deleting a visitor tally (other attributes no affected). Installations Fixes Corrected Lifecycle isFirstLaunch issue in Objective-C. New/Cool Stuff Added sample application to display the use of the current Firebase Remote command for Swift. (Learn more) ... View more

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

This article describes how to set up the APSIS connector in your Universal Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Create Subscriber ✓ ✗ Update Subscriber ✓ ✗ Send Transactional Email ✓ ✗ Create Subscriber with Double Opt-in ✓ ✗ Delete Single Subscription ✓ ✗ Create Single Subscription ✓ ✗ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: API Key To get an API key, log in to your APSIS Pro account and select the Account section. Find the API Keys link and click to generate a new API key. One account can have multiple API keys. You can manage your keys using the Account Settings section in APSIS Pro. For more information, see: APSIS: Getting Started Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Create Subscriber Parameters Parameter Description Mailing List ID The ID of the list the subscriber should be added to. For more information, see: http://se.apidoc.anpdm.com/Browse/Method/SubscriberService/CreateSubscriber Update If Exists If the email address already exists on the account and this parameter is true, then the subscriber data will be updated. Otherwise, an error is returned. Email The subscriber's email address. Password The subscriber's password. Name The name of the subscriber. Format The subscriber's desired format. Country Code The subscriber's country code. Phone Number The subscriber's phone number. External ID The subscriber's external ID. Demographic Data Fields The subscriber's list of demographic data fields. Action - Update Subscriber Parameters Parameter Description Subscriber ID The subscriber's ID. For more information, see: http://se.apidoc.anpdm.com/Browse/Method/SubscriberService/UpdateSubscribers Email The subscriber's email address. Password The subscriber's password. Name The name of the subscriber. Format The subscriber's desired format. Country Code The subscriber's country code. Phone Number The subscriber's phone number. Demographic Data Fields The subscriber's list of demographic data fields. Action - Send Transactional Email Parameters Parameter Description Project ID ID of the project. For more information, see: http://se.apidoc.anpdm.com/Browse/Method/TransactionalService/SendTransactionalEmail Send Date Send date. Allow Inactive Projects True or false indicating if sending should be allowed when project is inactive Default value is true. Email The subscriber's email address. Name The name of the subscriber. Format The subscriber's desired format. External ID The subscriber's external ID. Country Code The subscriber's country code. Demographic Data Fields The subscriber's list of demographic data fields. Sending Type Possible values: m - marketing t - transactional (default) Action - Create Subscriber with Double Opt-in Parameters Parameter Description Mailing List ID ID of the mailing list to which the subscriber will be added. For more information, see: http://se.apidoc.anpdm.com/Browse/Method/SubscriberService/CreateSubscriberWithDoubleOptIn Email The subscriber's email address. Password The subscriber's password. Name The name of the subscriber. Format The subscriber's desired format. Country Code The subscriber's country code. Phone Number The subscriber's phone number. External ID The subscriber's external ID. Demographic Data Fields The subscriber's list of demographic data fields. Action - Delete Single Subscription Parameters Parameter Description Mailing List ID The mailing list from which to delete the subscriber. For more information, see: http://se.apidoc.anpdm.com/Browse/Method/MailingListService/DeleteSingleSubscription Subscriber ID The ID of the subscriber to be removed from the list. Action - Create Single Subscription Parameters Parameter Description Mailing List ID The Mailing List ID to which the subscription should be created. For more information, see: http://se.apidoc.anpdm.com/Browse/Method/MailingListService/CreateSingleSubscription Subscriber ID The ID of the subscriber to be added to the list. ... View more

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

This article describes how to set up the Sarbacane connector in your Universal Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add or Edit a Contact ✓ ✗ Add Recipients to a Campaign ✓ ✗ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: Account ID For more information about your Account ID, see: https://developers.sarbacane.com/#authentification API key For more information about your API key, see: https://developers.sarbacane.com/#authentification Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Add or Edit a Contact Parameters Parameter Description List ID ID of the list concerned. For more information, see: https://developers.sarbacane.com/#ajouter-modifier-un-contact Email The email of the contact. Must use either email and/or phone. Phone Phone number of the contact. Must use either email and/or phone. Field ID's Key:value pairs of ID's of columns and values to be added to those columns. For more information on how to retrieve or add column ID's, see: https://developers.sarbacane.com/#lister-les-champs-personnalises Action - Add Recipients to a Campaign Parameters Parameter Description Campaign ID ID of the campaign For more information, see: https://developers.sarbacane.com/#ajouter-des-destinataires Email The email of the contact. Must use either email and/or phone. Phone Phone number of the contact. Must use either email and/or phone. ... View more

This article describes how to set up the MoEngage connector in your Universal Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add/Modify User Information ✓ ✓ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: Username Data API ID. See https://docs.moengage.com/docs/data-import-apis#section-authentication Password Data API Key Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Add/Modify User Information Parameters Parameter Description Customer ID The unique identifier which is set and passed on from MoEngage SDK. For more information, see: https://docs.moengage.com/docs/data-import-apis#section-addmodify-user-information Name The name of the user you are updating. First Name First name of the user. Last Name Last name of the user. Email Email of the user. Age Age of the user. Gender Male or female. Case-sensitive. Mobile Phone number of the user. Geography Location of the user, latitude and longitude (- lat,lng). Must be an array of numbers attribute type. Source Acquisition source of the user. Created Time User created time. Last Seen User last seen time. Transactions Number of transactions by the user. Revenue Lifetime value of the user. Platform The current platform on which the user is interacting with the system, such as Android, Windows, iOS, etc. ... View more

This article describes how to set up the SendPulse connector in your Universal Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add Email to Mailing List (single opt-in) ✓ ✗ Add Email to Mailing List (double opt-in) ✓ ✗ Delete Email from Mailing List ✓ ✗ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: Client ID See https://sendpulse.com/integrations/ap authorization for information about your OAuth2 credentials. Client Secret Required. Provide your web application client secret. Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Add Email to Mailing List (single opt-in) Parameters Parameter Description List ID ID of the mailing to list to which you are adding the user. For more information, see: https://sendpulse.com/integrations/api/bulk-email Email Email address of the user to be added to the list. Action - Add Email to Mailing List (double opt-in) Parameters Parameter Description List ID ID of the mailing to list to which you are adding the user. For more information, see: https://sendpulse.com/integrations/api/bulk-email Sender Email Your sender email. Sender email address must be activated in your SendPulse account in Email-Service settings-From address menu. Email Email address of the user to be added to the list. Action - Delete Email from Mailing List Parameters Parameter Description List ID ID of the list from which you are deleting the contact. For more information, see: https://sendpulse.com/integrations/api/bulk-email Email Email address to be deleted from list. ... View more

View the Release Notes summary to learn about updated product features, enhancements, and fixes. To view details about how to use a new feature, click the Learn More link next to the description. Tags New/Cool Stuff New marketplace tag: Knotch Updated the Floodlight (gtag.js) tag to add support for "purchase-details". (Learn more) Updated the Google Analytics (gtag.js) tag to allow configuration set method in a link event. Updated to the Tealium Collect tag to abide by Interactive Advertising Bureau (IAB) consent settings when present. Fixes Updated the Adobe Analytics AppMeasurement tag for JS to support mapping to linkName and linkType for AppMeasurement, Versions 2.12.0 and later. Updated the Facebook Pixel tag to normalize case in advanced matching unless the item being matched is recognized. (Learn more) Connectors New/Cool Stuff New marketplace connector: Adestra (Learn more) New marketplace connector: Eloqua Custom Objects (Learn more) New marketplace connector: Enchant (Learn more) New marketplace connector: Infobip (Learn more) New marketplace connector: LeadSquared (Learn more) New marketplace connector: LeanPlum (Learn more) New marketplace connector: Mocean (Learn more) New marketplace connector: DCM Floodlight (Learn more) New marketplace connector: Google Adwords Customer Match. (Learn more) Updated and replaced the existing Cordial connector. (Learn more) Updated the DialogOne connector to latest version. (Learn more) Updated the Optimizely Events connector to latest version. (Learn more) Updated the Selligent connector to add custom attributes for the Add to Action List and Trigger Campaign actions. Updated the Selligent connector to use REST calls and Auth mechanism in Data-Distributor in order to support returning 500 items per HTTP call (increased from 200 to 500). Fixes Updated the Optimizely Events connector to correct API link listed in Tool Tips to generate a token and updated the logo for all Optimizely connectors. (Learn more) Corrected issue with the Google AdWords Customer Match connector causing a VendorApiException error. Deprecated the Twitter Tailored Audiences connector. Corrected the Facebook Offline Conversations connector to enable AudienceStream support.  (Learn more) Updated the Webtrekk connector to exclude empty values from the API call. (Learn more) iQ Tag Management New/Cool Stuff Introduced the new unified interface. (Learn more) Fixes Updated message text returned when an incorrect email address entered at login to ensure that the email address is properly masked. Users entering five (5) unsuccessful two-factor authentication (2FA) codes with a valid username and password are now locked out for 10 minutes before they can retry. Universal Data Hub New/Cool Stuff Introduced the new unified user interface. (Learn more) Updated AudienceStream options to expose relevant profile settings to the Admin user. Fixes Corrected issue in new rule editor that did not allow the number zero (0) as a string literal entry. Corrected issue in the display of the rule modal where drop-down values appeared incorrectly when adding a new attribute (display issue only). Corrected issue that caused rules assigned within enrichments to be assigned to all enrichments in an attribute instead of the expected behavior of only assigning to the enrichment that is being worked on. Corrected an issue on the rules screen causing the loading status to stick at 65%. Updated file import data source to accept Microsoft MIME file types for .csv file imports. Installations Fixes Corrected issue with React Native on mobile by updating to the Version 1.0.4 fixes for possible null activity and other null checks in Consent Manager methods. ... View more

This article describes how to set up the Google AdWords Customer Match (Customer-Provided Credentials) connector in your Universal Data Hub account. In this article: Table of Contents Placeholder Requirements There are two types of Google Adwords Customer Match Connectors. Ensure that you select the appropriate one when adding the connector. Google Adword Customer Match (Customer-Provided Credentials) Requires Google approval. Google Adword Customer Match (Tealium-Provided Credentials) Tealium has been pre-approved to handle volume, bypassing your need to go through the application process. Connector Actions Action Name AudienceStream EventStream Add User to Remarketing List ✓ ✓ Remove User from Remarketing List ✓ ✓ Add User to Remarketing List ✓ ✓ Remove User from Remarketing List ✓ ✓ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: AdWords Customer Id: Customer Id of AdWords account to manage Developer Token Requires submission for approval to Google to make Production Volume API Requests. This is a multi-step process that you will need to own and manage. Start here. Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Add User to Remarketing List Parameters Parameter Description Remarketing List Remarketing List to add user to User Email Required. Email address of user to add. If plain text (unhashed email) is passed, Tealium trims whitespaces and lowercases the email per API requirements. See Remarketing Caveats. See also Email Address Caveats. Check this box if the provided email address is in plain text, i.e. not SHA_256 encoded. Check if the provided email address is in plain text (not SHA_256 encoded). Action - Remove User from Remarketing List Parameters Parameter Description Remarketing List Remarketing List to remove user from. User Email Required. Email address of user to remove. If plain text (unhashed email) is passed, Tealium trims whitespaces and lowercases the email per API requirements. See Remarketing Caveats. See also Email Address Caveats. Check this box if the provided email address is in plain text, i.e. not SHA_256 encoded. Check if the provided email address is in plain text (not SHA_256 encoded). Action - Add User to Remarketing List Parameters Parameter Description Remarketing List Remarketing List to add user to. User Email Required. Email address of user to add. If plain text (unhashed email) is passed, Tealium trims whitespaces and lowercases the email per API requirements. See Remarketing Caveats. See also Email Address Caveats. Check this box if the provided email address is in plain text, i.e. not SHA_256 encoded. Check if the provided email address is in plain text (not SHA_256 encoded). Action - Remove User from Remarketing List Parameters Parameter Description Remarketing List Remarketing List to remove user from. User Email Required. Email address of user to remove. If plain text (unhashed email) is passed, Tealium trims whitespaces and lowercases the email per API requirements. See Remarketing Caveats. See also Email Address Caveats. Check this box if the provided email address is in plain text, i.e. not SHA_256 encoded. Check if the provided email address is in plain text (not SHA_256 encoded). ... View more

This article describes how to set up the ActiveCampaign connector in your Universal Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add New Contact ✓ ✗ Add Tags to Contact ✓ ✗ Add Contact to Automation ✓ ✗ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: API URL Go to ActiveCampaign and click Settings > Developer. For more information, see: https://account.api-us1.com">https://account.api-us1.com. API Key Go to ActiveCampaign and click Settings > Developer. Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Add New Contact Parameters Parameter Description Email Email of the new contact. for example, 'test@example.com'. List ID Assign a contact to a list. Specify the integer value of the list, for example, 12345. Additional Fields Optional. Include additional data about the contact. For a list of available fields, see: https://www.activecampaign.com/api/example.php?call=contact_add. Action - Add Tags to Contact Parameters Parameter Description Email Email of the new contact, for example 'test@example.com'. Tags Tags to add to the contact. Pass a string for one tag, an array (set of strings) for multiple tags, or a comma-separated list of custom values. Action - Add Contact to Automation Parameters Parameter Description Contact Email Email of the new contact, for example, 'test@example.com'. Automation IDs The automation IDs to add the contact to. You may use multiple, comma-separated values. ... View more

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

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

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

This article describes how to set up the Enchant connector in your Universal Data Hub account. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Create a New Customer ✓ ✗ Update a Customer ✓ ✗ Create a Contact ✓ ✗ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: Access token To get an access token, install the API app from the apps tab of your help desk settings. Each instance of the API application has it's own access token. For more information, see: Enchant Rest API Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Create a New Customer Parameters Parameter Description First name First name of the customer. For more information on this endpoint, see: https://dev.enchant.com/api/v1#customers Last name Last name of the customer. Summary Custom summary information. Action - Update a Customer Parameters Parameter Description Customer ID ID of the customer. For more information on this endpoint, see: https://dev.enchant.com/api/v1#customers First name First name of the customer. Last name Last name of the customer. Summary Custom summary information. Action - Create a Contact Parameters Parameter Description Customer ID ID of the customer. For more information on this endpoint, see: https://dev.enchant.com/api/v1#contacts Type Either "email" or "twitter." Value Email or Twitter value. ... View more

This article describes how to set up the Cordial connector in your Universal Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Update List Value of a User ✓ ✓ Send an Automation Template ✓ ✓ Upsert Contact ✓ ✗ Contact Activities ✓ ✗ 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 settings: Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. The following sections describe how to set up parameters and options for each action. Action - Update List Value of a User Parameters Parameter Description API Key Cordial uses HTTP Basic Authentication (BA). From within the Cordial platform, you can generate an encoded API key for your account. The encoded API key is then used as the "username" for your BA credentials. Primary Key The "primary_key" is defined by the contact's unique "email address" value. List Name The name of the list the contact will be added to within the Cordial database. Note that the lists were created prior to updating the contact. For more information, see: https://cordial.zendesk.com/hc/en-us/articles/203885958-Contacts. Action - Send an Automation Template Parameters Parameter Description API Key Cordial uses HTTP Basic Authentication (BA). From within the Cordial platform, you can generate an encoded API key for your account. The API key is then used as the "username" for your BA credentials. Message Key The automation template to be sent is defined by the template's unique "key" value. For more information, see: https://cordial.zendesk.com/hc/en-us/articles/203886108-Automationtemplates. Email The email address to send to. Action - Upsert Contact Parameters Parameter Description Email The email address of the contact to insert or update. Subscribed Status (Optional) Set the subscription status to one of the following: subscribed, unsubscribed, none Contact Attributes Contact attributes to set or update for the user (string or number values). For list updates, use booleans. For example: {list_name} : true Action - Contact Activities Parameters Parameter Description Action Name The name of the action or activity to record for the user. Can be click, open, send, or any other user-defined actions. Contact Primary Key The name of the primary key used to identify the user, for example: email Contact Primary Key Value The value of the primary key used to identify the user, for example: user@test.com Action Properties Additional data about the action or activity to record for the user. Action Timestamp The timestamp of the action or activity. Cordial will automatically populate the timestamp if not provided in the request. ... View more

View the Release Notes summary to learn about updated product features, enhancements, and fixes. To view details about how to use a new feature, click the Learn More link next to the description. Tags New/Cool Stuff New marketplace tag: Adition Cookie Matching Service Updated Adobe AppMeasurement for JavaScript tag to Version 2.12. (Learn more) Updated Adobe Audience Manager tag library to Version 9.1.  (Learn more) Updated Adobe Experience Cloud ID Service tag to Version 4.1. (Learn more) Updated AT Internet Smarttag to prevent an erroneous page tracking event with a click event. Updated the Bing UET tag to support events and new parameters. Updated the Conversant Media - Direct to Brands tag to support mapping to dtm_fid  parameter. Updated the Facebook Pixel tag to add support for new standard events. (Learn more) Updated Google Ads Conversion Tracking and Remarketing (gtag.js) tags to add phone conversion mappings. (Learn more) Updated Rakuten Marketing tag to make additional mappings available as basic configuration options to support SPAs and optional data. Fixes Corrected issue with Google Ads Conversion Tracking and Remarketing tag to only add conversion event if no event is currently set. Corrected issue with The Tradedesk tag causing properties from previous events to persist. Corrected the page_view scope for the Google Analytics (gtag.js) tag and added support for product-scoped dimensions and metrics. Connectors New/Cool Stuff Updated Google DMP AdWords connectors to the latest API versions, including DoubleClick Bid Manager, DoubleClick for Publishers (DFP), Google AdWords, DoubleClick Ad Exchange, and AdWords Customer Match. iQ Tag Management New/Cool Stuff Updated Amazon Web Services ( AWS) region support for the Tealium Collect tag (JavaScript tealium.js) and added support for a more compact page code snippet. Fixes Corrected issue causing insufficient session expiration resulting in logout or removal of user. Updated deprecated Google Chart API to correctly generate QR code for multi-factor authentication (MFA). Universal Data Hub New/Cool Stuff Introduced new Concurrent User Management options and support feature. (Learn more) Introduced new Data Supply Chain View feature. (Learn more) Introduced new File Import Data Source (Omnichannel) feature. (Learn more) Introduced new GitHub Integration feature. (Learn more) Introduced new Minified Trace feature. (Learn more) Fixes Applied updates to allow UDO string variables declared in the UDH to be used with the "Set Date" enrichment. Corrected issue created when two (2) conditions for a rule are saved and published and the second is subsequently removed. Corrected issue introduced by the lastest version of Google Chrome (73.0.3683.86) where user is not able to select an account in the UDH UI when using this version of the Chrome browser. Corrected issue preventing pop-up dependencies warning from displaying when deleting a rule that contains linked enrichments. Corrected issue with latest deployment causing mismatched event feeds. ... View more

This article describes how to set up the LeanPlum connector in your Universal Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Set User Attributes ✓ ✓ Send Message ✓ ✓ Track Event ✗ ✓ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: 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 - Set User Attributes Parameters Parameter Description App ID The application ID. To find your application ID: Select your application in the navigation column, and click Edit Apps. Under Keys, click Show. For more information on this endpoint, see: https://www.leanplum.com/docs/api/production#setuserattributes. Client Key The Production key for your LeanPlum application. API Version The version of the LeanPlum API to use. At time of publishing this version, the most recent version is 1.0.6. User ID The current user ID. Set to an email address or what you use at your company for user IDs. Leave blank to use the device ID. For more information, see: https://www.leanplum.com/docs/api/#users-and-devices. Create Disposition The policy that determines whether users are created by the API. The default value for this method is CreateIfNeeded. Possible values are: CreateIfNeeded creates a user with the given IDs if one does not already exist. CreateNever requires that the user already exists, otherwise the API call is skipped and a warning will be returned. Dev Mode Whether the user is in Development mode (the caller is a developer and not a user). Important for reporting purposes. Value options are  true or false . Default Value: false . User Attributes A map of user attributes as key-value pairs. Each key must be a string. Attributes are saved across sessions. Only supplied attributes are updated. If you omit an existing attribute, it will be preserved. Example: {"gender":"F","age":21} . User Attribute Values To Add A map of values to add to existing user attribute sets. For example, supply {"Interests":"Sports"} to add Sports to the existing set of interests. Action - Send Message Parameters Parameter Description App ID The application ID. To find your application ID: Select your application in the navigation column, and click Edit Apps. Under Keys, click Show. For more information on this endpoint, visit: https://www.leanplum.com/docs/api/production#setuserattributes. Client Key The Production key for your LeanPlum App. API Version The version of the LeanPlum API to use. At time of publishing this version, the most recent version is 1.0.6. User ID The current user ID. Set to an email address, or what you use at your company for user IDs. Leave blank to use the device ID. For more information, see: https://www.leanplum.com/docs/api/#users-and-devices. Message ID The ID of the message, found in the URL when viewing a message. For example:  www.leanplum.com/dashboard#/{APP_ID}/messaging/{MESSAGE_ID} . For more information on this endpoint, see: https://www.leanplum.com/docs/api/production#sendmessage. Dev Mode Whether the user is in Development mode (the caller is a developer and not a user). Important for reporting purposes. Value options are  true or false . Default Value: false . Device ID A unique ID for the device targeted by the call. A deviceID and/or a userID  is required. For more information, see: https://www.leanplum.com/docs/api/#users-and-devices. Create Disposition The policy that determines whether users are created by the API. The default value for this method is CreateIfNeeded. Possible values are: CreateIfNeeded creates a user with the given IDs if one does not already exist. CreateNever requires that the user already exists, otherwise the API call is skipped and a warning will be returned. Force Whether to send the message regardless of whether the user meets the targeting criteria. Value options are  true or false . Default Value: false . Values A JSON object of key-value pairs to override Jinja values in the message. Action - Track Event Parameters Parameter Description App ID To find your application ID: Select your application in the navigation column, and click Edit Apps. Under Keys, click Show. For more information, see: https://www.leanplum.com/docs/api/production#setuserattributes. Client Key The Production key for your LeanPlum application. API Version The version of the LeanPlum API to use. At time of publishing this version, the most recent version is 1.0.6. User ID The current user ID. Set to an email address, or what you use at your company for user IDs. Leave blank to use the device ID. For more information, see: https://www.leanplum.com/docs/api/#users-and-devices. Event The name of the event. Use "Purchase" to identify a monetization event, with the event value being the revenue. You can change the default monetization event name in Analytics by going to the metric chooser and clicking the Monetization metric category. For more information, see: https://docs.leanplum.com/reference#post_api-action-track Device ID A unique ID for the device targeted by the call. A Device ID and/or a User ID is required. For more information, see: https://www.leanplum.com/docs/api/#users-and-devices. Dev Mode Whether the user is in Development mode (the caller is a developer and not a user). Important for reporting purposes. Value options are  true or false . Default Value: false . Create Disposition The policy that determines whether users are created by the API. The default value for this method is CreateIfNeeded. Possible values are: CreateIfNeeded creates a user with the given IDs if one does not already exist. CreateNever requires that the user already exists, otherwise the API call is skipped and a warning will be returned. Value The event value. Example: For a purchase event, this would be the purchase price. Currency Code The ISO 4217 currency code associated with value. LeanPlum automatically converts the value into your preferred currency, while retaining the original price and currency code as event parameters localCurrency and localPrice . Currency conversion rates are updated every hour. Info Any information attached to the event. Time Option to provide the Unix timestamp for when the event occurred, which may be different from the current time. Parameters Parameters as key-value pairs. Each key must be a string, and up to 50 parameters may be set. Message ID The message ID this event is associated with. Set this to track a user's interaction with a message. To track a message Send or a View, set the event argument to an empty string. For other interactions, set the event argument to the type of action. Example values: Open , Cancel , Accept . The LeanPlum SDK does this automatically, so this should be used for advanced use cases only. Disposition Determines how tracked events affect sessions and user activity. If present, the disposition must have one of the following values:   active This is the default value. Used for events reflect user activity. Active events should mark the user as active and should be tracked within a session. Replaces the deprecated option allowOffline: false .   passive Used for events that do not correspond to user activity. These events do not need to occur within a session and do not mark a user as active. Example: Sending a user a message would be tracked passively, since it affects a user, but does not represent user activity. Replaces the deprecated option allowOffline: true .   requireActive Used for events that must only be tracked within a session. These events are rejected and return a warning response with ignored: true  if the user does not have an active session. Clients should detect the warning by the ignored field, as warning messages may change. ... View more