-
Expand/CollapseMenu
- TLC Home Home
- Forums Forums
- Product Guides Product Guides
- Developer Docs Developer Docs
- Product Ideas Product Ideas
- Education Education
- Blog TLC Blog
- Support Desk Support Desk
Tealium Learning Center
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Home
- :
- About Tony_Taliaferro
Friday
since
09-25-2017
Tealium Employee
This widget could not be displayed.
- loginsThis widget could not be displayed.
- 184Posts
- 35Kudos
- 0Solutions
User Recent Badges
Wednesday
This article describes how to use the Iterable data source to create a webhook in your Iterable account to send actionable events into EventStream.
In this article:
Table of Contents Placeholder
Prerequisites
Iterable account
EventStream/AudienceStream account
How It Works
Iterable offers a Webhook API that sends outgoing requests to an endpoint that you specify. These requests act like push notifications to EventStream to inform it about things that happened in your Iterable account. When you add the Iterable data source in the CDH, a unique endpoint is generated. This endpoint is used to configure the Iterable webhook. Once configured you can create subscriptions based on a topics and receive related push notifications to automate use cases, stay informed, and increase productivity.
Iterable Data Source
The Iterable data source generates a unique URL to use as the HTTP POST URL in your Iterable configuration. The URL is generated in the following format:
https://collect.tealiumiq.com/integration/event/ACCOUNT/PROFILE/DATA_SOURCE_KEY
Add the Iterable data source before proceeding. (Learn how to add a data source)
Iterable Setup
Once you have your data source endpoint, use the following steps to go to your Iterable account and create the webhook.
Log in to your Iterable account.
Go to Integrations > System Webhooks.
Click Create Webhook. The system webhook creation form displays.
Enter the following Webhook URL: https://collect-us-east1.tealiumiq.com/integration/event/tealium/main/phichx
Click Edit.
Check the Enabled checkbox.
Click Save.
Events and Attributes
All incoming Iterable event attributes are automatically prefixed with iterable_ . For example, when the Iterable webhook sends eventName , the matching EventStream event attribute is iterable_eventName .
For a full list of webhook events and attributes generated by Iterable, see the Iterable Webhook Documentation.
Event Attribute
Type
Example
iterable_datafields_appalreadyrunning
Boolean
false
iterable_datafields_browsertoken
String
cZn_inqLGPk:APA91bHsn5jo0-4V55RB38eCeLHj8ZXVJYciU7k6Kipbit3lrRlEe2Dt6bNzR4lSf6r2YNVdWY8l90hV0jmb_Y7y5ufcJ68xNI7wbsH6Q2jbEghA_Qo4kWbtu6A4NZN4gxc1xsEbyh7b
iterable_datafields_campaignid
Number
723636
iterable_datafields_campaignname
String
My campaign name
iterable_datafields_canonicalurlid
String
3145668988
iterable_datafields_channelid
Number
8539
iterable_datafields_city
String
San Francisco
iterable_datafields_contentavailable
Boolean
false
iterable_datafields_contentid
Number
3681
iterable_datafields_createdat
String
2019-08-07 23:43:48 +00:00
iterable_datafields_device
String
Gmail
iterable_datafields_email
String
docs@iterable.com
iterable_datafields_emailid
String
723636:t1020396:docs@iterable.com
iterable_datafields_emailsubject
String
My subject
iterable_datafields_expiresat
String
2019-08-08 22:37:40 +00:00
iterable_datafields_fromphonenumberid
Number
258
iterable_datafields_fromsmssenderid
Number
258
iterable_datafields_inappbody
String
<!DOCTYPE html PUBLIC \\-//W3C//DTD XHTML
iterable_datafields_ip
String
162.245.22.159
iterable_datafields_isghostpush
Boolean
false
iterable_datafields_linkid
String
3145668988
iterable_datafields_linkurl
String
https://www.iterable.com
iterable_datafields_messagecontext_savetoinbox
Boolean
false
iterable_datafields_messagecontext_trigger
String
immediate
iterable_datafields_messageid
String
4238c918b20a41dfbe9a910275b76f12
iterable_datafields_messagetypeid
Number
9106
iterable_datafields_payload_path
String
"your_folder/30"
iterable_datafields_platformendpoint
String
<Platform endpoint>
iterable_datafields_pushmessage
String
Push message text
iterable_datafields_reason
String
DuplicateMarketingMessage
iterable_datafields_recipientstate
String
Complaint
iterable_datafields_region
String
CA
iterable_datafields_signupsource
String
ResubscribePage
iterable_datafields_smsmessage
String
Message text
iterable_datafields_smsproviderresponse_code
Number
20404
iterable_datafields_smsproviderresponse_message
String
The requested resource /2010-04-01/Accounts/ACCOUNT_NUMBER/Messages.json was not found
iterable_datafields_smsproviderresponse_more_info
String
https://www.twilio.com/docs/errors/20404
iterable_datafields_smsproviderresponse_status
Number
404
iterable_datafields_templateid
Number
1020396
iterable_datafields_templatename
String
My template name
iterable_datafields_tophonenumber
String
+16503926753
iterable_datafields_transactionaldata_comment
String
transactionalData lists the...
iterable_datafields_unsubsource
String
EmailLink
iterable_datafields_url
String
https://iterable.com/?_e=a4b8cc0358422787f5cd5525005017172432ae33
iterable_datafields_useragent
String
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36
iterable_datafields_useragentdevice
String
Mac
iterable_datafields_workflowid
Number
53505
iterable_datafields_workflowname
String
My workflow name
iterable_email
String
dev@tealium.com
iterable_eventname
String
pushUninstall
Vendor Documentation
Iterable Webhook Documentation
... View more
a week ago
This article describes how to use the Intercom data source to create a webhook in your Intercom account to send actionable events into EventStream.
In this article:
Table of Contents Placeholder
Prerequisites
Intercom account
EventStream/AudienceStream account
How It Works
Intercom offers a Webhook API that sends outgoing requests to an endpoint that you specify. These requests act like push notifications to EventStream to inform it about things that happened in your Intercom account. When you add the Intercom data source in the CDH, a unique endpoint is generated. This endpoint is used to configure the Intercom webhook. Once configured, you can create subscriptions based on topics and receive related push notifications to automate use cases, stay informed, and increase productivity.
Intercom Data Source
The Intercom data source generates a unique URL to use as the HTTP POST URL in your Intercom configuration. The URL is generated in the following format:
https://collect.tealiumiq.com/integration/event/ACCOUNT/PROFILE/DATA_SOURCE_KEY
Add the Intercom data source before proceeding. (Learn how to add a data source)
Intercom Setup
Once you have your data source endpoint, use the following steps to go to your Intercom account and create the webhook.
Log in to your Intercom account.
Navigate to your applications.
Select the application you want to configure.
From the Configure menu, select Webhooks.
For your Intercom data source, specify the request endpoint URL generated by Tealium, as described in the previous section.
Select the topics that you want to receive notifications about.
Events and Attributes
All incoming Intercom event attributes are automatically prefixed with intercom_ . For example, when the Intercom webhook sends data.item.conversation_message.type , the matching EventStream event attribute is intercom_data_item_conversation_message_type .
For a full list of webhook events and attributes generated by Intercom, go to Intercom - Webhook Models.
Event Attribute
Type
Example
intercom_type
String
"notification_event"
intercom_id
String
"notif_4e3504a3-ba3f-46dc-ab48-8e4d5bdfdf4e"
intercom_created_at
Number
"1571080403"
intercom_topic
String
"conversation.admin.closed"
intercom_data_type
String
"notification_event_data"
intercom_data_item_type
String
One of the following:
"conversation"
"user"
"contact"
"usertag"
"ead"
"contacttag"
"visitor"
"event"
"ping"
intercom_data_item_id
String
"24098479713"
intercom_data_item_user_type
String
"user"
intercom_data_item_user_email
String
"wz1996@gmail.com"
intercom_data_item_assignee_type
String
"admin"
intercom_data_item_assignee_email
String
"weibin.zhong@intercom.io"
intercom_data_item_conversation_message_subject
String
"Hello"
intercom_data_item_conversation_message_body
String
"<p>This is a new conversation</p>"
intercom_data_item_conversation_parts_conversation_parts
List of objects
"[{"type":"conversation_part", "id": "3928295317"},{"type": "conversation_part", "id": "3928295318"}]"
intercom_data_item_tags_tags
List of objects
"[{"type": "tag", "id": "2913705", "name": "API"}, {"type": "tag", "id": "2914621", "name": "Feature request"}]"
intercom_data_item_id
String
"530370b477ad7120001d"
intercom_data_item_user_id
String
"25"
intercom_data_item_email
String
"wash@serenity.io"
intercom_data_item_phone
String
"+1123456789"
intercom_data_item_name
String
"Hoban Washburne"
intercom_data_item_company_id
String
"6"
intercom_data_item_event_name
String
"invited-friend"
Vendor Documentation
Intercom developer hub
Intercom: webhooks overview
Intercom: setting up webhooks
Intercom: setting up auth - permissions and scopes
Intercom: webhook models
... View more
2 weeks ago
As the coronavirus (COVID-19) continues to be the lead story in global news and and on social media, we want to keep each of you up to date on what Tealium is doing to keep our employees safe and your services running.
For our full statement and action plan, see A Message from Tealium Regarding Coronavirus (COVID-19).
As always, we are proud to be your trusted partner and look forward to working with you as we navigate these circumstances.
... View more
3 weeks ago
This article describes how to set up the Airship Push connector in your Customer Data Hub account.
In this article:
Table of Contents Placeholder
Connector Actions
Action Name
AudienceStream
EventStream
Send a Push Notification Based on Named User Identifier
✓
✗
Send Push Notification Based on Channel ID
✓
✗
Send an Email Notification Based on Named User Identifier
✓
✗
Configure Settings
Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector.
After adding the connector, configure the following settings:
App Key
Basic master auth is required for push endpoints.
For more information, see Airship Authentication.
Master Secret
Basic master auth is required for push endpoints.
For more information, see Airship Authentication.
Action Settings - Parameters and Options
Click Next or go to the Actions tab. This is where you configure connector actions.
This section describes how to set up parameters and options for each action.
Action - Send a Push Notification Based on Named User Identifier
Parameters
Parameter
Description
Named User
A named_user is an alternate name mapped to a user profile in a different database, such as CRM, that can be used to target devices associated with that profile.
For more information on named users, see: Named Users.
Notification Message
A notification message, displayed for any platforms receiving the push.
For more information on this endpoint, see: Airship Push/Post.
Action - Send Push Notification Based on Channel ID
Parameters
Parameter
Description
Channel ID
The Channel ID for the device you wish to send a push message to.
For more information on Channel ID's, see: Airship Intro to Channels.
Notification Message
A notification message, displayed for any platforms receiving the push.
For more information on this endpoint, see: Airship Push/Post.
Action - Send an Email Notification Based on Named User Identifier
Parameters
Parameter
Description
Named User
A named_user is an alternate name mapped to a user profile in a different database, such as CRM, that can be used to target devices associated with that profile.
For more information on named users, see: Named Users.
Message Type
Must be transactional or commercial.
For more information on this endpoint, see: Airship Email Override.
Plain Text Body
The plain text body of the email you want to send, no larger than 100kb.
For message_type:commercial , the body must contain a [[ua_unsubscribe]] link, which will be replaced by the unsubscribe link in Airship.
You can send the user to a custom "goodbye" page by providing an href in the following format: [[ua-unsubscribe href="your url here"]] .
If you include an href , Airship unsubscribes the user before redirecting to your page.
Reply To
String.
Required.
The reply-to address.
Sender Address
The email address of the sender.
The domain of the email must be enabled in the email provider at the delivery tier/
Example: Sparkpost
Sender Name
The common name for the sender, visible to email recipients.
Subject
The subject line of the email.
Bypass Opt In Level
You can set this when message_type is set to transactional to send a business critical email.
If set to true, the message is sent to your entire audience, ignoring the transactional_opted_out status.
HTML Body
The rich-text html body of the email, no larger than 100kb.
For message_type:commercial , the body must contain an unsubscribe link in the Unsubscribe format.
You can send the user to a custom "goodbye" page by providing an href attribute in the link: Unsubscribe.
If your unsubscribe link includes an href , Airship unsubscribes the user before redirecting to your page.
... View more
a month ago
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.
Connectors
New/Cool Stuff
New marketplace connector: Tapjoy Conversion Postbacks (Learn more)
New marketplace connector: Xandr Instant Audience Service, Customer-Provided Credentials (BETA). (Learn more)
iQ Tag Management
New/Cool Stuff
Applied various performance enhancements to Consent Manager.
Customer Data Hub
New/Cool Stuff
New Communications data source: Intercom
Installations
New/Cool Stuff
Flutter
Added support for Tealium remote commands (Learn more)
Updated Tealium libraries to Android 5.7.0 and iOS 5.6.6.
iOS Swift
Updated mobile publish settings to be enabled by defaultin Version 1.9.0. (Learn more)
Added the ability to remotely change event batch size for from the iQ Tag Management Publish Settings interface to Version 1.9.0 in order to match functionality in the Tealium iOS (Objective-C) and Tealium Android libraries. (Learn more)
Added Swift Package Manager support. (Learn more)
Removed the requirement to bundle Swift runtime with applications when using Swift 5.x in order to reduce the size of application bundles.
Added Mac Catalyst support for iOS applications enabled to run on macOS Catalina versions 10.15.x.
Added lifecycle tracking methods to the public API. (Learn More)
Added a list of enabled modules to track each request ( enabled_modules=["attribution","tagmanagement"] ) .
Optimized the Tealium.update method so that modules are no longer deinitialized and reinitialized when the update method is called to change TealiumConfig settings.
Added the "wifi only sending" option to Mobile Push Settings to queue hits when wifi is unavailable.
Added a "battery saver" option to Mobile Push Settings to queue hits when a device has less than 20% battery power remaining.
React Native
Added 1.0.8 support for Tealium remote commands to allow remote commands to be added in a JavaScript file and for the payload to be passed back using a callback function. ( Learn More )
Fixes
iOS Swift
Updated version number to to 1.9.1 to correct an issue with the Carthage dependency manager.
Removed support for older versions of Swift and instructed users to use Tealium Swift 1.8.2 if they are unable to use Swift 5.x.
Removed Objective-C dependency required for Swift Package Manager support, which also corrects issue related to import of bridging headers.
To avoid compiler warnings, the setters and getters on the TealiumConfig class are now deprecated and properties are used instead.
... View more
02-25-2020
11:36 AM
This article describes how to set up the Clicktale tag in your iQ Tag Management (TiQ) account.
In this guide:
Table of Contents Placeholder
How it Works
Clicktale empowers brands to act on unique behavioral insights to turn user experiences into measurable advantages. For more information about Clicktale, a Contentsquare company, visit contentsquare.com.
What to Expect from this Integration
A working integration of iQ Tag Management with the Clicktale tag from the Tealium tag marketplace enables customers to seamlessly execute session replays associated with clickstream data in order to detect and minimize end customer friction associated with tagged web pages.
Prerequisites
Tealium
iQ Tag Management
AudienceStream
EventStream (optional)
Clicktale
Clicktale real-time signals are available to all customers with access to the Data Export
Signals Extensions
Clicktale signals enable joint Tealium and Clicktale customers to identify real-time behaviors, trigger events, and activate on those signals through AudienceStream. Once a potential friction or fraud behavior is detected, these signals are automatically sent to both Clicktale and AudienceStream. From there, customers can build powerful behavior-based segments that can be used across their marketing and advertising ecosystem.
Some of the features described below require configuration of additional JavaScript extensions. All required code will be provided by your Clicktale representative.
Signals Settings
This JavaScript code extension is required for any of the signals described below. When adding the JavaScript Code extension, ensure that the order of execution is set to execute specific signals code and that all signals extensions are scoped to your Clicktale tag.
The Clicktale Signals settings provide the following capture points associated with web page activity:
Friction
Repeated Scrolling repeated_scrolling_signal Identifies when a visitor scans the page quickly and scrolls repeatedly from top to bottom. Identifies a potentially poor user experience or a frustrated visitor.
Constant Hovering constant_hovering_signal Identifies when a visitor consistently hovers over the same element without clicking. This signal indicates a visitor’s intent or interest without clicking the element.
Consecutive Clicking (Clickable Element) consecutive_click_signal Identifies when a visitor repeatedly clicks the same (clickable) element without a response from the page. The customer does not click any other element between clicks. This signal indicates a potential issue with the element.
Consecutive Clicking (Un-clickable Element) Identifies when a visitor repeatedly clicks the same (un-clickable) element without a response from the page. The customer does not click any other element between clicks. This signal indicates a potential design flaw.
Rage Clicking rage_click_signal Identifies when a customer repeatedly clicks the same element without a response from the page. This event triggers regardless of whether customers click other elements in between clicks.
JavaScript Click Error js_error_signal Identifies each time a click triggers a JavaScript error.
Fraud
Excessive Pasting excessive_paste_fraud_signal Triggers when thresholds are met that identify abnormal and potentially fraudulent pasting behavior within the same visitor session. There are three (3) levels of Fraud likelihood: low, medium, and high.
Excessive Reload excessive_reloads_fraud_signal Triggers when thresholds are met that identify abnormal and potentially fraudulent reload behavior within the same visitor session. There are three (3) levels of Fraud likelihood: low, medium, and high
Ad Blocking
Ad Blocker Signal adblocker_signal Identifies when or if certain files are blocked, which identifies that an ad-blocker is present.
You can optionally use signals from your EventStream event specifications and your AudienceStream visitor attributes.
Tag Configuration
First, go to Tealium's tag marketplace and add the Clicktale Carmel tag (Learn more about how to add a tag).
After adding the tag, configure the following settings in the Data Mappings section.
Tag Tips
Conversion fires when Order ID is set.
In order to send your Clicktale Replay Link to UDH, you must:
Contact your Clicktale representative to enable the generation of the replay link.
Set the Send Replay Link configuration to True.
The Contentsquare tag automatically detects the Tealium account and profile loading on the page and sends the replay link there. To send the replay link to a different account or profile, override the default values by mapping the desired account and profile to the tealium_account and tealium_profile destinations, respectively
To pass Tealium Audiences and Badges to Clicktale:
Contact your Clicktale representative to enable the receiving of this data.
To send a Badge to Clicktale, navigate to the Badges tab in the mapping toolbox and enter the name by which the Badge will be identified in the Clicktale system.
To send all Audiences to Clicktale, toggle the Send UDH Audiences toggle to True.
Applying Load Rules
Load Rules determine when and where to load an instance of this tag. The 'Load on All Pages' rule is the default load rule. To load this tag on a specific page, create a new load rule with the relevant conditions.
Load this Tag on the page where you want to track the visitor's mouse movements.
Data Mappings
Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see Data Mappings.
The available categories are:
Standard
Variable
Description
title
Required.
Identifies the tag instance.
Clicktale Carmel is the default name.
When using multiple tags by the same vendor, assign a unique name.
partition
Partition.
The partition where data is sent.
Map to this variable to dynamically configure the server partition value.
project_guid
Project GUID.
Map to this variable to set the project guide field.
send_replay_link
Send Clicktale Replay Link
Values are true or false.
send_udh_audiences
Send UDH Audiences.
Values are true or false.
tealium_account
Tealium Account.
tealium_profile
Tealium Profile.
E-Commerce
Variable
Description
order_id
Order ID.
Overrides _corder .
Required for transactions.
order_total
Order total.
Overrides _ctotal .
Required for transactions.
order_shipping
Shipping amount.
Overrides _cship .
order_tax
Tax amount.
Overrides _ctax .
product_id
Array
List of Product IDs.
Overrides _cprod .
product_name
Array
List of Names.
Overrides _cprodname .
Required for transactions.
product_sku
Array
List of SKUs.
Overrides _csku .
Required for transactions.
product_category
Array
List of Categories.
Overrides _ccat .
product_quantity
Array
List of Quantities.
Overrides _cquan .
Required for transactions.
product_unit_price
Array
List of Prices.
Overrides _cprice .
Required for transactions.
Badges
Variable
Description
title
Badge Identifier.
To send the mapped badge to Clicktale, enter the name by which the badge will be identified in Clicktale.
Tealium automatically includes the badge title as a child property of a new object send_udh_data
Your badge name will appear as mapped to send_udh_data .
... View more
02-21-2020
11:32 AM
This article describes how to set up the Salesforce Email Studio OAuth2 (ExactTarget) connector in your Customer Data Hub account.
In this article:
Table of Contents Placeholder
Prerequisites
Salesforce Marketing Cloud Account
Salesforce Marketing Cloud App Client Credentials
Appropriate permissions set on the Salesforce Marketing Cloud App
Connect Using the OAuth2 Authentication Scheme
Use the following steps to connect Tealium to ExactTarget using OAuth2 authentication scheme:
Log into your ExactTarget account and from the top right menu, select Setup.
Navigate to Platform Tools > Apps > Installed Packages.
At the top right of the Installed Packages panel, click New to create a new package.
In the opened dialog box, name your package and click Save.
In the newly created package, click Add Component.
Select API Integration as the component type and Server-to-Server as the integration type.
Set appropriate Server-to-Server properties. If correct permissions are not provided, the integration may fail. Changing permissions after the package has been created may require some wait time for the permissions to apply.
Save your component. In the package window, the component named API Integration shows the authentication information.
Copy the following values to use later in the connector configuration:
Client ID
Client Secret
SOAP Base URI
Also copy your account's MID value, found in the top menu bar.
Connector Actions
Action Name
AudienceStream
EventStream
Send Email to User
✓
✓
Add to Email List
✓
✓
Remove from Email List
✓
✓
Upsert Subscriber and Add to Email List(s)
✓
✓
Data Extension - Add Record
✓
✓
Data Extension - Add Multiple Records
✓
✓
Data Extension - Delete Record
✓
✓
Data Extension - Update Record
✓
✓
Data Extension - Upsert Record
✓
✓
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:
This connector requires the following information to connect to ExactTarget's SOAP protocol, upgraded with OAuth2 authentication scheme.
Market Cloud App Client ID
Required: provide your app client ID.
See: Get OAuth Client Credentials
Client Secret: Required: provide your app client secret
Account ID
Required.
Provide account identifier (MID) of the target business unit.
Tenant-specific subdomain
Required: provide tenant-specific subdomain for your application.
If your SOAP Base URL looks something like this: https://mctg-xxxxxx.soap.marketingcloudapis.com/, then provide the portion of this URL between two slashes and the first period, in this example it would be mctg-xxxxxx .
The connector will automatically augment this subdomain name with correct suffixes for authentication and for SOAP messaging.
ExactTarget Account ID (MID)
Action Settings - Parameters and Options
Click Next or go to the Actions tab. This is where you configure connector actions.
See Salesforce Marketing Cloud Email Studio (Legacy authentication) for details about actions setup.
This section describes how to set up parameters and options for each action.
Action - Send Email to User
Parameters
Parameter
Description
Business Unit
Recommended.
Select appropriate business unit.
If not specified then default option will be used, which corresponds to default business unit of configured Marketing Cloud user.
Triggered Send Email Interaction
Required.
Select triggered send email interaction.
Subscriber Lookup By Key
Required.
Lookup existing subscriber by key to send them an email.
Disable Subscriber Lookup
To disable lookup, check "Disable Subscriber Lookup" and configure "Subscriber Email" section.
Subscriber Email
Provide email to send message to (required if subscriber lookup is disabled).
Email can be left blank to use looked-up subscriber's email instead.
Attributes to Add or Overwrite
Map values to keys to include dynamic contents in your email and a sample input, see: Passing Content to a Triggered Send Message at Send Time.
To manage your Profile Attributes, see: Profile and Preference Attributes.
Don't Send Email to Subscriber with Status
If looked-up subscriber has one of the following statuses then do not send the email.
Enable Asynchronous Processing
Check option to enable asynchronous processing. API calls will be queued before being processed, rather than directly at the time the API call is received.
Async API calls are generally faster to complete and always return successful responses, even if underlying queued operation fails at a later point.
For more information, see: Asynchronous Processing.
Action - Add to Email List
Parameters
Parameter
Description
Business Unit
Recommended.
Select appropriate business unit.
If not specified then default option will be used, which corresponds to default business unit of configured Marketing Cloud user.
Email List
Required.
Select email list.
Subscriber Lookup By Key
Required.
Provide subscriber key to find existing subscriber.
Enable Asynchronous Processing
Check option to enable asynchronous processing.
API calls will be queued before being processed, rather than directly at the time the API call is received.
Async API calls are generally faster to complete and always return successful responses, even if underlying queued operation fails at a later point.
For more information, see: Asynchronous Processing.
Action - Remove from Email List
Parameters
Parameter
Description
Business Unit
Recommended.
Select appropriate business unit.
If not specified then default option will be used, which corresponds to default business unit of configured Marketing Cloud user.
Email List
Required.
Select email list.
Subscriber Lookup By Key
Required.
Provide subscriber key to find existing subscriber.
Enable Asynchronous Processing
Check option to enable asynchronous processing.
API calls will be queued before being processed, rather than directly at the time the API call is received.
Async API calls are generally faster to complete and always return successful responses, even if underlying queued operation fails at a later point.
For more information, see: Asynchronous Processing.
Action - Upsert Subscriber and Add to Email List(s)
Parameters
Parameter
Description
Business Unit
Recommended.
Select appropriate business unit.
If not specified then default option will be used, which corresponds to default business unit of configured Marketing Cloud user.
Subscriber Key
Required.
Subscriber Email Address
Required.
Add Subscriber to Email List(s)
Select one or more email lists to add subscriber to.
User Status
Select value to update user's status to.
Enable Asynchronous Processing
Check option to enable asynchronous processing.
API calls will be queued before being processed, rather than directly at the time the API call is received.
Async API calls are generally faster to complete and always return successful responses, even if underlying queued operation fails at a later point.
For more information, see: Asynchronous Processing.
Action - Data Extension - Add Record
Parameters
Parameter
Description
Business Unit
Recommended.
Select appropriate business unit.
If not specified then default option will be used, which corresponds to default business unit of configured Marketing Cloud user.
Data Extension
Required.
Select data extension.
Enable Asynchronous Processing
Check option to enable asynchronous processing.
API calls will be queued before being processed, rather than directly at the time the API call is received.
Async API calls are generally faster to complete and always return successful responses, even if underlying queued operation fails at a later point.
For more information, see: Asynchronous Processing.
Action - Data Extension - Add Multiple Records
Parameters
Parameter
Description
Business Unit
Recommended.
Select appropriate business unit.
If not specified then default option will be used, which corresponds to default business unit of configured Marketing Cloud user.
Data Extension
Required.
Select data extension.
Enable Asynchronous Processing
Check option to enable asynchronous processing.
API calls will be queued before being processed, rather than directly at the time the API call is received.
Async API calls are generally faster to complete and always return successful responses, even if underlying queued operation fails at a later point.
For more information, see: Asynchronous Processing.
Action - Data Extension - Delete Record
Parameters
Parameter
Description
Business Unit
Recommended.
Select appropriate business unit.
If not specified then default option will be used, which corresponds to default business unit of configured Marketing Cloud user.
Data Extension
Required.
Select data extension.
Enable Asynchronous Processing
Check option to enable asynchronous processing.
API calls will be queued before being processed, rather than directly at the time the API call is received.
Async API calls are generally faster to complete and always return successful responses, even if underlying queued operation fails at a later point.
For more information, see: Asynchronous Processing.
Action - Data Extension - Update Record
Parameters
Parameter
Description
Business Unit
Recommended.
Select appropriate business unit.
If not specified then default option will be used, which corresponds to default business unit of configured Marketing Cloud user.
Data Extension
Required.
Select data extension.
Enable Asynchronous Processing
Check option to enable asynchronous processing.
API calls will be queued before being processed, rather than directly at the time the API call is received.
Async API calls are generally faster to complete and always return successful responses, even if underlying queued operation fails at a later point.
For more information, see: Asynchronous Processing.
Action - Data Extension - Upsert Record
Parameters
Parameter
Description
Business Unit
Recommended:.
elect appropriate business unit.
If not specified then DEFAULT option will be used, which corresponds to default business unit of configured Marketing Cloud user.
Data Extension
Required.
Select data extension.
Enable Asynchronous Processing
Check option to enable asynchronous processing.
API calls will be queued before being processed, rather than directly at the time the API call is received.
Async API calls are generally faster to complete and always return successful responses, even if underlying queued operation fails at a later point.
For more information, see: Asynchronous Processing.
Vendor Documentation
Salesforce Marketing Cloud: Create an OAuth 2.0 API Integration in Enhanced Packages
Salesforce Marketing Cloud: API Integration
Salesforce Marketing Cloud: Authenticate Your SOAP API Calls
... View more
02-03-2020
11:17 AM
This article describes how to get the most out of Tealium and Contentsquare by setting up the Contentsquare UX Analytics tag in your Tealium iQ Tag Management account and enabling the transmission of Tealium audiences and Visitor badges to Contentsquare.
In this guide:
Table of Contents Placeholder
How it Works
Contentsquare empowers brands to act on unique behavioral insights to turn user experiences into measurable advantages. Contentsquare daily transforms trillions of digital behaviors into intelligent visualizations and recommendations that can be used to grow revenue, increase loyalty, and fuel innovation. Users can access benchmarks and predictive scoring based on leading global data sets of digital behavior across geographies and industries.
For more information, visit contentsquare.com.
What to Expect From This Integration
A working integration of iQ Tag Management with the Contentsquare tag from the Tealium tag marketplace enables customers to execute session replays associated with clickstream data in order to detect and minimize end customer friction associated with tagged web pages.
Prerequisites
Tealium
iQ Tag Management
AudienceStream
EventStream (optional)
Contentsquare
Contentsquare Business Edition or higher
Signals Extensions
Contentsquare signals enable joint Tealium and Contentsquare customers to identify real-time behaviors, trigger events, and activate on those signals through AudienceStream. Once a potential friction or fraud behavior is detected, these signals are automatically sent to both Contentsquare and AudienceStream. From there, customers can build powerful behavior-based segments that can be used across their marketing and advertising ecosystem.
To learn how to set up signals for Clicktale Carmel, see the Tealium + Clicktale Carmel Enablement Guide.
https://tealium.atlassian.net/browse/DOC-4
Some of the features described below require configuration of additional JavaScript extensions. All required code will be provided by your Contentsquare representative.
Signals Settings
This JavaScript code extension is required for any of the signals described below. When adding the JavaScript Code extension, ensure that the order of execution is set to execute specific signals code and that all signals extensions are scoped to your Contentsquare tag.
To learn how to set up signals for Clicktale Carmel, see the Tealium + Clicktale Carmel Enablement Guide.
The Contentsquare Signals settings provide the following capture points associated with web page activity:
Friction
Repeated Scrolling repeated_scrolling_signal Identifies when a visitor scans the page quickly and scrolls repeatedly from top to bottom. Identifies a potentially poor user experience or a frustrated visitor.
Constant Hovering constant_hovering_signal Identifies when a visitor consistently hovers over the same element without clicking. This signal indicates a visitor’s intent or interest without clicking the element.
Consecutive Clicking (Clickable Element) consecutive_click_signal Identifies when a visitor repeatedly clicks the same (clickable) element without a response from the page. The customer does not click any other element between clicks. This signal indicates a potential issue with the element.
Consecutive Clicking (Un-clickable Element) Identifies when a visitor repeatedly clicks the same (un-clickable) element without a response from the page. The customer does not click any other element between clicks. This signal indicates a potential design flaw.
Rage Clicking rage_click_signal Identifies when a customer repeatedly clicks the same element without a response from the page. This event triggers regardless of whether customers click other elements in between clicks.
JavaScript Click Error js_error_signal Identifies each time a click triggers a JavaScript error.
Fraud
Excessive Pasting excessive_paste_fraud_signal Triggers when thresholds are met that identify abnormal and potentially fraudulent pasting behavior within the same visitor session. There are three (3) levels of Fraud likelihood: low, medium, and high.
Excessive Reload excessive_reloads_fraud_signal Triggers when thresholds are met that identify abnormal and potentially fraudulent reload behavior within the same visitor session. There are three (3) levels of Fraud likelihood: low, medium, and high
Ad Blocking
Ad Blocker Signal adblocker_signal Identifies when or if certain files are blocked, which identifies that an ad-blocker is present.
You can optionally use signals from your EventStream event specifications and your AudienceStream visitor attributes.
Tag Configuration
First, go to the Tealium tag marketplace and add the Contentsquare tag (Learn more about how to add a tag).
After adding the tag, go to the Data Mappings section to configure any additional mappings.
Tag Tips
Conversion fires when Order ID is set.
In order to send your Contentsquare Replay Link to UDH, you must:
Contact your Contentsquare representative to enable the generation of the replay link.
Set the Send Replay Link configuration to True.
The Contentsquare tag automatically detects the Tealium account and profile loading on the page and sends the replay link there. To send the replay link to a different account or profile, override the default values by mapping the desired account and profile to the tealium_account and tealium_profile destinations, respectively.
To pass Tealium Audiences and Badges to Contentsquare:
Contact your Contentsquare representative to enable the receiving of this data.
To send a Badge to Contentsquare, navigate to the Badges tab in the mapping toolbox and enter the name by which the Badge will be identified in the Contentsquare system.
To send all Audiences to Contentsquare, toggle the Send UDH Audiences toggle to True.
Applying Load Rules
Load Rules determine when and where to load an instance of this tag. The 'Load on All Pages' rule is the default load rule.
To load this tag on a specific page, create a new load rule with the relevant conditions and load the Contentsquare tag on the page where you want to track the visitor's mouse movements.
Data Mappings
Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see Data Mappings.
The available categories are:
Standard
Variable
Description
title
Required.
Identifies the tag instance.
Contentsquare UX Analytics is the default name.
When using multiple tags by the same vendor, assign a unique name.
id_project
The Project Tag ID specific to your project.
Map to this variable to set the project guide field.
base_url
Base URL
send_replay_link
Send Contentsquare Replay Link
Values are true or false.
Also known as contensquare_replay_link .
This variable and session replay capability is currently in development for Contentsquare tag and is expected to be released in H1 2020
send_udh_audiences
Send Customer Data Hub (CDH) audiences.
Values are true or false.
tealium_account
Tealium account.
tealium_profile
Tealium profile.
E-Commerce
Variable
Description
order_id
Order ID.
Overrides _corder .
Required for transactions.
order_total
Order total.
Overrides _ctotal .
Required for transactions.
order_shipping
Shipping amount.
Overrides _cship .
order_tax
Tax amount.
Overrides _ctax .
product_id
Array
List of Product IDs.
Overrides _cprod .
product_name
Array
List of Names.
Overrides _cprodname .
Required for transactions.
product_sku
Array
List of SKUs.
Overrides _csku .
Required for transactions.
product_category
Array
List of Categories.
Overrides _ccat .
product_quantity
Array
List of Quantities.
Overrides _cquan .
Required for transactions.
product_unit_price
Array
List of Prices.
Overrides _cprice .
Required for transactions.
Badges
Variable
Description
title
Badge Identifier.
To send the mapped badge to Contentsquare, enter the name by which the badge will be identified in Contentsquare.
Tealium automatically includes the badge title as a child property of a new object send_udh_data
Your badge name will appear as mapped to send_udh_data .
... View more
01-29-2020
01:17 PM
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
Updated the Adobe Analytics connector to highlight legacy actions that will soon be deprecated. (Learn more)
Connectors
New/Cool Stuff
Updated the SOAP action parameters for the Adobe Campaign Classic Batch connector. (Learn more)
Updated the Criteo EventStream connector to make IP address optional and to pass errors in the response body instead of the response header. (Learn more)
iQ Tag Management
New/Cool Stuff
Applied various performance enhancements to Consent Manager.
Customer Data Hub
Fixes
Corrected issue causing the file import last updated timestamp to not update correctly when a data source for file import is created and a user then updates the source settings.
Corrected issue causing incorrect order of enrichments by ensuring that string attributes enriched by "join" also enrich the component to be joined.
Corrected DataAccess issue that caused view_normalized tables to populate with attribute IDs and render inaccurate query results.
Installations
New/Cool Stuff
Android 5.6.2
Embedded ProGuard rules for each module.
Android/Swift iOS
Firebase remote command. (Learn more)
Swift 1.8.2
Added a removeInstance method to the TealiumInstanceManager to allow total deinitialization (deinit) of Tealium .
Added the config.shouldAddCookieObserver = false configuration option to not use the cookie observer for WKWebView.
Optimized module initialization so that init is only called on modules that are present in the modules list.
Fixes
Swift 1.8.2
Corrected issue causing thread-related remote command crashes.
Reduced stored lifecycle sessions to 20 sessions to resolve issues with low-memory lifecycle sessions.
Corrected retain cycles that occasionally prevented a total deinitialization (deinit) of the Tealium class.
Corrected issues related to low memory lifecycle sessions when using remote commands.
... View more
01-29-2020
11:41 AM
This article describes how to get the most out of Tealium and Quantum Metric by setting up the Quantum Metric tag in Tealium iQ Tag Management and enabling the Quantum Metric Tag to send Session Replay URLs to Tealium AudienceStream.
In this guide:
Table of Contents Placeholder
How it Works
Quantum Metric is the Digital Experience Intelligence platform, driving unparalleled visibility into every customer interaction across all devices and delivering faster data-driven decisions. Built to automatically prioritize both technical and behavioral insights, the platform promotes enterprise digital transformation by empowering organizational Customer Experience (CX) alignment. Performance and security are the foundation of Quantum Metric, enabling customers to gain real-time user insights securely and at scale.
See the Tealium and Quantum Metric Partnership Overview for more information.
What to Expect From This Integration
The bi-directional integration between Tealium and Quantum Metric gives you deeper insights into how your key customer segments experience your digital products.
Prerequisites
Tealium:
iQ Tag Management (Required)
AudienceStream (Recommended) To achieve the most value out of the bi-directional integration.
Quantum Metric
Platform for Native or Web (Required)
Tag Configuration
To add and configure the Quantum Metric tag, you must first add and configure the tag from the Tealium tag marketplace. You will then enable Tealium AudienceStream to receive Quantum Metric Replay URLs.
Add and Configure the Tag in your Tealium Account
Add and configure the Quantum Metric tag from the Tealium tag marketplace:
Log in to your Tealium account.
Follow the steps to add a new tag from the tag marketplace. To find the Quantum Metric tag, type Quantum in the Vendor Name search field.
Select Quantum Metric and add that tag to your account.
In the Subscription Name field, enter the name provided by your Quantum Metric Client Service Manager.
Click Apply.
(Optional) Define Load Rules and Data Mappings.
Click Finish.
Save and publish your changes to the desired environments.
Enable AudienceStream
Before enabling Quantum Metric Replay URLs to be sent to AudienceStream, consult with your Quantum Metric Client Service Manager to determine desired target behaviors and experiences to send from Quantum Metric to Tealium.
Enable AudienceStream to receive data from Quantum Metric:
Go to your Quantum Metric tag in iQ Tag Management.
Expand the details and click Edit.
Set the Send Replay URL field to True.
Define the following fields:
Time Stamp
Tealium Account
Tealium Profile
Click Apply.
Save and publish your changes to the desired environments.
View in Live Events
Once the Quantum Metric tag is configured and sending Replay URLs to AudienceStream is enabled, you can view activity in the Live Events feed.
Use the following steps to view in Live Events:
In the Customer Data Hub left sidebar, click Event Stream > Live Events.
Scroll down to find the events from Quantum Metric by filtering for events containing the event attribute quantum_metric_replay_url or quantum_metric_user_id .
Use these event attributes to enrich the profile with other AudienceStream attributes.
... View more
01-27-2020
01:50 PM
1 Kudo
This article describes how to get the most out of Tealium and Invoca by setting up the Invoca tag in Tealium iQ Tag Management and then enabling the bi-directional integration in Tealium AudienceStream.
In this guide:
Table of Contents Placeholder
How it Works
Invoca helps marketers optimize for the most important step in the customer journey: the phone call. With the Invoca call and conversational analytics platform, marketers can:
Get granular campaign attribution to understand why customers are calling.
Gain real-time intelligence about who is calling and analyze what is being said in the conversations.
Put the data to work directly in the platform by automating an ideal customer experience before, during. and after each call.
See the Tealium + Invoca Technology Partnership Overview for more information.
What to Expect From This Integration
The bi-directional integration between Tealium and Invoca allows organizations to leverage valuable Invoca call interaction data – integrated with cross-channel customer profiles – to power more intelligent customer engagements and more accurate insights.
Prerequisites
Tealium
iQ Tag Management (Required)
AudienceStream (Recommended) To achieve the most value out of the bi-directional integration.
Invoca
Network-Level Account (Required) This integration is only available for network-level Invoca accounts
Tag Configuration
To add and configure the Invoca tag, you must first create an Invoca tag in your Invoca account. You will then add and configure the Invoca tag from the Tealium tag marketplace.
Create the Tag in your Invoca Account
Create an Invoca tag from your Invoca account:
Log in to your Invoca account.
Go to the Invoca tag wizard and follow the steps to create and deploy the tag in your Invoca account.
Add and Configure the Tag in your Tealium Account
To add and configure the Invoca tag in Tealium:
Log in to your Tealium account.
Follow the steps to add a new tag from the tag marketplace. To find the Invoca tag, type Invoca in the search field.
Find the InvocaJS Web Integration tag and click Add.
Deploy the Tag
Now that you have added and configured the tag, use the following steps to deploy the tag from your Invoca account:
Log in to your Invoca account.
Click the gear icon in the top right corner, and select Invoca Tags.
If you have more than one Invoca tag, click the Invoca Tags drop-down menu and select the tag that you want to add to your Tealium account.
Scroll down to the Code Snippets tile and copy your 4-digit network ID and unique Tag ID.
Return to Tealium and paste the 4-digit Network ID and unique Tag ID into the iQ Tag Management configuration page to complete the tag set up.
Apply load rules you would like to use for the Invoca tag.
The "All Pages" load rule is recommended.
Select the environments to which you want to deploy your Invoca tag.
Save and publish your changes. The Invoca Tag is now successfully implemented onto the enabled environments.
Send Data
To use this integration and to have the ability to send data, you must be able to create custom Marketing Data fields and custom webhooks in your Invoca account. The following sections describe the steps required to send Invoca data to Tealium AudienceStream and send Tealium AudienceStream data to Invoca.
Set up AudienceStream to Receive Invoca Data
To send Invoca data to AudienceStream:
Log in to your Invoca account.
Create a new Marketing Data field with the following settings:
Field type Short Text
Partner (API) Name tealium_vid
Friendly Name Tealium Visitor ID
Attribution Unique
Click the gear icon in the menu ribbon and select Invoca Tags. If you have more than one Invoca tag, use the tag selection drop-down menu to find the tags that you want to use with your Tealium integration and edit those tags.
Scroll down to the Marketing Data section of the Tag Wizard and locate the new “Tealium Visitor ID” Marketing Data field you just created.
Click the Enabled slider to enable the tag to collect data for that field.
Complete the data source type and name fields as follows: Tealium Visitor ID ( tealium_vid ):
Data Source Type JavaScript Data Layer
Data Source Name utag_data.tealium_visitor_id
Log in to your Tealium AudienceStream account and add a new Data Source. (Learn more)
Under Developer Languages, select the HTTP API Data Source.
Name the new Data Source “Invoca Post-Call Webhook”.
Skip the Event Specifications step and continue to the Get Code page.
Copy the Account, Profile, and Data Source Key shown on this page into a separate document — you will need these soon.
When finished, save and publish your new AudienceStream profile. Now your Tealium AudienceStream account is set up to receive Invoca data.
Create an Invoca Webhook to Send Data to AudienceStream
Next, you will create a new Invoca webhook that will send that data over to Tealium AudienceStream.
Create the Invoca webhook:
Return to your Invoca account.
Create a new rule-based signal with the following settings:
Name Tealium Visitor
Description Tealium Visitor ID ( tealium_vid ) is captured for this call.
Rules Click the Text tab and then paste custom_data[tealium_vid] present
Click Save.
Create a new custom webhook with the following settings:
Name Tealium AudienceStream POST
HTTP Verb POST
URL https://collect.tealiumiq.com/event
Click the Body tab of your webhook and select JSON.
Paste the following into the BODY text box below: Each line in the sample webhook body text copied represents a data parameter captured by Invoca that this webhook will send to AudienceStream.
{ “tealium_account” : “{Your Tealium Account Name}”, “tealium_profile” : “main”, “tealium_datasource” : “{Data Source Key}”, “tealium_event” : “InvocaPhoneCall”, “tealium_visitor_id” : “<tealium_vid>”, “connect_duration” : “<connect_duration>”, “advertiser_campaign_name” : “<advertiser_campaign_name>”, “advertiser_name” : “<advertiser_name>”, “unique_promo_number” : “<call_source_description>”, “media_type” : “<media_type>”, “phone_type” : “<mobile>”, “calling_phone_number” : “<calling_phone_number>”, “unique_promo_description” : “<promo_line_description>”, “call_start_time_utc” . : “<start_time_utc>”, “destination_phone_number” : “<destination_phone_number>”, “utm_campaign” : “<utm_campaign>”, “gclid” : “<gclid>”, “g_cid” : “<g_cid>”, “utm_source” : “<utm_source>”, “utm_medium” : “<utm_medium>”, “utm_content” : “<utm_content>”, “first_page” : “<firstPage>”, “last_page” : “<lastPage>” }
Use the following table to replace the fields from the sample above with information from your Tealium account:
Field from sample
Replace with
{Your Tealium Account Name}
The name of your Tealium account, assigned when your account was created. If you do not know your account name, you can find it by logging into Tealium — your account name displays at the top left corner of the window.
{Data Source Key}
The Data Source Key copied and saved from the previous section.
(Optional) You can delete any line of the sample body text to omit that data from your webhook or send additional data, such as custom Marketing Data fields or Signals you created.
To send additional data, return to the body text sample and press Enter to create a new line in your webhook.
Click the Add Substitution Parameter (<>) button and select the Invoca data parameter you want to send.
Complete the remainder of the webhook line in the following format: “parametername” : “<parametername>”
Click the Firing Conditions tab for your webhook, and complete in the following settings:
Fire On: Signal Select Tealium Visitor in the drop-down menu
Retry if first attempt fails: Yes
Fire for call corrections: No
How should batches be sent: Do not send batches
Click Save.
Locate your new webhook in your Custom Webhooks menu.
In the Actions menu, click the Settings button and select Activate. Your Invoca account is now set up to send your call data to AudienceStream.
You can now add Invoca call and conversion data to your visitor profiles within your Customer Data Platform (CDP) and throughout all of your marketing applications.
Send Tealium AudienceStream Data to Invoca
This section describes how to setup your Tealium account to send visitor profile data back to Invoca. From Invoca, you can then use the data to optimize your real-time call routing and caller experience.
Use the following steps to configure Tealium to inject data into the JavaScript data layer on your landing page so that the Invoca tag can pick it up.
Ensure that all previous steps in this guide are complete.
Log in to your iQ Tag Management account.
Navigate to your Invoca tag and then create a new Custom Data Mapping parameter for each parameter in your Tealium account that you want to send to Invoca.
You can send as many of these variables as you want to Invoca, limited only by the number of custom Marketing Data fields available in your Invoca account.
Go to Creating a Custom Data Mapping for detailed instructions.
Name the Destination of each Data Mapping according to the variable you selected. Example: invoca_leadscore for a lead score variable
When finished, record a list of each of your destination names in another document — you will need this information in the next steps.
Create Custom Marketing Data Fields in Invoca
Use the following steps to create custom marketing data fields in Invoca to enable the Invoca tag to pick up the data specified:
Return to your Invoca account use the following settings to create a new custom Marketing Data field for each data mapping you created.
Field type Short Text
Partner (API) Name: Choose a name that reflects the variable you selected in previous steps, such as tealium_leadscore .
Friendly Name Choose the "friendly name" that reflects the variable you selected in previous steps, such as Tealium Lead Score.
Attribution Last
Click the gear icon in the menu ribbon and, then select Invoca Tags.
If you have more than one Invoca tag, use the tag selection drop-down menu to find the tags that you want to use with your Tealium integration and edit those tags.
Scroll down to the Marketing Data section of the Tag Wizard and locate the new “Tealium Visitor ID” Marketing Data field you just created.
Click the Enabled slider to enable the tag to collect data for that field.
Complete the data source type and name fields as follows:
Data Source Type JavaScript Data Layer
Data Source Name localStorage.getItem("DESTINATION NAME")
Click Save.
Click Go Live. Your Invoca Tag will now capture any data from Tealium that you want in the Marketing Data fields you created.
You can now use your Marketing Data fields as part of a Real Time Routing Webhook, to build new rule-based signals, in your Call Treatment (IVR) options, or to pass along in other Invoca integrations.
Validate and Troubleshoot with EventStream
Using event specifications in Tealium EventStream you can view the following to validate and troubleshoot your Invoca for Tealium integration:
Live events
A record of your Invoca Tag firing
Data collected and transferred through this integration.
To create event specifications for your Invoca + Tealium integration:
Log in to your Tealium account and go to EventStream.
Go to your your Data Sources menu and scroll down to the Invoca Post-Call Webhook data source.
Click View in Live Events. to the right of the row.
From the Live Events menu, find and select an event sent by an Invoca Webhook. From here, you will be able to view all data sent to Tealium from one phone call.
Create a new event specification from this event. If you need help, see Event Specifications and follow the instructions outlined.
Title the event specification “InvocaPhoneCall”.
Uncheck the Required checkbox for all attributes. This event specification will primarily be used for troubleshooting purposes and to track the total volume of phone calls passing through Invoca.
Save and publish your changes to the appropriate environments.
... View more
01-23-2020
03:02 PM
1 Kudo
Happy New Year and welcome to 2020! You might have noticed a small change around here--we made an important update to the name of our platform, from the Universal Data Hub to the Customer Data Hub.
Customer Data Hub is now the name for the full suite of Tealium products:
Tealium iQ Tag Management
Tealium EventStream API Hub
Tealium AudienceStream
Tealium DataAccess
Tealium Predict Machine Learning
Does this affect the product capabilities?
No, the name change does not impact any of the current capabilities, product packaging or pricing of the Tealium services.
... View more
01-14-2020
09:27 AM
This article describes how to set up the Facebook Audiences - Beta connector in your Customer Data Hub account.
The Beta version of this connector is currently available as an Experiment. (Learn more)
In this article:
Table of Contents Placeholder
Connector Actions
Action Name
AudienceStream
EventStream
Add User to Custom Audience
✓
✗
Remove User from Custom Audience
✓
✗
Opt Out User from All Custom Audiences
✓
✗
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
The Facebook Ads Account ID you want to manage.
Before you can use this connector and build a custom audience in Facebook, you must agree to the Facebook Custom Audience Terms.
How do I find the ID number for my ad account?
This connection generally expires within 60 days, which causes all Facebook Ad actions to behave unpredictably. You can re-establish the connection at any point by clicking the Establish Connection/Connected button.
Before you click the Establish Connection button, you must first ensure that you are signed into Facebook with the account that is linked to the Ad Account ID being used, otherwise issues may arise with the token that is generated. .
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
Phone Number
Gender
Year of birth
Month of birth
Day of birth
Last Name
First Name
First Initial
City
US State
Zip Code
Country
Facebook User ID
Facebook App ID
Mobile Advertiser ID
External ID
Lookalike Value
Check this box if the Target User Identifier is already hashed
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
Phone Number
Gender
Year of birth
Month of birth
Day of birth
Last Name
First Name
First Initial
City
US State
Zip Code
Country
Facebook User ID
Facebook App ID
Mobile Advertiser ID
External ID
Lookalike Value
Check this box if the Target User Identifier is already hashed
Action - Opt Out User from All Custom Audiences
Parameters
Parameter
Description
Email Address
Phone Number
Gender
Year of birth
Month of birth
Day of birth
Last Name
First Name
First Initial
City
US State
Zip Code
Country
Facebook User ID
Facebook App ID
Mobile Advertiser ID
External ID
Lookalike Value
Check this box if the Target User Identifier is already hashed
... View more
01-13-2020
10:43 AM
5 Kudos
This article serves as a notification of an upcoming change to Google Chrome that could potentially affect the behavior of your Tealium implementation.
What is changing in Chrome?
Starting in February, 2020 the release of Google Chrome 80 introduces a new default value for the SameSite cookie attribute that affects its behavior in cross-domain scenarios. The current default value is SameSite=None , which implies that the cookie be available in third-party contexts. With the release of Chrome 80, the default value will be SameSite=Lax , which implies that the cookie not be available in third-party contexts. Third-party cookie requests that do not set SameSite=None (and thus default to SameSite=Lax ) will be rejected.
Also, when the value is set to SameSite=None , the cookie must be tagged with a secure attribute to indicate it requires an encrypted HTTPS connection. Cookie requests with the attribute value of SameSite=None that are not marked secure will be rejected.
Learn more about Google's Chrome update: Cookies default to SameSite:Lax
Why is this important?
Cookies with the SameSite=None attribute are marked for use in third-party contexts that are typically used for tracking and can contain sensitive data about the identity of a user. This change is important to increase web privacy and security by limiting the amount of personal data shared across domains and to encourage adoption of HTTPS and first-party data.
Using non-secure cookies can facilitate pervasive monitoring and potential attacks on user privacy. This change mitigates this risk by restricting the use of non-secure third-party cookies. By requiring SameSite=None cookies to be secure, users are protected by default from attacks on data that can personally identify them and potentially compromise privacy.
Any service that sets a server-side third-party cookie must make an update to accommodate the new default behavior from Chrome 80, otherwise their cookies will be rejected.
What is Tealium doing in response?
Tealium has made the following changes to ensure that cookies continue to perform as expected after the Chrome 80 release:
Server-side cookies set by the Tealium Collect service, the View-Through Tracking extension, and Cookie Matching tags will be set to secure and use the SameSite=None attribute.
The Tealium Collect tag used in iQ Tag Management has been updated to force the use of HTTPS for custom server endpoints in cases where no protocol is specified in the custom endpoint URL.
Tealium additionally sets a server-side TAPID cookie with a unique identifier that is used for specific items, such as cross-domain visitor stitching.
Cookies set by the Universal Tag (utag.js) are not affected because they are set in a first-party context.
What do I need to do?
Review the following scenarios and actions to see if you are affected:
Scenario
Action
You use the Tealium Collect tag in your iQ Tag Management configuration and use a custom server endpoint (instead of the default Tealium endpoint).
Ensure your custom server endpoint is set to use https:// . For more information, see: Tealium Collect Tag Setup Guide
You use the Tealium Collect tag on a site that mixes HTTP pages with HTTPS pages.
Update to the latest version of the Tealium Collect tag to ensure all requests will use https:// . For more information, see: Updating a Tag
You use older tag templates that leverage the visitor stitching feature
Older tag templates may use HTTP instead of HTTPS, which cannot be verified as secure. The tags that use HTTP do not set a third-party cookie, which makes all visitors seem to be unique visitors. Also, in rare instances, the relative path can prevent third party cookies from not being set and can potentially create issues with visitor stitching.
Due to modern browser requirements and the need for strong security enforcement, the visitor stitching feature is only available for HTTPS data collection, which is the Tealium default.
Recommendations:
Update all websites to use the most current tag templates, which uses HTTPS as the default configuration.
Use HTTPS in all cases where you currently use or may use the visitor stitching feature.
You use a custom name (CNAME) that was originally set to SameSite=Lax or SameSite=Strict .
No action required. Tealium sets SameSite=None for all instances.
... View more
01-02-2020
02:12 PM
1 Kudo
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: Rtoaster (Learn more)
New marketplace tag: ShopMessage (Learn more)
Added the Viewthrough Tracking option to the Adobe Analytics AppMeasurement for JS tag. (Learn more)
Updated the library version for the Dun & Bradstreet tag. (Learn more)
Update mapped variable handling for the Kenshoo tag. (Learn more)
Updated order total handling for the Dynamic Yield tag. (Learn more)
Updated parameters for the Adform tag. (Learn more)
Connectors
New/Cool Stuff
New marketplace connector: Adobe Campaign Classic Batch (Learn more)
New marketplace connector: Facebook Audiences - Beta (Learn more)
New marketplace connector: Optimizely Events - Beta (Learn more)
New marketplace connector: Tapjoy Conversion Postbacks - Beta (Learn more)
Updated the Criteo connector to ensure the first item in a list is passed correctly and that additional items follow, in the correct format. (Learn more)
EventStream, AudienceStream, and DataAccess
New/Cool Stuff
Introduced the new Server-Side user permissions management feature. (Learn more)
Fixes
Added Event Feeds to global warning messages to ensure that deleted TiQ-imported attributes can be identified, saved, published, and disabled.
Installations
New/Cool Stuff
Braze iOS 0.0.5/Android 0.0.3
Added new configuration options and variables.
Added setlocation command for location and geofencing support.
iOS 5.6.5
Added tealium_session_id to volatile data sources for Xamarin.
Swift 1.8.0, 1.81
Added new device_type variable to capture internal device identifier.
Added option to disable event batching.
Added optional Visitor Service module (required AudienceStream CDP) to retrieve visitor profile changes in real-time.
Moved Persistent Storage from UserDefaults to JSON-based file storage.
Removed the following modules:
FileStorage (superseded by DiskStorage, part of Core)
DefaultsStorage (superseded by DiskStorage, part of Core)
DataSource (incorporated into VolatileData module)
Updated event batching to send up to 10 events in a single UDH "hit".
Xamarin 1.01
Updated lifecycle.dll files to correct issues with Lifecycle modules.
Fixes
Android 5.6.0, 5.6.1
Corrected encoding issue for event data sent using POST method.
Added methods to the Tealium.Config class to correctly override the Visitor service domain and profile.
Swift 1.8.0, 1.81
Corrected issue causing occasional Tag Management module issues.
... View more
12-12-2019
04:39 PM
This article describes how to set up the ShopMessage tag in your Tealium iQ Tag Management (TiQ) account.
In this article:
Table of Contents Placeholder
Tag Tips
The PurchaseComplete Event fires when an Order ID is present.
Use mapping to:
Dynamically override the standard config values
Configure event triggers
Send required, optional, and custom event parameters
Override the E-Commerce extension values
Use "Custom Product Variable Name" for any Product variables not listed by replacing "custom" with the variable you want to send
Supports these E-commerce extension parameters:
Order ID
Order Total
Order Subtotal
Shipping Amount
Tax Amount
Currency
Customer ID
Customer City
Customer State
Customer Zip
Customer Country
List of Product IDs
List of Names
List of SKUs
List of Categories
List of Quantities
List of Prices
Implementation Guide: https://help.shopmessage.me/en/articles/1443137-integrating-shopmessage-with-your-store
Tag Configuration
First, go to Tealium's tag marketplace and add the ShopMessage tag (Learn more about how to add a tag).
After adding the tag, configure the following settings:
Account ID: An alphanumerical value found in the src URL
c_id: An alphanumerical value found after "initialize.js?c=" in the src URL
Facebook Login:
Facebook Optin:
Data Mappings
Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see Data Mappings.
The available categories are:
Standard
Variable
Description
Account ID
(account_id)
c_id
(c_id)
Facebook Login (fb_login)
[true/false]
Facebook Optin (fb_optin)
[true/false]
E-Commerce
Variable
Description
Order ID
(order_id) (Overrides _corder)
Order Total
(order_total) (Overrides _ctotal)
Order Subtotal
(order_subtotal) (Overrides _csubtotal)
Shipping Amount
(order_shipping) (Overrides _cship)
Tax Amount
(order_tax) (Overrides _ctax)
Currency
(order_currency) (Overrides _ccurrency)
Customer ID
(customer_id) (Overrides _ccustid)
Customer City
(customer_city) (Overrides _ccity)
Customer State
(customer_state) (Overrides _cstate)
Customer Zip
(customer_zip) (Overrides _czip)
Customer Country
(customer_country) (Overrides _ccountry)
List of Product IDs (product_id) (Overrides _cprod)
[Array]
List of Names (product_name) (Overrides _cprodname)
[Array]
List of SKUs (product_sku) (Overrides _csku)
[Array]
List of Categories (product_category) (Overrides _ccat)
[Array]
List of Quantities (product_quantity) (Overrides _cquan)
[Array]
List of Prices (product_unit_price) (Overrides _cprice)
[Array]
Event Triggers
Variable
Description
ViewProduct
ViewProduct
UpdateCart
UpdateCart
PurchaseComplete
PurchaseComplete
Event Data: ViewProduct
Variable
Description
Title
(ViewProduct.title) (Overrides E-Commerce Product Name)
Price
(ViewProduct.price) (Overrides E-Commerce Product Unit Price)
Product ID
(ViewProduct.product_id) (Overrides E-Commerce Product ID)
Product Type
(ViewProduct.product_type) (Overrides E-Commerce Product Category)
Color
(ViewProduct.color)
Style
(ViewProduct.style)
Image
(ViewProduct.image)
Product URL
(ViewProduct.product_url)
Tags
(ViewProduct.tags)
Vendor
(ViewProduct.vendor)
Event Data: UpdateCart
Variable
Description
Total Price
(UpdateCart.total_price) (Overrides E-Commerce Order Total)
CTA URL
(UpdateCart.cta_url)
Product Title (UpdateCart.items.title) (Overrides E-Commerce Product Name)
[Array]
Product Price (UpdateCart.items.price) (Overrides E-Commerce Product Unit Price)
[Array]
Product Currency (UpdateCart.items.currency) (Overrides E-Commerce Currency)
[Array]
Product ID (UpdateCart.items.product_id) (Overrides E-Commerce Product ID)
[Array]
Variant ID (UpdateCart.items.variant_id)
[Array]
Product SKU (UpdateCart.items.sku)
[Array]
Product Size (UpdateCart.items.size)
[Array]
Product Color (UpdateCart.items.color)
[Array]
Product Image (UpdateCart.items.image)
[Array]
Product URL (UpdateCart.items.product_url)
[Array]
Product Quantity (UpdateCart.items.quantity) (Overrides E-Commerce Product Quantity)
[Array]
Product Tags UupdateCart.items.tags)
[Array]
Custom Product Variable Name (UpdateCart.items.custom)
[Array]
Event Data: PurchaseComplete
Variable
Description
Order ID
(PurchaseComplete.order_id) (Overrides E-Commerce Order ID)
Checkout Token
(PurchaseComplete.checkout_token)
Created at
(PurchaseComplete.created_at)
Order Status URL
(PurchaseComplete.order_status_url)
Currency
(PurchaseComplete.currency) (Overrides E-Commerce Currency)
Total Price
(PurchaseComplete.total_price) (Overrides E-Commerce Order Total)
Subtotal Price
(PurchaseComplete.subtotal_price) (Overrides E-Commerce Order Subtotal)
Total Tax
(PurchaseComplete.total_tax) (Overrides E-Commerce Tax Amount)
Shipping Price
(PurchaseComplete.shipping_price) (Overrides E-Commerce Shipping Amount)
Platform
(PurchaseComplete.platform)
Address 1
(PurchaseComplete.shipping_address.address1)
Address 2
(PurchaseComplete.shipping_address.address2)
First Name
(PurchaseComplete.shipping_address.first_name)
Last Name
(PurchaseComplete.shipping_address.last_name)
Full Name
(PurchaseComplete.shipping_address.full_name)
City
(PurchaseComplete.shipping_address.city) (Overrides E-Commerce Customer City)
State
(PurchaseComplete.shipping_address.state) (Overrides E-Commerce Customer State)
Zip Code
(PurchaseComplete.shipping_address.zip) (Overrides E-Commerce Customer Zip)
Phone Number
(PurchaseComplete.shipping_address.phone)
Product Title (PurchaseComplete.items.title) (Overrides E-Commerce Product Name)
[Array]
Product Price (PurchaseComplete.items.price) (Overrides E-Commerce Product Unit Price)
[Array]
Product ID (PurchaseComplete.items.product_id) (Overrides E-Commerce Product ID)
[Array]
Variant ID (PurchaseComplete.items.variant_id)
[Array]
Product SKU (PurchaseComplete.items.sku) (Overrides E-Comemrce Product SKU)
[Array]
Product Size (PurchaseComplete.items.size)
[Array]
Product Color (PurchaseComplete.items.color)
[Array]
Product Image (PurchaseComplete.items.image)
[Array]
Product URL (PurchaseComplete.items.product_url)
[Array]
Product Quantity (PurchaseComplete.items.quantity) (Overrides E-Commerce Product Quantity)
[Array]
Product Tags (PurchaseComplete.items.tags)
[Array]
Custom Product Variable Name (PurchaseComplete.items.custom)
[Array]
Customer Email
(PurchaseComplete.customer_properties.email)
Customer ID
(PurchaseComplete.customer_properties.id) (Overrides E-Commerce Customer ID)
Customer First Name
(PurchaseComplete.customer_properties.first_name)
Customer Last Name
(PurchaseComplete.customer_properties.last_name)
Visitor Parameters
Variable
Description
Customer ID
(visitor.customer_id) (Overrides E-Commerce Customer ID)
Address 1
(visitor.address1)
Address 2
(visitor.address2)
First Name
(visitor.first_name)
Last Name
(visitor.last_name)
Full Name
(visitor.full_name)
Gender
(visitor.gender)
Language
(visitor.language)
City
(visitor.city) (Overrides E-Commerce Customer City)
State
(visitor.state) (Overrides E-Commerce Customer State)
Zip Code
(visitor.zip) (Overrides E-Commerce Customer Zip)
Phone Number
(visitor.phone)
Profile Picture
(visitor.profile_pic)
... View more
12-12-2019
04:25 PM
This article describes how to set up the Rtoaster tag in your Tealium iQ Tag Management (TiQ) account.
In this article:
Table of Contents Placeholder
Tag Tips
You can configure more than one element ID by entering the IDs as a comma-separated list.
Use mappings to override standard config values.
Tag Configuration
First, go to Tealium's tag marketplace and add the Rtoaster tag (Learn more about how to add a tag).
After adding the tag, configure the following settings:
Account ID
Your Rtoaster Account ID.
Recommendation Element ID
The IDs of the elements targeted by the Rtoaster recommendation.
You can enter more than one ID in a comma-separated list.
Popup Element ID
The ID of the element targeted by the Rtoaster popup recommendation.
Data Mappings
Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see Data Mappings.
The available categories are:
Standard
Variable
Description
account_id
String
Account ID
element_id
String, Array
Element ID
popup_element_id
String
Popup Element ID
category
String, Array
Category
price_min
String, Number
Price Minimum
price_max
String, Number
Price Maximum
E-Commerce
Variable
Description
order_subtotal
Subtotal
Overrides _csubtotal .
order_shipping
Shipping amount.
Overrides _cship .
customer_id
Customer ID
Overrides _ccustid .
product_id
Array
List of Product IDs.
Overrides _cprod
product_quantity
Array
List of Quantities.
Overrides _cquan
product_unit_price
Array
List of Prices
Overrides _cprice .
... View more
12-04-2019
01:31 PM
This article describes how to set up the Dun & Bradstreet Web Visitor ID tag in your Tealium iQ Tag Management (TiQ) account.
In this article:
Table of Contents Placeholder
Tag Tips
Use mapping to dynamically override standard configuration values.
Use the JavaScript Code extension to set returned data.
Example:
window.tealium_dnbwvid = function(dnb_Data) { // Set data here, ex: visitor_duns = dnb_Data.duns; }
Tag Configuration
First, go to Tealium's tag marketplace and add the D&B Web Visitor ID tag (Learn more about how to add a tag).
After adding the tag, configure the following settings:
API Key
Your API key supplied by Dun and Bradstreet.
Example: //API_KEY_HERE.d41.co/sync/
Data Key
API Key supplied in the getData call
Leave blank to use the API Key.
Example: dnbvid.getData('DATA_KEY_HERE','json','T'...
Data Mappings
Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see Data Mappings.
The available categories are:
Standard
Variable
Description
api_key
API Key
data_key
Data Key
... View more
12-03-2019
01:46 PM
This article describes how to set up the Quicklizard tag in your Tealium iQ Tag Management (TiQ) account.
In this article:
Table of Contents Placeholder
Tag Tips
Required mappings:
List of Product IDs
List of Prices
Supports the following E-Commerce extension values:
Order ID
List of Product IDs
List of Names
List of Brands
List of Categories
List of Prices
Tag Configuration
First, go to Tealium's tag marketplace and add the Quicklizard tag (Learn more about how to add a tag).
After adding the tag, configure the following settings:
Client Key The key supplied by Quicklizard.
Data Mappings
Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see Data Mappings.
The available categories are:
Custom
Variable
Description
Custom
Add custom destination
... View more
12-03-2019
01:33 PM
This article describes how to set up the iSpot TV Cooke Matching Service tag in your Tealium iQ Tag Management (TiQ) account.
In this article:
Table of Contents Placeholder
Tag Tips
This tag will only trigger once per session, assuming it successfully retrieves the iSpot ID.
If left blank, Tealium Account and Tealium Profile will be automatically populated with your current Tealium iQ account and profile.
The cookie matching call sends the following parameters:
tealium_cookie_sync : true
tealium_account : Your Tealium account
tealium_profile : Your Tealium profile
tealium_visitor_id : The visitor's Tealium ID
tealium_event : cookie_match_ispot
ispot_id : The visitor's iSpot ID
tealium_datasource : The Tealium data source ID, if set
tealium_trace_id : The Tealium Trace ID, if set
Tag Configuration
First, go to Tealium's tag marketplace and add the iSpot TV Cooke Matching Service tag (Learn more about how to add a tag).
After adding the tag, configure the following settings:
Site ID: Your iSpot-provided Site ID
Tealium Account: (Optional) Your Tealium account
Tealium Profile: (Optional) Your Tealium profile
Tealium Data Source ID: (Optional) Your Tealium Data Source ID
Data Mappings
Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see Data Mappings.
The available categories are:
Standard
Variable
Description
Site ID
(site_id)
Tealium Account
(tealium_account)
Tealium Profile
(tealium_profile)
Tealium Data Source ID
(tealium_datasource)
... View more
12-03-2019
01:23 PM
This article describes how to set up the Adobe Audience Manager tag in your Tealium iQ Tag Management (TiQ) account.
In this article:
Table of Contents Placeholder
Tag Tips
Select "On" under "Use E-Commerce Variables" to add the Order and Customer E-Commerce data to the "c_" data
Use the "Custom c_ Object" mapping to send your own object or additional objects with "c_" data
Current Library Version: 9.3
Tag Configuration
First, go to Tealium's tag marketplace and add the Adobe Audience Manager tag (Learn more about how to add a tag).
After adding the tag, configure the following settings:
Visitor Service Namespace: This is the same as your Adobe Org ID/Experience Cloud ID
Partner Name: Provided by Audience Management
Use E-Commerce Variables:
Data Mappings
Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see Data Mappings.
The available categories are:
Standard
Variable
Description
Visitor Service Namespace
(namespace)
Partner Name
(partner)
Use E-Commerce Variables
(use_ecommerce)
Container ID
(containerNSID)
Data Partner ID
(declaredId.dpid)
Unique User ID
(declaredId.dpuuid)
Defer Requests Until Page Load (delayAllUntilWindowLoad)
[Boolean]
Disable UUID Cookie (disableDeclaredUUIDCookie)
[Boolean]
Prevent Destination Publishing IFRAME (disableDestinationPublishingIframe)
[Boolean]
Disable ID Synchronization (disableIDSyncs)
[Boolean]
Enable Error Reporting (enableErrorReporting)
[Boolean]
Enable Logging (enableLogging)
[Boolean]
Enable URL Destinations (enableUrlDestinations)
[Boolean]
Enable Cookie Destinations (enableCookieDestinations)
[Boolean]
Enable Akamai for HTTPS (iframeAkamaiHTTPS)
[Boolean]
Remove Finished Scripts and Callbacks (emoveFinishedScriptsAndCallbacks)
[Boolean]
Key Mappings Object (mappings)
[Object]
Cookie Name
(uuidCookie.name)
Cookie Lifetime in Days
(uuidCookie.days)
Cookie Path
(uuidCookie.path)
Cookie Domain
(uuidCookie.domain)
Send Over HTTPS (uuidCookie.secure)
[Boolean]
Basic c_ Variables
Variable
Description
Ad ID
(c.ad_id)
Content Author
(c.content_author)
Content Title
(c.content_title)
Content Publish Date
(c.content_publish_date)
Category ID
(c.category_id)
Category Name
(c.category_name)
Page Name
(c.page_name)
Page Number
(c.page_number)
Previous Page Name
(c.previous_page_name)
Search Category
(c.search_category)
Search Keyword
(c.search_keyword)
Search Results
(c.search_results)
Site Section
(c.site_section)
Sort By
(c.sort_by)
Sort Order
(c.sort_order)
Custom c_ Variable
(c.custom)
Custom c_ Object
(cobject.custom)
Basic d_ Variables
Variable
Description
Caller
(d.caller)
Javascript Callback Function
(d.cb)
Data Provider ID
(s) (d.cid)
Integration Code and User ID
(d.cid_ic)
Trait and Segment Return Type
(d.cts)
Return URL Destination
(d.dst)
JSON Return Version
(d.jsonv)
Name Space ID
(d.nsid)
Return JSON
(d.rtbd)
Score ID
(d.sid)
Trait Data Source
(d.tdpid)
Trait Data Source via Integration Code
(d.tdpid_ic)
Unique User ID
(d.uuid)
Custom _d Variable
(d.custom)
Custom h_ and p_ Variables
Variable
Description
Custom _h Variable
(h.custom)
Custom _p Variable
(p.custom)
E-Commerce
Variable
Description
Order ID
(order_id) (Overrides _corder)
Order Total
(order_total) (Overrides _ctotal)
Sub Total
(order_subtotal) (Overrides _csubtotal)
Shipping Amount
(order_shipping) (Overrides _cship)
Tax Amount
(order_tax) (Overrides _ctax)
Store
(order_store) (Overrides _cstore)
Currency
(order_currency) (Overrides _ccurrency)
Promo Code
(order_coupon_code) (Overrides _cpromo)
Cart or Order Type
(order_type) (Overrides _ctype)
... View more
12-02-2019
02:27 PM
This article describes how to set up the Dynamic Yield tag in your Tealium iQ Tag Management (TiQ) account.
In this article:
Table of Contents Placeholder
Tag Tips
You can set the name and properties.
Type parameters of a custom event via mappings in the Custom Event Data tab in the mappings toolbox.
Conversion fires when Order ID is set.
Supports the following E-Commerce extension parameters:
Order ID ( _corder )
Order Total ( _ctotal )
Sub Total ( _csubtotal )
Currency ( _ccurrency )
List of Product IDs ( _cprod )
List of Names _cprodname )
List of Quantities ( _cquan )
List of Prices ( _cprice )
Tag Configuration
First, go to Tealium's tag marketplace and add the Dynamic Yield tag (Learn more about how to add a tag).
After adding the tag, configure the following settings:
Site ID: Your Dynamic Yield supplied Site ID or scsec
Data Mappings
Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see Data Mappings.
The available categories are:
Standard
Variable
Description
SiteID
(scsec)
evt_list
CSV/Array
List of Events to fire
context.type
Context type
context.data
Array
Context Data
E-Commerce
Variable
Description
order_id
Order ID
Overrides _corder .
order_total
Order total
Overrides _ctotal .
order_subtotal
Subtotal
Overrides _csubtotal .
order_currency
Currency
Overrides _ccurrency .
product_id
Array
List of Product IDs.
Overrides _cprod .
product_name
Array
List of Names.
Overrides _cprodname .
product_quantity
Array
List of Quantities.
Overrides _cquan .
product_unit_price
Array
List of Prices.
Overrides _cprice .
Events
Variable
Description
AddToCart
AddToCart
RemoveFromCart
RemoveFromCart
Search
Search
EmailSignup
EmailSignup
VideoWatch
VideoWatch
Custom
Custom
Parameters
Variable
Description
Size (size)
properties.size
Search Keywords (keywords)
properties.keywords
Hashed Email (hashedEmail)
properties.hashedEmail
Custom
Custom
Video Parameters
Variable
Description
Item Id
properties.itemId
Categories (categories)
properties.categories
Autoplay (autoplay) [true/false]
properties.autoplay
Progress (progress)
properties.progress
Progress Percent (progressPercent)
properties.progressPercent
Custom
Custom
... View more
12-02-2019
11:08 AM
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: Genesys Chat Widget (Learn more)
New marketplace tag: iSpotTV Cookie Matching Service (Learn more)
Added "allowAdFeatures" field for display advertising features to the Google Analytics tag (gtag.js and analytics.js). (Learn more)
Added customEvent support to the Sailthru Personalization Engine tag. (Learn more)
Improved plug-in support for the the Webtrekk tag and added support for versions 4.4.7 and 5.1.1. (Learn more)
Removed the AdRoll tag from the tag marketplace (this tag can only be used if previously installed).
Updated the Adobe Analytics AppMeasurement tag for clearvars to use callback and always fire after Track call. (Learn more)
Updated the Adobe Audience Manager tag library to version 9.3 and added new mappings. (Learn more)
Updated the Adobe Target tag to support Version 1.8 and 2.2. (Learn more)
Updated the configuration fields for the Facebook Buttons tag. (Learn more)
Updated the Google Ads Conversion and Remarketing tag (gtag.js) to make Conversion ID a required field. (Learn more)
Updated the handling of the PID for different event types for the Pepperjam tag. (Learn more)
Updated the JavaScript library version for the Amplitude tag. (Learn more)
Updated the Quicklizard tag to the latest SDK version. (Learn more)
Updated the Yext tag configuration options and data mappings. (Learn more)
Fixes
Added a check for the existence of an Advertiser ID for the Floodlight (gtag.js) tag before converting it to an array. (Learn more)
Corrected parameter name display for the Firebase Mobile Remote Command tag. (Learn more)
Connectors
New/Cool Stuff
Applied performance enhancements to the Adobe Analytics connector. (Learn more)
Updated the Amplitude connector to add support API, v4. (Learn more)
Updated the Facebook Ads connector to support the Facebook Marketing API, v4. (Learn more)
Updated AppNexus branding name for all articles and logo images in interface to "Xandr". (Learn more)
Added batch actions and updated existing actions for the ExactTarget (formerly Salesforce) connector. (Learn more)
Fixes
Corrected automatic connector configuration field population issue with the Webhook connector .
iQ Tag Management
Fixes
Corrected issue causing the Edit button to be inaccessible when the mapped variable Note field contains a long note with no spaces.
Corrected issue causing erroneous message to display when searching for and selecting the jQuery clickHandler extension or the jQuery onHandler extension.
EventStream, AudienceStream, and DataAccess
Fixes
Added Event Feeds to global warning messages to ensure that deleted TiQ-imported attributes can be identified, saved, published, and disabled.
Applied performance enhancements for the Visitor Lookup API response time.
Corrected issue causing header table text wrapping to only display half of the second line when viewing the screen at half width.
Updated the Live Events Timeline graph to correctly display the entire timeline for smaller screen resolutions.
Updated functionality for the Live Events Quick Add button to only allow valid attribute names.
Updated the Visitor Lookup API error messaging to display a more meaningful description when a "5xx" error is returned.
... View more
11-25-2019
02:47 PM
This article describes how to set up the The Trade Desk (theTradeDesk) Offline Conversion connector in your Customer Data Hub account.
Table of Contents Placeholder
Connector Actions
Action Name
AudienceStream
EventStream
Send Offline Conversion
✓
✓
Configure Settings
Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector.
After adding the connector, configure the following settings:
Partner/Agency Secret Key Secret Key provided to you by theTradeDesk
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 Offline Conversion
Parameters
Parameter
Description
Data Provider ID
The ID for the data provider in the TTD System.
TDID
The Trade Desk ID for the user.
Required if DAID is blank.
You must use TDID or DAID.
DAID
The Device Advertising ID for the user.
Required if TDID is blank.
iOS IDFA or Android Advertising ID.
You must use TDID or DAID.
Tracking Tag ID
Required
The Tracking Tag ID created using the Tracking tag APIs.
Example: xy4s8ef
Conversion Timestamp
Required
Conversion Date TIme in UTC.
The time the offline conversion happened, in UTC.
Example: 2019-02-07T13:25:00Z
ImpressionId
Valid 36 characters.
Globally Unique Identifier (GUID) for the Impression this item is for.
Value
Monetary value.
Example: 0.02
ValueCurrency
Monetary value currency.
Example: USD
Country
Country
Example: United States
Region
Region
Example: New York
Metro
Metro Area
Example: 501
City
City
Example: Brooklyn
PostalCode
Postal Code
Example: 11223
TD1
Optional reporting field.
Can be used for user category or flags.
TD2
Optional reporting field.
Can be used for user category or flags.
TD3
Optional reporting field.
Can be used for user category or flags.
TD4
Optional reporting field.
Can be used for user category or flags.
TD5
Optional reporting field.
Can be used for user category or flags.
TD6
Optional reporting field.
Can be used for user category or flags.
TD7
Optional reporting field.
Can be used for user category or flags.
TD8
Optional reporting field.
Can be used for user category or flags.
TD9
Optional reporting field.
Can be used for user category or flags.
TD10
Optional reporting field.
Can be used for user category or flags.
... View more
11-22-2019
12:44 PM
This article describes how to set up the Amplitude connector in your Customer Data Hub account.
In this article:
Table of Contents Placeholder
Connector Actions
Action Name
AudienceStream
EventStream
Send Event
✓
✓
Configure Settings
Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector.
After adding the connector, configure the following settings:
API Key Located under Settings > Projects.
Action Settings - Parameters and Options
Click Next or go to the Actions tab. This is where you configure connector actions.
This section describes how to set up parameters and options for each action.
Action - Send Event
Parameters
Parameter
Description
Event Properties
Optional.
A dictionary of key-value pairs that represent additional data to be sent along with the event.
User Properties
Optional.
A dictionary of key-value pairs that represent additional data tied to the user.
Each distinct value display as a user segment on the Amplitude dashboard.
Groups
Optional.
Enterprise only.
A dictionary of key-value pairs that represent groups of users.
For more information on groups, see the following JavaScript SDK excerpt .
... View more
Public Statistics
| Date Registered | 09-25-2017 12:25 PM |
| Date Last Visited | Friday |
| Total Messages Posted | 254 |
| Total Kudos Received | 35 |
Kudos given to
Kudos from
Latest Tags
No tags yet
-
Products
- Tealium iQ Tag Management
- Tealium EventStream
- Tealium AudienceStream
- Tealium DataAccess
- Tealium for Mobile
-
Company
- Tealium.com
- Blog
- Careers
- Contact Us
- Events
Copyright All Rights Reserved © 2008-2020