Tealium Learning Center

Tealium's integration with Marketo allows marketing operations and email marketing professionals to enrich their marketing automation programs for customer behavior attributes to build more targeted and relevant programs. This article describes how to set up the Marketo connector in your Customer Data Hub account. Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Add Lead to a List ✓ ✗ Remove Lead from a List ✓ ✗ Send Transactional Email ✓ ✗ Create or Update a Lead ✓ ✗ Merge 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: REST API Client ID: Required: provide client ID found in Marketo > Admin > LaunchPoint. API User must have permissions for 'Read-Write Lead', 'Read/Execute Campaigns' and 'Read Lists'. (Learn more about How to Create a Custom Service.) REST API Client Secret: Required: provide client secret found inMarketo > Admin > LaunchPoint. REST API Endpoint URL: Required: REST API Endpoint can be found from Marketo > Admin > Web Service, example: https://123-ABC-123.mktorest.com/rest REST API Identity URL: Required: REST API Identity can be found from Marketo > Admin > Web Service, example: https://123-ABC-123.mktorest.com/identity 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 Lead to a List Parameters Parameter Description Target Static List Required: select list Target Lead ID If the Lead ID for the user is known leave the Lead ID Lookup field blank and use this field. id   cookies   email   twitterId   facebookId   linkedInId   sfdcAccountId   sfdcContactId   sfdcLeadId   sfdcLeadOwnerId   sfdcOpptyId   Action - Remove Lead from a List Parameters Parameter Description Target Static List Required: select list Target Lead ID If the Lead ID for the user is known leave the Lead ID Lookup field blank and use this field. id   cookies   email   twitterId   facebookId   linkedInId   sfdcAccountId   sfdcContactId   sfdcLeadId   sfdcLeadOwnerId   sfdcOpptyId   Action - Send Transactional Email Parameters Parameter Description Target Email Campaign Please select the Target Smart Campaign that was created according to: Sending a transactional email from Marketo using the API Target Lead ID Required: provide target lead ID Token Data to Set Optional: Map token value to token name. Use the full token format as in the Marketo UI. For example, { { my.message } } Action - Create or Update a Lead Parameters Parameter Description Update Strategy Required: select update strategy Lead Lookup Filter Optional: select filter field by which to lookup existing Lead Selected lookup filter field must have value set in Lead Data section Action - Merge a Lead Parameters Parameter Description Winning Lead ID (Required) Losing Lead ID (Required) Merge in CRM     Use Case Example In this example, you will using the Marketo connector to create and push a new lead into our lead database. More specifically, you will making those who join our "Shoe Fans" audience into leads. Step 1: Define Attributes and Audience conditions. Create a new Visitor Id attribute to store the users email address. It will be the unique value associated with the lead. NOTE: Although it is possible to create a lead solely from an email address, it would best to capture more information to associate with the lead. In step 6, we will be passing this "Visitor Email" visitor id attribute along with three trait attributes for First name, Last name and Company. Then create a new audience titled “Shoe Fans” and set up logic so that all visitors with the "Shoe Fan Badge", and a true "Known User" Flag attribute will be added to the audience NOTE: "Known user" flag was created to determine whether or not we know who the user is. If there is an email address associated with user, it is set to true. If no email address, it is set to false. It is a necessary condition because we cannot convert a site user into a lead if we do not know who they are. Step 2: Create a Custom Service in Marketo Log into your Marketo account: https://login.marketo.com/ A custom service allows users to describe and define what data their client application can access. Before the application can be used, a Marketo Admin must associate it with a single API-only user with the ability to read, write, and merge leads, as well as being able to read, and execute campaigns. You will need to obtain the: REST API, Client ID REST API, Client Secret REST API, Complete REST endpoint URL REST API, Complete Identity endpoint URL Follow steps 1-7 in the link below to learn how to create a Custom Service in Marketo. Custom Service Step 3: Add the Marketo Connector Navigate to the "Act" tab, then click onto "Connectors". Next, click the "+ Add Connector" button to select from a list of available connectors. Click onto "Marketo", then click the "+ Add Connector" button once more. Configure REST API Fields You should now have obtained all the information needed to properly set up your connector. Navigate the the "Configure" tab of your connector window to copy and paste the values obtained from step 3, along with your title and any relevant notes. Click "Next". Configure Actions It is in this window where we will actually give the connector instructions on what to do. In the "Actions" dropdown, select the "Create or Update a lead" option. Then select the "Shoes Fans" audience, "Create only" for our "Update Strategy" and "Email" for our "Lead Lookup Filter". Since a lead is only as good as the information associated with it, we will need to map the appropriate data and values. Under "Lead Data to Set" we will select the attribute created in step 1 along with any others, and map them to their corresponding values. Step 4: Test / Trace Configuration We have just finished setting up our configuration. Now, we need to check to make sure we did it properly. The best way to go about testing is to run a trace to make sure your events are handled properly and to check your Marketo dashboard to make sure your lead was created with the proper information. The image above shows 3 main things: My audience was joined ("Shoe Fans") My action was triggered ("Marketo- Create leads") My action was processed successfully. ( "1 action processed/ 0 actions failed") Step 5: Verify in Marketo Summary: The Marketo connector would make an excellent addition in nearly any AudienceStream configuration. With its powerful features, and easy user interface, the possibilities to reach your prospects are endless.     ... View more

This article describes how to set up the Mandrill by MailChimp connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Send Transactional Email using a Template ✓ ✗ 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: Mandrill API Key: This parameter is Required Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Send Transactional Email using a Template Parameters Parameter Description Target Template Required Target Template. Subaccount Optional Subaccount for this message Must already exist or will fail with an error Tag List Optional String(s) to tag the message with. Stats are accumulated using tags, though Mandrill only stores the first 100 we see, so this should not be unique or change frequently. Tags should be 50 characters or less. Any tags starting with an underscore are reserved for internal use and will cause errors. message.subject Message subject line message.from_email Email address of sender  message.from_name Name of sender message.to.email Required Email address of recipient message.to.name Name of recipient message.important Values are true or false message.track_opens Track file opens   Values are yes or no message.track_clicks Track clicks Values are yes or no message.auto_text Optional message.auto_html Optional message.inline_css Optional message.url_strip_qs Optional message.preserve_recipients Optional message.view_content_link Optional message.bcc_address Optional message.tracking_domain Optional message.signing_domain Optional message.return_path_domain Optional message.merge Optional message.merge_language Optional async Optional ip_pool Optional send_at Optional Google Analytics Domains to Set Optional An array of strings indicating for which any matching URLs will automatically automatically append Google Analytics parameters to their query string. Google Analytics Campaign to Set Optional Optional string indicating the value to set for the utm_campaign tracking parameter. If not provide, the from address for the email is used instead. Recipient Header Type Optional The header type to use for the recipient, defaults to "to" if not provided one of the following: to , cc , bcc to.type: Header Data (Map Value to Key) Optional extra headers to add to the message (most headers are allowed) Template Content To Set (Map Content to Name) An array of template content to send. Each item in the array should be a struct with two keys: name the name of the content block to set the content content The actual content to put into the block Global Merge Vars To Set (Map Content to Name) Optional Global merge variables to use for recipient. name (string) The global merge variable"s name. Merge variable names are case-insensitive and may not start with an underscore ( _ ) character content (mixed) The content of the global merge variable Metadata To Set (Map Value to Key) Optional Metadata an associative array of user metadata. Mandrill will store this metadata and make it available for retrieval. In addition, you can select up to 10 metadata fields to index and make searchable using the Mandrill search api. ... View more

This article describes how to set up the Responsys connector in your Customer Data Hub account. In this article: Table of Contents Placeholder Connector Actions Action Name AudienceStream EventStream Merge Visitor into Profile Extension Table ✓ ✗ Merge Visitor into Supplemental Table ✓ ✗ Merge Visitor into List ✓ ✗ Send Transactional Campaign Email ✓ ✗ Trigger Custom Event ✓ ✗ Configure Settings Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector. After adding the connector, configure the following settings: API Username API Password Server Host Contact your Responsys representative to get the appropriate server host. When entering the server host, do not include the protocol and/or a path (e.g. https://) 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 Visitor into Profile Extension Table Parameter Description Table Folder Name Required Table Object 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. i.e. to enforce an INSERT only, use this option REPLACE_ALL When selected, if an existing record is matched, all the properties configured will be updated. RIID   CUSTOMER_ID   EMAIL_ADDRESS   Pass Empty Values for Data Columns(s) to Set Optional Data Column(s) to Set Required, please specify the record data to merge. Action - Merge Visitor into Supplemental Table Parameter Description Table Folder Name Required Table Object 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. i.e. to enforce an INSERT only, use this option and check the Insert on No Match checkbox REPLACE_ALL When selected, if an existing record is matched, all the properties configured will be updated. Insert on No Match Optional Pass Empty Values for Data Columns(s) to Set Optional Data Column(s) to Set Required Ensure you have included primary key columns. To pass a List, use a List Attribute and ensure all the lists have the same index length. Action - Merge Visitor into List Parameters Parameter Description List Folder Name   List Object 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. i.e. to enforce an INSERT only, use this option and check the Insert on No Match checkbox REPLACE_ALL When selected, if an existing record is matched, all the properties configured will be updated. Insert on No Match   RIID   CUSTOMER_ID   EMAIL_ADDRESS   Pass Empty Values for Data Columns(s) to Set   Data Column(s) to Set Required Please specify the record data to merge. optinValue   optoutValue   Action - Send Transactional Campaign Email Parameters Parameter Description Campaign Folder Name   Campaign Object Name   RIID   CUSTOMER_ID   EMAIL_ADDRESS   Action - Trigger Custom Event Parameters Parameter Description Recipient List Folder Name   Recipient List Object Name   RIID   CUSTOMER_ID   EMAIL_ADDRESS   Custom Event ID   Custom Event Name   Optional Data Map Optional Custom Event data that the user can set to any value Vendor Documentation Oracle Marketing Cloud - Responsys API ... View more

Overview In this post we will be going over how to pass dynamic content with the Mandrill connector. One way to add dynamic content to your Mandrill templates is by using part of the MailChimp template language in your templates to create regions that can be completely replaced with customized content when sending an email. Mandrill supports one specific element of the MailChimp template language: editable content areas (also known as mc:edit regions). You can use these within your desired template to create regions that can be completely replaced with customized content when sending an email. AudienceStream will populate these areas dynamically. Within Mandrill, you may also use Merge tags to personalize your messages with your recipients’ names, addresses, order information, or other customized content. Step 1 : Create or Edit the template. We will create and assign our editable regions and merge variables within the template. For this example, we will create a "header" , "main", and "footer" section. To add an editable region to your HTML, you'll add the following within an HTML tag: mc:edit="section-name" It is important when creating your editable regions that each one has a unique identifier. Next, we will need to define our merge variables to create an element of personalization to our emails. We will need to make variables for our first name, response email, and a special one to show based on certain conditions. It is important to note that merge tags use the following format, with a pipe ( | ) and asterisk (<code>*) on each side of the merge tag name: *|MERGETAG|* Mandrill conditional merge tags support traditional IF, ELSE, ELSEIF, IFNOT logic, and the following operators: = equal to != does not equal > greater than < less than >= greater than or equal to <= less than or equal to Step 2: Configure Actions Next, we must set up and configure our connector in AudienceStream. If you are unfamiliar with the process, please see the post below. AudienceStream Mandrill Connector In AudienceStream, navigate to the "Actions" tab of your Mandrill Connector. It is in this window that we select our desired template and map our editable areas and merge variables. For this example, we will set our merge variables ("FNAME", "MERGE", "SUPPORT_TEAM_EMAIL") and editable areas to custom values to better illustrate what is happening. For a live use case though, these variables would be mapped to various AudienceStream attributes like traits and visitor ID's. Next, we will need to save and publish our changes. Step 3: Validate email results After we have defined the dynamic areas of the template and configured our actions, we will need to ensure that we are getting the proper email results. This validation essentially has two parts: Use a trace to ensure that the email action is firing successfully. Ensure that the email is being delivered and is in the proper format. In the image above we can see that our merge variables were properly set with the values we put in our custom fields, and the header content was successfully replaced. Conclusion: Mandrill offers a flexible platform to meet the many needs their users require. Through the use of merge variables and editable content areas, we can manipulate our templates to satisfy our most challenging transactional email use cases. ... View more

This article describes how to set up the Facebook Audiences connector in your Customer Data Hub account. In this article: Connector Actions Action Name AudienceStream EventStream Add User to Custom Audience ✓ ✗ Remove User from Custom Audience ✓ ✗ Opt Out User from All Custom Audiences ✓ ✗ 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 Documentation: FaceBook Marketing API Batch Limits This connector uses batched requests to support high-volume data transfers to the vendor. Requests are queued until one of the following three (3) thresholds is met: Max number of requests: 10000 Max time since oldest request: 10 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: Ad Account ID Required Facebook Audiences Account ID you want to manage. (Learn more.) Before you can use this connector and build a custom audience in Facebook, you must agree to the Facebook Custom Audience Terms. This connection will generally expire within 60 days, causing unpredictable results for all Facebook Ad actions. Reestablish the connection at any point by clicking Establish Connection/Connected. Before clicking the Establish Connection button, ensure that you are signed into Facebook with the account that is linked with the Ad Account ID that is being used. If this is not the case issues, can arise with the token that is generated. Settings specific to the Facebook Audiences Connector Facebook App ID (Required) The ID of the Facebook App you want to connect to. Request "Ads Management Standard Access" to get more resources such as a better rate limit. For more information, see: Facebook Marketing API: Access and Authentication. Make sure to request "ads_management" permission for for Ads Management. For more information, see: Facebook Login: Permissions Reference. Facebook App Secret (Required) App Secret for the Facebook App you want to connect to, which can be found in Facebook app > Settings > Basic. Action Settings - Parameters and Options Click Next or go to the Actions tab. This is where you configure connector actions. This section describes how to set up parameters and options for each action. Action - Add User to Custom Audience Parameters Parameter Description Custom Audience to Add User To Required. Select your Target Custom Audience. Audiences created from customer files are not displayed. Before you can use this connector and build a custom audience in Facebook, you must agree to the Facebook Custom Audience Terms. Email Address Identify a user based on their email address. Phone Number Identify a user based on their phone number. Facebook User ID Identify a user based on their Facebook ID. You must provide the "Facebook App ID" corresponding to the Facebook User ID (UID) when using this identifier type. Facebook App ID Required if the "Facebook User ID" is used as the user identifier. See "Facebook User ID". Mobile Advertiser ID Use this to target a user based on the app user ID, Apple's Advertising Identifier (IDFA), or Android's advertising ID. External ID Do not hash. Any unique ID from the advertiser, such as loyalty membership IDs, user IDs, and external cookie IDs. Zip Code Postal code. Exact format depends on country. City User City. Lowercase. No punctuation or spaces. Country User Country. 2-letter country code. ISO 3166-1 Alpha-2 format. US State User State in the United States. Lowercase. 2-character ANSI abbreviation code. First Name User first name. Lowercase. No punctuation or special characters. UTF-8 format. Last Name User last name. Lowercase. No punctuation or special characters. UTF-8 format. First Initial First initial of user. Lowercase. No punctuation or special characters. UTF-8 format. Year of Birth Year of birth for user. YYYY format. Values from 1900 to current year. Day of Birth Day of birth for user. DD format. Values from 01 to 31. Month of Birth Birth month for user. MM format. Values from 01 to 12. Gender Gender of user. M for male, F for female Lookalike Value An arbitrary, numeric value for each user set when you create a seed custom audience from CRM data. Facebook uses this to determine which users in audience are worth the most to you, in a quantifiable way. Check Box Check this box if the Target User Identifier is already hashed. Facebook only accepts the SHA256 hashing method. Action - Remove User from Custom Audience Parameters Parameter Description Custom Audience to Remove User From Required. Select your Target Custom Audience. Before you can use this connector and build a custom audience in Facebook, you must agree to the Facebook Custom Audience Terms. Email Address Identify a user based on their email address. Phone Number Identify a user based on their phone number. Facebook User ID Identify a user based on their Facebook ID. You must provide the "Facebook App ID" corresponding to the Facebook User ID (UID) when using this identifier type. Facebook App ID Required if the "Facebook User ID" is used as the user identifier. See "Facebook User ID". Mobile Advertiser ID Use this to target a user based on the app user ID, Apple's Advertising Identifier (IDFA), or Android's advertising ID. External ID Do not hash. Any unique ID from the advertiser, such as loyalty membership IDs, user IDs, and external cookie IDs. Zip Code Postal code. Exact format depends on country. City User City. Lowercase. No punctuation or spaces. Country User Country. 2-letter country code. ISO 3166-1 Alpha-2 format. US State User State in the United States. Lowercase. 2-character ANSI abbreviation code. First Name User first name. Lowercase. No punctuation or special characters. UTF-8 format. Last Name User last name. Lowercase. No punctuation or special characters. UTF-8 format. First Initial First initial of user. Lowercase. No punctuation or special characters. UTF-8 format. Year of Birth Year of birth for user. YYYY format. Values from 1900 to current year. Day of Birth Day of birth for user. DD format. Values from 01 to 31. Month of Birth Birth month for user. MM format. Values from 01 to 12. Gender Gender of user. M for male, F for female Lookalike Value An arbitrary, numeric value for each user set when you create a seed custom audience from CRM data. Facebook uses this to determine which users in audience are worth the most to you, in a quantifiable way. Check Box Check this box if the Target User Identifier is already hashed. Facebook only accepts the SHA256 hashing method. Action - Opt Out User from All Custom Audiences Parameters Parameter Description Email Address Identify a user based on their email address. Phone Number Identify a user based on their phone number. Facebook User ID Identify a user based on their Facebook ID. You must provide the "Facebook App ID" corresponding to the Facebook User ID (UID) when using this identifier type. Facebook App Id Required if the "Facebook User ID" is used as the user identifier See "Facebook User ID". Mobile Advertiser ID Use this to target a user based on the app user ID, Apple's Advertising Identifier (IDFA), or Android's advertising ID. External ID Do not hash. Any unique ID from the advertiser, such as loyalty membership IDs, user IDs, and external cookie IDs. Zip Code Postal code. Exact format depends on country. City User City. Lowercase. No punctuation or spaces. Country User Country. 2-letter country code. ISO 3166-1 Alpha-2 format. US State User State in the United States. Lowercase. 2-character ANSI abbreviation code. First Name User first name. Lowercase. No punctuation or special characters. UTF-8 format. Last Name User last name. Lowercase. No punctuation or special characters. UTF-8 format. First Initial First initial of user. Lowercase. No punctuation or special characters. UTF-8 format. Year of birth Year of birth for user. YYYY format. Values from 1900 to current year. Day of birth Day of birth for user. DD format. Values from 01 to 31. Month of Birth Birth month for user. MM format. Values from 01 to 12. Gender Gender of user. M for male, F for female Lookalike Value An arbitrary, numeric value for each user set when you create a seed custom audience from CRM data. Facebook uses this to determine which users in audience are worth the most to you, in a quantifiable way. Check Box Check this box if the Target User Identifier is already hashed. Facebook only accepts the SHA256 hashing method. Using the Facebook Audiences Connector Create a Visitor ID Attribute The Facebook Audiences connector requires at least one Visitor ID attribute with the ability to be passed through to Facebook Audiences. Use the following resource to set up a Visitor ID attribute: Setting up a Visitor ID attribute Facebook Marketing API Define an Audience Your account may have several Visitor ID attributes defined. In this case, it is important to create a visitor-scoped attribute of the Boolean data type and named "Known Visitor" to check for the existence of any of the Visitor IDs. Using this attribute ensures that the audience only contains visitors with an assigned Visitor ID that can be passed to Facebook. You cannot target an unknown visitor. This connector also has required ID parameters, such as email, phone, app, or user IDs. At least one of these IDs is required. Including these IDs in your audience filter helps avoid connector errors. Use the following example to create an audience filter of visitors that have a "Known Visitor" Boolean data type set to "true". You can add the badge and Boolean attributes in advance or add them when creating the filter. Connect Tealium to Your Facebook Audiences Account You will need the account ID to configure the connector with your Facebook Audiences account. Use the following steps to get your Facebook Audiences account ID: Log into your Facebook Audiences account. Click an ad account, campaign, ad set, or ad in Ads Manager. Copy the account_id parameter value from the URL in your browser then return to the connector in AudienceStream. In the Configure window, add your title and any relevant notes and your Ad Account ID (copied from above). Click Establish Connection to verify the connection. Create Custom Audience Now that you are connected to your Facebook Audiences account, it's time to create a Custom Audience. You will need to create your first Custom Audience on the Facebook site to accept the terms and conditions before you are able to create a Custom Audience via the connector. Use the following steps to create a custom audience: In the connector configuration, click the Create tab. Enter the desired Custom Audience name and a short description. Click Create. The customer_file_source parameter supports the following values: USER_PROVIDED_ONLY PARTNER_PROVIDED_ONLY BOTH_USER_AND_PARTNER_PROVIDED On the Facebook Audiences site, you have the option to create audiences based on a customer list, website traffic, or app activity. For this example, create your audience based on a customer list. In order to use your custom audience, it must contain a minimum of 20 entries. If your audience has been created successfully, a small check icon displays beside the button. Specify Connector Actions You must now specify the actions you want the connector to take. Use the following steps to specify actions for the connector: Click the Actions tab. Select Add User to Custom Audience. Click + Create Action. Configure Connector Actions Use the following steps to configure actions for the connector: From the Audience menu, select the Shoe-Fans audience you created earlier. The Custom Audience to Add User To menu displays audiences that exist in your Facebook Audiences account. From the Custom Audience to Add User To drop-down list, select the audience you want to add visitors to. In the Target User Identifier drop-down list, map the visitor email attribute to the matching visitor identifier in your Facebook Audiences account. Leave the WHEN set to Joined Audience. Click Save. Testing The most effective testing method is to run a Trace to ensure that your events are handled properly and to check your Facebook dashboard to verify that your Custom Audience was created and populated. FAQ Why can't I see my audiences in the AudienceStream drop-down list? If you have more than 2,000 audiences in Facebook, they are not all selectable in the drop-down list from an AudienceStream connector. Use the following steps in Facebook to view all audiences and select the identifier for a specific audience: Log in to Facebook as the user that has access to the Facebook Audiences account. Go to https://www.facebook.com/adsmanager/audiences. Find the audience you are looking for and copy the Audience ID. If the Audience ID does not display, you can modify your table column view to include it. Return to AudienceStream and enter the Audience ID as custom value for your AudienceStream connector. ... View more