![](\"/images/industries/screen-shot-2022-09-26-at-13.41.19.png\")
\n \nTealium relies on deterministic information sources to use PII to stitch visitor data together into a visitor profile for a single customer view. However, you can use identity providers of first-party and third-party data, which often rely on probabilistic methods of identity resolution, to create high-quality insights about each visitor, prospect and customer. These probabilistic insights can be combined with data collected and profiles enriched by Tealium to enhance relationship data and provide personalized experiences to customers.
\nTealium’s Identity Partners provide the following services:
\nTealium provides access to a large number of identity partner integrations across the platform: iQ Tag Management, EventStream, Data Source, AudienceStream, and Functions. Because it can be a lot of work pulling information from each of these sources and combining it into a clear vision of your visitor and customer profile, Tealium is here to make the process of integrating identity provider data from multiple sources smoother and easier.
\nIt is important to understand the difference between deterministic matching and probabailistic data models:
\nThe deterministic method uses PII (email, UID2.0, etc.) to identify the user. Tealium employs the deterministic model with visitor stitching.
\nIntegrations with probabilistic identity programs typically require the use of Tealium’s functions to process returned data along with the confidence score.
\nAuth0 uses the Customer Identity Access Management (CIAM) model:
\n\n \nWhen the user logs in to Auth0, their identity is confirmed by the Auth0 authorization server.
\nTealium appears as an Auth0 action, which can be used through drag and drop integration.
\nThe Auth0 data source appears under the new Identity category in Tealium.
\nThe Trade Desk and other vendors use UID 2.0, which uses PII for deterministic identification. You will need to configure an enrichment and function code to assign a UID 2.0 to a visitor:
\n![](\"/images/industries/screen-shot-2022-09-26-at-13.41.53.png\")
\n \nFor more information, see Using Tealium Functions to Generate a UID2.0 Token.
\nUID 2.0 cannot be used in the EU due to privacy restrictions.
\nAs identity and data management solution providers, Acxiom and Merkle perform the following roles:
\n![](\"/images/industries/data-partners-+-tealium---acxiom-%283%29.png\")
\n \nAfter login or registration with a netID on a website, the user’s netID identity parameter is available to Tealium’s real-time data collection, enrichment, and activation capabilities.
\nWhen the user logs in on a website with netID authentication, their identity is confirmed by the netID authentication API. The identity parameter tpid from the API READ SERVICE response can be persisted in the Tealium data layer.
You can use an identity provider to immediately share PII such as phone numbers and email addresses with Tealium to enrich customer profiles. This lets you turn anonymous visitors into known visitors or customers.
\nBecause data providers constantly clean and normalize their data, you can use this information to help clean your own data.
\nAs third party cookies are deprecated, anonymous retargeting will no longer be possible. So sharing one or more pieces of PII with AdTech ID partners allows identification and targeting of that individual across publishers and domains.
\nMany customers have already hired third-party identity providers to improve their visitor profiles. The Tealium Identity Marketplace can help simplify the process of subscribing to, importing, and incorporating this data.
\nThe Identity category in each of the Tags, Connectors, and Data Sources interfaces lists all of the available identifier resources for that part of the platform.
\n| Partner | \nIntegration Type | \nSummary | \nDocumentation Link | \n
|---|---|---|---|
| Acxiom | \nTag | \n
| \nAcxiom Real Identity rTag Setup Guide | \n
| Auth0 | \nData Source | \nAn action within the Auth0 integration market that sends user data from Auth0 upon login | \nTealium Integrations at Auth0 | \n
| Merkle | \nTag | \nMerkury uses an organization’s first-party CRM data and valuable interactions such as logins, outbound email campaigns and media reach to create and grow a universe of person-based IDs. Tealium IQ’s data mapping feature lets you control which data points are shared with Merkury. | \nMerkle Merkury Tag Setup Guide | \n
| netID | \nData Layer (UDO object) | \nTo implement the netID Login Standard, netID partners implement the netID browser-based Javascript API request on their website, and persist netID identity and privacy properties in browser storage, such as first-party-cookies, localStorage, or sessionStorage, where Tealium can pick them up for downstream activation. | \nnetID Implementation Guide | \n
| Partner | \nIntegration Type | \nSummary | \nDocumentation Link | \n
|---|---|---|---|
| Criteo | \nTag | \nCookie Matching associates a cookie that identifies a Tealium visitor to the cookie that identifies the user for Criteo. | \nCriteo Cookie Matching Service Tag Setup Guide | \n
| Criteo | \nConnector | \nAudience Match is a flexible customer targeting solution. | \nCriteo Audiences Connector Setup Guide | \n
| Epsilon | \nTag | \nReturns a list of partner pixel URLs that, when called by the browser, synchronize IDs with exchanges. This allows users can to be identified and messaged after they leave your site. | \nEpsilon Partner Sync Web Service Tag Setup Guide | \n
| The Trade Desk (TDD) | \nTag | \nThe Trade Desk Universal Pixel enables marketers to gain more visibility into user data, and analyze reporting at a more granular level. | \nTrade Desk Universal Pixel Setup Guide for Tealium iQ | \n
| The Trade Desk (TDD) | \nConnector | \nThe Trade Desk Connector can be used for posting enriched Visitor Profiles and Audiences to TDD for more personalized advertising campaigns. | \nThe Trade Desk Cookie Matching Service Tag Setup Guide (used with UID2.0 Function) | \n
| The Trade Desk (TDD) | \nFunction | \nUID2.0 is an open source identifier that replaces third-party cookies. | \nThe Trade Desk Connector Setup Guide (used with UID2.0 Function) | \n
Identity Partners have limitations on where they can operate due to legislation such as the GDPR. Each partner will have different capabilities (for example, Merkle is Global, while the TDD UID2.0 cannot be used within the EU).
\nTo implement identity providers:
\nWe will add more function examples soon.
\n" } , { "weight": "80", "url": "https://docs-preview.tealium.com/server-side/functions/event-visitor-functions/uid2/", "title": "Generate a UID2 with a visitor function", "body": "Unified ID 2.0 (UID2) is an open source ID framework from The Trade Desk. UID2 replaces third-party cookies with a deterministic user identifier based on personally identifiable information (PII), such as an email address or phone number. The identifier is hashed and encrypted to create a UID2, which is returned in response to a UID2 request. For more information, see The Trade Desk: UID2 documentation.
\nA UID2 is supported in The Trade Desk connector and other outbound connectors.
\nWe recommend that you use a visitor function to generate a UID2 for each visitor who has PII but no UID2. The function creates the UID2, sends it with the tealium_visitor_id to Tealium Collect, and updates the visitor’s profile.
For details about visitor functions, see About event and visitor functions.
\nBefore you create a visitor function to generate a UID2:
\nuid_identifier, uid2, uid_timestamp). The function uses this event spec to send an event to Tealium Collect. For more information, see Manage event specifications and About enrichments.![\"Example](\"/images/server-side/functions-uid2_event_spec.png\" "\\"Example")
\n \n ![\"uid2-function-trigger-example.png\"\n](\"/images/server-side/uid2-function-trigger-example.png\" "\\"uid2-function-trigger-example.png\\"/")
\n \n To configure the visitor function:
\nJoined Audience.TODO comments in the code mark required changes.)Version 3 supports multiple identifiers, such as email addresses and phone numbers, in a single request. Update the attribute IDs in the code to match your data. The code prioritizes the email UID, but you can change this as needed. The track() method runs only if the returned UID does not match the existing visitor UID.
The Trade Desk configuration attributes (api_key, secret) and the UID2 attribute ID are grouped in the ttd_config object at the start of the script.
The version three example returns a hashed UID2 for the email attribute in the following JSON structure:
\n{\n "body": {\n "email_hash": [\n {\n "u": "AdvIvSiaum0P5s3X/7X8h8sz+OhF2IG8DNbEnkWSbYM=",\n "p": "EObwtHBUqDNZR33LNSMdtt5cafsYFuGmuY4ZLenlue4=",\n "r": 1735689600000\n },\n {\n "u": "IbW4n6LIvtDj/8fCESlU0QG9K/fH63UdcTkJpAG8fIQ=",\n "p": null,\n "r": 1735862400000\n }\n ],\n "phone_hash": []\n },\n "status": "success"\n}\nUID2 version 2 is deprecated on June 30, 2026. Update any existing UID2 version 2 functions to version 3.
\nThe version 2 example uses email addresses as the user identifier. Adapt it to use a different identifier, such as a phone number. An attribute ID is used to get the value of the email attribute. Update the attribute ID with the correct value for your attribute.
\n\nThe version two example returns a hashed UID2 for the email attribute in the following JSON structure:
\n{\n "body": {\n "mapped": [\n {\n "identifier": "EObwtHBUqDNZR33LNSMdtt5cafsYFuGmuY4ZLenlue4=",\n "advertising_id": "AdvIvSiaum0P5s3X/7X8h8sz+OhF2IG8DNbEnkWSbYM=",\n "bucket_id": "a30od4mNRd"\n },\n {\n "identifier": "Rx8SW4ZyKqbPypXmswDNuq0SPxStFXBTG/yvPns/2NQ=",\n "advertising_id": "IbW4n6LIvtDj/8fCESlU0QG9K/fH63UdcTkJpAG8fIQ=",\n "bucket_id": "ad1ANEmVZ"\n }\n ]\n },\n "status": "success"\n}\nEuropean Unified ID (EUID) is an open source ID framework created by The Trade Desk, which can be used instead of a third-party cookie. EUID is a deterministic user identifier based on a user’s Personally Identifiable Information (PII). EUID currently uses only the user’s email address as an identifier and is limited to European regions. The identifier is hashed and encrypted to create an EUID that is returned in the response to an EUID request. For more information, see the European Unified ID Overview.
\nAn EUID can be used in The Trade Desk connector and other supported outbound connectors.
\nWe recommend using a visitor function to generate the EUID. Trigger the function when the visitor has PII but does not have an EUID assigned. For more information about visitor functions, see About event and visitor functions.
\nThe visitor function does the following:
\ntealium_visitor_id to Tealium Collect.The visitor attribute is enriched by the event sent from the function.
\nBefore you create a visitor function to generate an EUID, do the following:
\n![\"euid-function-trigger-example.png\"\n](\"/images/server-side/euid-function-trigger-example.png\" "\\"euid-function-trigger-example.png\\"/")
\n \nWhen you create your function, do the following:
\nJoined Audience.This example code is only a guide for setting up a function to assign an EUID to visitors and cannot be used without modification. Look for comments in the code with TODO for the lines that must be modified for your configuration.
This example uses an email address as the user identifier, but can be adapted to use other user identifiers. An attribute ID is used to get the value of the email attribute. Update the attribute ID with the correct value for the attribute you’re using and place your EUID credentials in the appropriate locations (api_key and secret).
import CryptoES from 'crypto-es'\n\nactivate(async ({ visitor, visit, helper }) => { \n \n const genHash = (data) => {\n return CryptoES.SHA256(data).toString(CryptoES.enc.Base64)\n }\n const validateEmail = (email) => {\n return String(email)\n .toLowerCase()\n .match(\n /^(([^<>()[\\]\\\\.,;:\\s@"]+(\\.[^<>()[\\]\\\\.,;:\\s@"]+)*)|.(".+"))@((\\[[0-9]{1,3}\\.[0-9]{1,3}\\.[0-9]{1,3}\\.[0-9]{1,3}\\])|(([a-zA-Z\\-0-9]+\\.)+[a-zA-Z]{2,}))$/\n );\n };\n\n let tealium_config = {\n tealium_account: 'CURRENT',\n tealium_profile: 'CURRENT',\n tealium_datasource: 'DATA_SOURCE_KEY', // TODO: Change DATA_SOURCE_KEY to your Tealium Data Source key.\n email_hashed: false // TODO: If your email is already hashed, set this to true.\n };\n\n if(tealium_config.tealium_account == 'CURRENT') {\n tealium_config.tealium_account = visitor.properties.account\n }\n if(tealium_config.tealium_profile == 'CURRENT') {\n tealium_config.tealium_profile = visitor.properties.profile\n }\n const email = visitor.getAttributeValueById("ATTRIBUTE_ID") // TODO: Change ATTRIBUTE_ID to the attribute ID of the user identifier attribute\n let email_hash = '';\n\n console.log(email)\n const tealium_vid = visitor.properties.visitor_id\n\n if(!tealium_config.email_hashed) {\n if(!validateEmail(email)) {\n throw new Error(`Email Attribute is not a valid email`);\n return false\n }\n email_hash = genHash(email)\n } else {\n email_hash = email\n }\n console.log(email_hash)\n\n //Update the following variables with your TTD EUID credentials\n const api_key = 'api_key' // TODO: Change api_key to your assigned EUID API Key\n const secret = 'secret' // TODO: Change secret to your assigned EUID secret\n // const url = 'https://integ.euid.eu/v2/identity/map' // Testing Environment (separate credentials are used). Only use for TESTING\n const url = 'https://prod.euid.eu/v2/identity/map' // Production Environment\n const key = CryptoES.enc.Base64.parse(secret)\n const hexRef = "0123456789abcdef"\n const randomBytes = (bytes) => {\n let buf = ''\n for (let i = 0; i < bytes * 2; i++)\n buf += hexRef.charAt(Math.floor(Math.random() * hexRef.length))\n return buf\n }\n\n const writeBigUint64BE = (num, bytes = 8) => {\n let buf = num.toString(16)\n let padding = ''\n for (let i = 0; i < bytes * 2 - buf.length; i++)\n padding += '0'\n return padding + buf\n }\n\n const encrypt = (data) => {\n const iv = randomBytes(12)\n const nonce = randomBytes(8)\n const millisec = Date.now()\n const timestamp = writeBigUint64BE(millisec)\n const payload = CryptoES.enc.Utf8.parse(JSON.stringify(data))\n const body = timestamp + nonce + payload \n const ivBuf = CryptoES.enc.Hex.parse(iv)\n const encryptedBody = CryptoES.AES.encrypt(\n CryptoES.enc.Hex.parse(body),\n key,\n {\n iv: ivBuf,\n mode: CryptoES.mode.GCM,\n padding: CryptoES.pad.NoPadding\n }\n )\n const ciphertext = encryptedBody.ciphertext\n const authTag = CryptoES.mode.GCM.mac(CryptoES.algo.AES, key, ivBuf, null, ciphertext).toString()\n const enveloped = '01' + iv + ciphertext.toString() + authTag\n\n return {\n timestamp: parseInt(timestamp, 16),\n nonce: parseInt(nonce, 16),\n enveloped: CryptoES.enc.Hex.parse(enveloped).toString(CryptoES.enc.Base64)\n }\n }\n\n const decrypt = (data) => {\n const buf = CryptoES.enc.Base64.parse(data).toString(CryptoES.enc.Hex)\n const iv = CryptoES.enc.Hex.parse(buf.substring(0, 24))\n const ciphertext = CryptoES.enc.Hex.parse(buf.substring(24, buf.length - 32))\n const tag = buf.substring(buf.length - 32)\n const encryptedBody = new CryptoES.lib.CipherParams({ ciphertext: ciphertext })\n const decrypted = CryptoES.AES.decrypt(encryptedBody,key, \n {\n iv: iv, \n mode: CryptoES.mode.GCM, \n padding: CryptoES.pad.NoPadding\n }\n ).toString()\n\n const timestamp = decrypted.substring(0, 16)\n const nonce = decrypted.substring(16, 32)\n const developed = decrypted.substring(32)\n //const tagCheck = CryptoES.mode.GCM.mac(CryptoES.AES, key, iv, null, ciphertext).toString()\n //console.log('\\nauthTag check:', tag == tagCheck)\n\n return {\n timestamp: parseInt(timestamp, 16),\n nonce: parseInt(nonce, 16),\n developed: JSON.parse(CryptoES.enc.Hex.parse(developed).toString(CryptoES.enc.Utf8))\n }\n }\n\n const payload = {\n email_hash: [genHash(email)]\n }\n const {timestamp, nonce, enveloped} = encrypt(payload)\n\n console.log('\\n********** encypted **********')\n console.log('timestamp:', timestamp)\n console.log('nonce:', nonce)\n console.log('enveloped:', enveloped)\n\n const response = await fetch(url, {\n method: 'POST',\n body: enveloped,\n headers: {\n 'Authorization': `Bearer ${api_key}`\n }\n })\n\n if (response.status == 200) {\n const body = await response.text()\n console.log('\\n********** response **********')\n console.log(body)\n const data = decrypt(body)\n console.log('\\n********** decrypted **********')\n console.log('timeStamp:', data.timestamp)\n console.log('nonce:', data.nonce)\n console.log('response:', JSON.stringify(data.developed))\n console.log('\\n')\n\n let event_data ={\n tealium_event: "euid_event",\n tealium_visitor_id: tealium_vid,\n euid_hashed_email: data.developed.body.mapped[0].identifier,\n euid_bucket_id: data.developed.body.mapped[0].bucket_id,\n euid_raw: data.developed.body.mapped[0].advertising_id,\n euid_timestamp : JSON.stringify(data.timestamp),\n euid_nonce: JSON.stringify(data.nonce)\n };\n\n console.log(JSON.stringify(event_data))\n if(event_data.euid_raw) {\n track(event_data, tealium_config)\n .then(response => {\n if (!response.ok) {\n throw new Error(`Network response was not ok. Status code: ${response.status}.`);\n }\n console.log('Status code:', response.status);\n return response.text();\n })\n .catch(error => console.error('Error:', error.message));\n } \n else {\n console.error("Couldn't generate advertising ID")\n }\n } \n else {\n console.log('\\nxxxxx failed xxxxx\\n')\n console.log(JSON.stringify(response))\n }\n })\nUse the Neustar IDMP Site Activity tag to track user behavior on your websites, such as conversion events.
\nGo to the tag marketplace to add a new tag. For more information about how to add a tag, see Manage tags.
\nWhen adding the tag, configure the following settings:
\nLoad the tag on all pages or set conditions for when your tag will load. For more information, see About load rules.
\nMapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For more information, see About data mappings.
\nThe available categories are:
\n| Variable | \nType | \nDescription | \n
|---|---|---|
pixelId | \nString | \nPixel ID | \n
pixelType | \nString | \nPixel type | \n
| Variable | \nType | \nDescription | \n
|---|---|---|
che | \nString | \nCache buster | \n
rev | \nNumber | \nRevenue | \n
cur | \nString | \nCurrency code | \n
qty | \nNumber | \nOrder count | \n
type | \nString | \nType | \n
ord | \nString | \nOrder ID | \n
uid | \nString | \nThird-party user ID | \n
dedup | \nString | \nDeduplication ID | \n
ip | \nString | \nIP Address | \n
Neustar (RUM), Inc. is a trusted, neutral provider of real-time information and analysis to the internet, telecommunications, information services, financial services, retail, media and advertising sectors.
\nwindow.t_pagestart = new Date().getTime();\nWait=Yes (default)Go to the tag marketplace to add a new tag. For more information about how to add a tag, see Manage tags.
\nWhen adding the tag, configure the following settings:
\nLoad the tag on all pages or set conditions for when your tag will load. For more information, see About load rules.
\nMapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For more information, see About data mappings.
\nThe available categories are:
\n| Description | \nVariable | \n
|---|---|
account | \nAccount ID | \n
time_out | \nPerceived load timeout | \n
Go to the tag marketplace to add a new tag. For more information about how to add a tag, see Manage tags.
\nWhen adding the tag, configure the following settings:
\n9876543210).http://www.neustar.biz).Load the tag on all pages or set conditions for when your tag will load. For more information, see About load rules.
\nMapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For more information, see About data mappings.
\nThe available categories are:
\n| Variable | \nDescription | \n
|---|---|
service_id | \nService ID | \n
page_ref | \nPage reference | \n
cv1 | \nCustom variable | \n
rTAG provides the ability to flexibly instrument digital channels with data collection capabilities, identity generation and association, privacy governance and containers for managing invocation of partner tags.
\nGo to the tag marketplace to add a new tag. For more information about how to add a tag, see Manage tags.
\nWhen adding the tag, configure the following settings:
\nLoad the tag on all pages or set conditions for when your tag will load. For more information about load rules, see the Load Rules documentation.
\nMapping 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.
\nThe available categories are:
\n| Variable | \nDescription | \n
|---|---|
Domain name (domain_name) | \n[String] | \n
ESI toggle (esi_toggle) | \n[String] | \n
Logging mode (logging_mode) | \n[String] | \n
Tag type (tag_type) | \n[String] | \n
| Variable | \nDescription | \n
|---|---|
Cache buster, typically set to a random number or timestamp (r) | \n[String] | \n
Encoded URL destination for a 302-redirect directive (ru) | \n[String] | \n
Event ID (evid) | \n[String] | \n
Session ID (s) | \n[String] | \n
Domain (dmn) | \n[String] | \n
Path with filename (pn) | \n[String] | \n
Query string of the URL (qs) | \n[String] | \n
Domain of the referring page (rdn) | \n[String] | \n
Path with filename of referring page (rpn) | \n[String] | \n
Query string of the URL of referring page (rqs) | \n[String] | \n
Unique user agent/user/browser identifier, which can be from a cookie, a statistical ID, or other source (uu) | \n[String] | \n
Statistical id (suu) | \n[String] | \n
The specific class tag configuration to be used (cls) | \n[String] | \n
Publisher or site identifier (pubid) | \n[String] | \n
Partner unique identifier (puu) | \n[String] | \n
Payload passed by client in clientObject (payload) | \n[String] | \n
Advertising agency identifier (ag) | \n[String] | \n
Advertiser or marketer identifier (adv) | \n[String] | \n
Campaign identifier (ca) | \n[String] | \n
Creative identifier (cr) | \n[String] | \n
List of user segments (sg) | \n[String] | \n
Comma separated list of entity types (aqet) | \n[String] | \n
Client-determined variable 0 (v0) | \n[String] | \n
Client-determined variable 1 (v1) | \n[String] | \n
Client-determined variable 2 (v2) | \n[String] | \n
Client-determined variable 3 (v3) | \n[String] | \n
Client-determined variable 4 (v4) | \n[String] | \n
Client-determined variable 5 (v5) | \n[String] | \n
Client-determined variable 6 (v6) | \n[String] | \n
Client-determined variable 7 (v7) | \n[String] | \n
Client-determined variable 8 (v8) | \n[String] | \n
Client-determined variable 9 (v9) | \n[String] | \n
Epsilon is the leader in outcome-based marketing with a rich, 50-year heritage in helping marketers anticipate, activate, and prove measurable business outcomes.
\nFirst, go to the tag marketplace and add the Epsilon Partner Sync Web Service tag (Learn more about how to add a tag).
\nAfter adding the tag, configure the following settings:
\ndtm_ciddtm_cmagicdtm_fidMapping 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.
\nThe available categories are:
\n| Variable | \nData Type | \nDescription | \n
|---|---|---|
dtm_cid | \nString | \nCompany ID | \n
dtm_cmagic | \nString | \nSecondary Company ID | \n
dtm_fid | \nString | \nForm ID | \n
dtm_cookie_id | \nString | \nCookie ID | \n
dtm_user_id | \nString | \nUser ID | \n
dtm_token_sc | \nString | \ndtm_token_sc | \n
dtmc_tcf_string | \nString | \ndtmc_tcf_string | \n
cachebuster | \nString | \nCache Buster | \n
We reccomend that you use the Criteo Audiences (OAuth) connector to send visitor data to Criteo. The OAuth connector uses your Criteo account credentials and the Authorization Code flow for improved security, privacy, and easier account management.
\n| Action Name | \nAudienceStream | \nEventStream | \n
|---|---|---|
| Add User to Audience | \n✓ | \n✓ | \n
| Remove User from Audience | \n✓ | \n✓ | \n
This connector uses the following vendor API:
\nhttps://api.criteo.com/2025-07/audiencesThis connector uses batched requests to support high-volume data transfers to the vendor. For more information, see Batched Actions. Requests are queued until one of the following thresholds is met or the profile is published:
\nIf you intend to use this connector, send an email to asintegrations@tealium.com to receive a consent link that authorizes the Tealium Customer Data Hub to manage audiences on behalf of advertisers. For more information, see Criteo Developers: Send an Authorization Request to Your Users.
\nThis step may take up to three working days for approval.
\nAfter receiving the Criteo activation link, complete the following steps:
\nGo to the Connector Marketplace and add the Criteo Audiences connector to your profile. For general instructions on how to add a connector, see Connector Overview.
\nAfter adding the connector, configure the following settings:
\nClick Next or go to the Actions tab. This is where you configure connector actions.
\nThis section describes how to set up parameters and options for each action.
\n| Parameter | \nDescription | \n
|---|---|
| Audience | \nSelect an audience or enter the Audience ID to add the user to. | \n
| Identifier | \nMap a user identifier value.
| \n
| Gum Caller ID | \nGum Caller ID - Value used by Criteo for GUM (Generative Unified Media) salting. If using the Tealium iQ Criteo Cookie Matching Service tag, leave this unmapped. | \n
| Parameter | \nDescription | \n
|---|---|
| Audience | \nSelect an audience or enter the Audience ID to remove the user from. | \n
| Identifier | \nMap a user identifier value.
| \n
| Gum Caller ID | \nGum Caller ID - Value used by Criteo for GUM salting. If using the Tealium iQ Criteo Cookie Matching Service tag, leave this unmapped. | \n
When using this tag with utag version 4.50 or later, you must set the utag.js always_set_v_id setting to true. This setting ensures that the visitor ID is available for cookie synchronization. For more information, see the utag 4.50 release notes and Considerations for tealium_visitor_id when upgrading to utag 4.50+.
Criteo Cookie Matching Service enables a buyer to associate the cookie that identifies a Tealium visitor, and the cookie that identifies the user for Criteo.
\ncriteo_user_idFor more information about cookie matching in EventStream, see: Understanding Persistent Cookie Matching in EventStream.
\nGo to the tag marketplace to add a new tag. For more information about how to add a tag, see Manage tags.
\nWhen adding the tag, configure the following settings:
\n/event endpoint: Send data to the /event endpoint.Load the tag on all pages or set conditions for when your tag will load. For more information about load rules, see the Load Rules documentation.
\nMapping 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.
\nThe available categories are:
\n| Variable | \nDescription | \n
|---|---|
Tealium Account (tealium_account) | \n[String] | \n
Tealium Profile (tealium_profile) | \n[String] | \n
Days between syncs (days_between_syncs) | \n[Number] | \n
Data Source Key (tealium_datasource) | \n[String] | \n
Use /event endpoint (use_event_endpoint) | \n[Boolean] | \n
utag.track('video', data); which should be implemented in your video event handlers.Go to the tag marketplace to add a new tag. For more information about how to add a tag, see Manage tags.
\nWhen adding the tag, configure the following settings:
\nmerkleinc.com.merkury_identity event, which contains the following information:\neventmerkury_email_sha256merkury_hmidmerkury_confidence_scoreLoad the tag on all pages or set conditions for when your tag will load. For more information about load rules, see the Load Rules documentation.
\nMapping 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.
\nThe available categories are:
\n| Description | \nVariable | \n
|---|---|
sv_cid | \nCID | \n
sv_origin | \nDomain | \n
uID | \nClient ID | \n
em | \nEmail address | \n
eme | \nMD5 email hash | \n
emID | \nClient email ID | \n
base_url | \nBase URL | \n
First-party data, such as a netID, is crucial for accurate retargeting and personalization. The Tealium real-time first-party data platform helps activate these identifiers across channels, enhancing the effectiveness of advertising campaigns.
\nWhen integrating netID’s Single Sign-On (SSO) and consent management solutions, netID partners must implement a request to the netID browser-based JavaScript API. The properties returned from the API must be persisted in the browser session as first-party cookies, in localStorage, or in sessionStorage.
NetID properties like tpid can be used with client-side tags in Tealium iQ to integrate with advertising technologies on your webpage.
Additionally, the same netID properties are collected by the Tealium Collect tag and made available as attributes in EventStream and AudienceStream. With netID saved as a visitor attribute, the visitor profiles can then be activated through real-time connectors to advertising vendors.
\nFor more information about the netID browser-based JavaScript API, see the following:
\n\nnetID properties that have been stored in the browser can be fetched as part of the data layer (UDO object). This data can then be used in Tealium iQ load rules and tag data mappings where relevant.
\nFor example, if you’ve persisted the netID tpid parameter in a first-party cookie, add a new variable of type First-Party Cookie in the data layer, and set the value for Source to the cookie’s name (for example, netid_tpid).
![\"netID](\"/images/industries/netid-add-variable.png\" "\\"netID")
\n \nAs a netID partner, use one of the following methods to include netID’s properties as key-value pairs in the Tealium Data Layer:
\nFirst-Party-Cookie: Persist the netID tpid as a first-party-cookie named netid_tpid in the browser, and it will appear in the data layer with the cp. prefix alongside Tealium standard cookies:
{\n ...,\n "cp.netid_tpid": "Bst040QDNr1nB9JM6sWH0I9__70JEvRyIiKvvd7G0MQLQ",\n ...\n}\nUniversal Data Object (UDO): Use a UDO variable to explicitly persist the netID property in utag_data. For example, add the netID identity property as netid_tpid to the UDO of your pages:
<script type="text/javascript">\n var utag_data={\n "tealium_event" : "page_view",\n "page_name" : "product_page",\n "product_id" : "423543",\n "netid_tpid" : "12345"\n };\n</script>\nTrack an event: Use utag.link() to track a successful netID authentication and response from the browser-based JavaScript API, and include the netID tpid as netid_tpid in the payload:
utag.link({\n "tealium_event" : "netid_login",\n "netid_tpid" : "12345",\n ...\n});\nAfter the Tealium Collect Tag captures netID properties from the browser’s data layer, this data is processed as event attributes.
\nTo do this, create an event attribute to capture the netid_tpid value. In the following example, the attribute is set to the value of the first-party cookie:
![\"netID](\"/images//industries/netid-es-add-attribute.png\" "\\"netID")
\n \nnetID’s identifier (tpid) can be activated as a first-party (Advertiser) ID to an advertising platform using their connector, such as:
If you use Adform, map the netid_tpid event attribute to Adform’s First-Party ID attribute:
![\"netID](\"/images//industries/netid-es-attribute-mapping.png\" "\\"netID")
\n \nThis data is processed as event attributes and can be stored as visitor attributes on the real-time visitor profile.
\nTo do this, set a visitor string attribute on the visitor profile to the netid_tpid event attribute value. In the following example, the attribute is set to the value of the first-party cookie:
![\"netID](\"/images//industries/netid-as-add-attribute.png\" "\\"netID")
\n \nThe visitor ID can then be used to create audiences for visitors using netID as their authentication method.
\n![\"netID](\"/images//industries/netid-as-new-audience.png\" "\\"netID")
\n \nFor real-time activation to advertising platforms such as Adform and The Trade Desk, use their Tealium connectors:
\nWhen using this tag with utag version 4.50 or later, you must set the utag.js always_set_v_id setting to true. This setting ensures that the visitor ID is available for cookie synchronization. For more information, see the utag 4.50 release notes and Considerations for tealium_visitor_id when upgrading to utag 4.50+.
neustar_fabrickId_sync:\nfabrickIdvisitor_idelement_one (Optional)Go to the tag marketplace to add a new tag. For more information about how to add a tag, see Manage tags.
\nWhen adding the tag, configure the following settings:
\nfabrickId will change. Default is seven days.Load the tag on all pages or set conditions for when your tag will load. For more information, see About load rules.
\nMapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For more information, see About data mappings.
\nThe available categories are:
\n| Variable | \nDescription | \n
|---|---|
Base Url (base_url) | \nString | \n
Event Url (event_url) | \nString | \n
Api Key (apiKey) | \nString | \n
FabrickId Timespan Days (daysSyncPeriod) | \nNumber | \n
Tealium Account (tealium_account) | \nString | \n
Tealium Profile (tealium_profile) | \nString | \n
Data Source Key (tealium_datasource) | \nString | \n
Hashed email address (e) | \nString | \n
E.164 standard hashed phone number (p) | \nString | \n
IPv4 Address (raw i4) | \nString | \n
IPv6 Address (raw i6) | \nString | \n
Mobile Advertising ID (m) | \nString | \n
Identifier for Advertising (ia) | \nString | \n
Denotes the source for the IFA (ifa_type) | \nString | \n
Indicates whether the user can be tracked or not (lmt) | \nString | \n
Partner or advertiser’s first-party user ID (1pd) | \nString | \n
When using this tag with utag version 4.50 or later, you must set the utag.js always_set_v_id setting to true. This setting ensures that the visitor ID is available for cookie synchronization. For more information, see the utag 4.50 release notes and Considerations for tealium_visitor_id when upgrading to utag 4.50+.
The Trade Desk Cookie Matching Service tag sets a new variable named ttd_uuid. It is stored as a session cookie and as a standard data layer variable. The tag triggers only once per session, by default.
The Trade Desk Cookie Matching Service tag communicates with the Trade Desk servers to request the current user’s identifier. When this value is returned to the tag, the value is passed to AudienceStream so that it can be used to populate a visitor attribute containing the synced user ID. This attribute can then be used in The Trade Desk connector actions as a mapping to “Trade Desk ID (TDID)”.
\nBefore you add the tag, create the following data layer variables:
\nttd_uuid: UDO Variableutag_main_ttd_uuid: First Party CookieThese variables are populated automatically by the cookie matching tag.
\n![\"The](\"/images/client-side-tags/the-trade-desk-cookie.png\" "\\"The")
\n \nGo to the tag marketplace to add a new tag. For more information about how to add a tag, see Manage tags.
\nAfter adding the tag, configure the following settings:
\nLoad rules determine when and where to load an instance of this tag on your site.
\nThis tag only needs to run if the cookie match has not already occurred. You can determine this by using the cookie variable utag_main_ttd_uuid in a load rule condition such as:
utag_main_ttd_uuid is not defined
The tag also has built-in logic to only fire when the cookie is not defined, but using a load rule ensures that the tag is not loaded on a page when it has already run for the current session.
\nMapping 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.
\n| Destination Name | \nType | \nDescription | \n
|---|---|---|
tealium_account | \nString | \nThe Tealium account to sync the user ID to. The default is the current account. | \n
tealium_profile | \nString | \nThe Tealium profile to sync the user ID to. The default is the current profile. | \n
gdpr | \nBoolean | \nPass a value that indicates if the current user resides in the European Union (EU), and therefore subject to GDPR.
| \n
gdpr_consent_string | \nString | \nBase64 URL-encoded GDPR consent string. | \n
domain | \nString | \nThe domain where the cookie synchronization initiates. NOTE: You must add this domain to Allowlist in The Trade Desk configuration. | \n
order_id | \nString | \nOverrides the _corder e-commerce extension value. | \n
After you save and publish your changes to Prod, the new variables will be available in AudienceStream. The ttd_uuid variable appears as an event attribute, but you must create it as a visitor attribute so that it can be used in The Trade Desk connector action.
To add a visitor attribute to store the ttd_uuid value:
Trade Desk User ID.ttd_uuid.You can now create audiences of visitors that have their Trade Desk User ID populated. Those audiences will be used in connector actions with The Trade Desk. Map this attribute to the “Trade Desk ID (TDID)” parameter in The Trade Desk connector actions.
\n" } , { "weight": "0", "url": "https://docs-preview.tealium.com/server-side-connectors/the-trade-desk-first-party-data-connector/", "title": "The Trade Desk First Party Data connector setup guide", "body": "Go to the Connector Marketplace and add a new connector. For general instructions on how to add a connector, see About Connectors.
\nAfter adding the connector, configure the following settings:
\n| Action Name | \nAudienceStream | \nEventStream | \n
|---|---|---|
| Send First Party Advertiser Data | \n✓ | \n✓ | \n
Enter a name for the action and select the action type from the drop-down menu.
\nThe following section describes how to set up parameters and options for each action.
\nUse either the TDID parameter or the UID2 parameter, not both. Setting a value for both TDID and UID2 can cause connector errors.
| Parameter | \nDescription | \n
|---|---|
| Data Center Region | \n(Required) Select the data center geographically closest to where user data comes from. | \n
| Parameter | \nDescription | \n
|---|---|
| Advertiser ID | \n(Required) Advertiser ID. Available types are DAID, TDID, UID2, EUID, IDL (RampID), ID5, and netID. Only one ID is required. | \n
| Device Advertising ID (DAID) | \nDevice Advertising ID (DAID) | \n
| Trade Desk ID (TDID) | \nTrade Desk ID (TDID) | \n
| Unified ID (UID2 already hashed) | \nUnified ID (UID2). If already hashed, use the Already SHA256 Hashed option and provide a value that has been whitespace trimmed, lowercased, and hashed using SHA256. For more information, see Use a function to generate a UID2. | \n
| UID2 Token (encrypted advertising token) | \nThe encrypted UID2 advertising token. This token is case-sensitive. | \n
| Identity Link (IDL) | \nIdentity Link (IDL) | \n
| Parameter | \nDescription | \n
|---|---|
| Override TTL in Minutes | \nOverride time to live (ttl), in minutes. The maximum ttl is 259200 minutes (180 days). | \n
| Override Timestamp | \nOverride timestamp | \n
| Data Name | \n(Required) Data Name | \n
This connector is not currently available in the Connector Marketplace. Using The Trade Desk Third-Party Data connector requires support from both Tealium and The Trade Desk account managers. To use this connector, contact your Tealium account manager.
\nThis connector uses the following vendor API:
\nhttps://bulk-data.adsrvr.org\nPOST /datarate/batchPOST /data/thirdpartyThis connector uses batched requests to support high-volume data transfers to the vendor. Parallel processing may result in events reaching the vendor out of sequence. Add a sequence value to events if ordering is important. For more information, see Batched actions. Requests are queued until one of the following thresholds is met or the profile is published:
\nGo to the Connector Marketplace and add a new connector. For general instructions on how to add a connector, see About Connectors.
\nAfter adding the connector, configure the following settings:
\nYou must generate an authentication token with a valid username and password before the admin tasks can be performed. Authentication only applies to the admin tasks and is not required for the connector to work.
\nFor more information, see The Trade Desk Partner Portal: Third-Party Data Taxonomy Design.
\n| Parameter | \nDescription | \n
|---|---|
| Provider ID | \n(Required) The unique ID for your provider account, which your Account Manager provided to you. | \n
| Provider Element ID | \n(Required) The unique ID assigned to the segment when the taxonomy was designed. The ID must be 512 characters long or less. This value cannot be changed after you create it. | \n
| Parent Element ID | \n(Required) The provider element ID value from the parent segment in the taxonomy. This parameter establishes the hierarchical structure of your taxonomy. This value cannot be changed after you create it. All data providers use the ROOT base element of the taxonomy. | \n
| Display Name | \n(Required) The name for the segment that buyers see in the DMP user interface. The display name must be 256 characters long or less, but we recommend 50 characters or less for readability, especially for lower-level child elements with longer full paths. Do not include tabs or special characters such as ', ", or ^. | \n
| Buyable | \n(Required) Set to true to make the segment visible and available for buyers in the DMP. For container elements, set this property value to false, since they are used only for organizing child elements and assigning rates. If you change the property value to false for a buyable segment, any customers that currently have the segment in their audience can use it until their campaign ends. | \n
| Description | \n(Optional) A description of the data segment, displayed to customers in the DMP. The description must be 4,000 characters long or less, but we recommend 256 characters or less for readability. | \n
| Is Direct IP Targeting | \n(Optional) If true, the TargetingData used or created is type 16 (DirectIpTargeting) instead of the default 7 (ThirdPartyData). | \n
| Parameter | \nDescription | \n
|---|---|
| Provider ID | \n(Required) The unique ID for your provider account, which your Account Manager provided to you. | \n
| Provider Element ID | \n(Required) A unique ID that identifies this data element in the system. | \n
| Brand ID | \n(Required) The unique ID that identifies a provider-managed brand. | \n
| Rate Level | \n(Required) The rate level for the third-party data. To request access, contact your Technical Account Manager.Partner: For specific partners and their advertisers.Advertiser: For specific advertisers. Note that this rate level requires additional permissions. | \n
| Partner ID | \n(Required) The platform ID of the partner eligible to access data segments at this rate in a custom taxonomy. | \n
| Advertiser ID | \n(Required) The platform ID of the advertiser eligible to access data segments at this rate in a custom taxonomy. | \n
| Rate Type | \n(Required) The data rate type for the segment. All system-level data rates for syndicated taxonomies must be assigned as hybrid rates, which use a percentage of media cost with a maximum CPM (cost per thousand) cap. This means that you must set this property to Hybrid and provide values for both CPMRate and PercentOfMediaCostRate properties. While custom taxonomies can use any data rate type, hybrid rates are strongly recommended. | \n
| CPM Rate Amount | \n(Required) The CPM rate amount. | \n
| CPM Rate Currency Code | \n(Required) The CPM rate currency code. | \n
| Percent of Media Cost Rate | \n(Optional) A percentage of media cost to be used in conjunction with the CPMRate cap for the hybrid data rate (selected in Rate Type). Enter the percentage as a decimal. | \n
| Action Name | \nAudienceStream | \nEventStream | \n
|---|---|---|
| Upload 3rd Party Data | \n✓ | \n✗ | \n
| Delete Third Party Data | \n✓ | \n✗ | \n
Enter a name for the action and select the action type from the drop-down menu.
\nThe following section describes how to set up parameters and options for each action.
\n| Parameter | \nDescription | \n
|---|---|
| Data Provider ID | \n(Required) The provider ID supplied by your Technical Account Manager. | \n
At least one ID parameter is required. Multiple IDs may be included in the same request. The Trade Desk supports the following IDs:
\n| Parameter | \nDescription | \n
|---|---|
| TDID | \nThe Trade Desk 36-character GUID (including dashes) for this user. | \n
| DAID | \nThe raw device ID for this user sent in 36-character GUID format (including dashes). Use iOS IDFA or Android’s AAID. | \n
| UID2Token (already SHA256 hashed) | \nThe user’s Unified ID 2.0, already SHA256 hashed. | \n
| UID2Token (apply SHA256 hash) | \nThe user’s Unified ID 2.0, to which a SHA256 hash is applied. | \n
| UID2 | \nThe user’s Unified ID 2.0 as a 44-character base64-encoded SHA-256 string. For more information, see The Trade Desk Partner Portal: PII Normalization and Hash Encoding and Unified IDs. | \n
| EUIDToken (already SHA256 hashed) | \nThe user’s European Unified ID, already SHA256 hashed. | \n
| EUIDToken (apply SHA256 hash) | \nThe user’s European Unified ID, to which a SHA256 hash is applied | \n
| EUID | \nThe user’s European Unified ID as a 44-character base64-encoded SHA-256 string. For more information, see The Trade Desk Partner Portal: PII Normalization and Hash Encoding. EUID offers user transparency and privacy controls designed to meet market requirements in Europe and the UK, and it requires the same normalization and encoding of email addresses as UID2. For more information, see The Trade Desk Partner Portal: Unified IDs. | \n
| IDL | \nThe 49-character or 70-character RampID (previously known as IdentityLink). This value must be a RampID from LiveRamp that is mapped specifically for The Trade Desk. For more information about mapping a RampID, see LiveRamp: LiveRamp’s Sidecar. | \n
| Parameter | \nDescription | \n
|---|---|
| Name | \n(Required) The segment name. Maximum 128 characters. | \n
| TTL in Minutes | \n(Required) Time to live (TTL) is the amount of time (in minutes) during which this user is to remain active relative to the TimeStampUtc value. When the TTL has expired, the user is no longer used for targeting. The maximum TTL is 259200 minutes (180 days). | \n
| Timestamp | \nThe timestamp of when a user is eligible for a segment. If not specified, the timestamp is assigned based on the time when the data is processed. This timestamp is used to determine a user’s recency for targeting and bid adjustments. | \n
| Parameter | \nDescription | \n
|---|---|
| Data Provider ID | \nRequired. The provider ID supplied to you by your Technical Account Manager. | \n
| Request Type | \n
| \n
At least one ID parameter is required. Multiple IDs may be included in the same request. The Trade Desk supports the following IDs:
\n| Parameter | \nDescription | \n
|---|---|
| TDID | \nThe Trade Desk 36-character GUID (including dashes) for this user. | \n
| DAID | \nThe raw device ID for this user sent in 36-character GUID format (including dashes). Use iOS IDFA or Android AAID. | \n
| UID2Token (already SHA256 hashed) | \nThe user’s Unified ID 2.0, already SHA256 hashed. | \n
| UID2Token (apply SHA256 hash) | \nThe user’s Unified ID 2.0, to which a SHA256 hash is applied. | \n
| UID2 | \nThe user’s Unified ID 2.0 as a 44-character base64-encoded SHA-256 string. For more information, see The Trade Desk Partner Portal: PII Normalization and Hash Encoding and Unified IDs. | \n
| EUIDToken (already SHA256 hashed) | \nThe user’s European Unified ID, already SHA256 hashed. | \n
| EUIDToken (apply SHA256 hash) | \nThe user’s European Unified ID, to which a SHA256 hash is applied | \n
| EUID | \nThe user’s European Unified ID as a 44-character base64-encoded SHA-256 string. For more information, see The Trade Desk Partner Portal: PII Normalization and Hash Encoding. EUID offers user transparency and privacy controls designed to meet market requirements in Europe and the UK, and it requires the same normalization and encoding of email addresses as UID2. For more information, see The Trade Desk Partner Portal: Unified IDs. | \n
| RampID | \nThe 49-character or 70-character RampID (previously known as IdentityLink). This must be a RampID from LiveRamp that is mapped specifically for The Trade Desk. For more information, see LiveRamp: LiveRamp’s Sidecar. | \n
First, go to the tag marketplace and add The Trade Desk Universal Pixel Tag to your profile (See Add a tag).
\nAfter adding the tag, configure the following settings:
\nUse data mappings if you prefer to configure the tag settings dynamically.
\nLoad the tag on all pages or set conditions for when your tag will load. For more information, see About load rules.
\nRecommended Load Rule: Load on all pages.
\nMapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For more information, see About data mappings.
\nThe destination variables for the The Trade Desk Universal Pixel Tag are built into its Data Mapping tab.
\nThe available categories are:
\n| Destination Name | \nDescription | \n
|---|---|
| Advertiser ID | \nUnique advertiser identifier supplied by Trade Desk | \n
| Pixel ID | \nUnique pixel identifier supplied by Trade Desk | \n
td1 | \nCustomer parameter #1 | \n
td2 | \nCustomer parameter #2 | \n
td3 | \nCustomer parameter #3 | \n
td4 | \nCustomer parameter #4 | \n
td5 | \nCustomer parameter #5 | \n
td6 | \nCustomer parameter #6 | \n
td7 | \nCustomer parameter #7 | \n
td8 | \nCustomer parameter #8 | \n
td9 | \nCustomer parameter #9 | \n
td10 | \nCustomer parameter #10 | \n
The consent parameters follow the IAB specification for URL-based services.
\nReference: IAB GDPR Consent Passing for URL-Based Services
\nThe creator of the URL should ensure these parameters are added only once and are passed to services that are expecting them and can properly handle them.
\n| Destination Name | \nValue | \nDescription | \n
|---|---|---|
gdpr | \n0 / 1 | \nDetermines if GDPR should apply to the user. Value of 1 means yes, default value of 0 means no. | \n
gdpr_consent | \nURL-safe base64-encoded GDPR consent string | \nThis parameter should only be passed if gdpr has a value of 1 and gdpr_consent is not an empty string. | \n
gdpr_pd | \n0 / 1 | \nThis parameter is optional and determines if personal data is included. Value of 1 means yes, default value of 0 means no. | \n
Other personal data, such as IP addresses or tracking pixel cookies, may be passed as part of the request. The gdpr and gdpr_consent parameters should be used by the callee to determine whether an identifier cookie or other personal data can be set and/or used.
We recommend using a visitor function to capture the data from Acxiom. For more information on visitor functions, see Event and Visitor Functions.
\nThe visitor function does the following:
\ntealium_visitor_id to Tealium Collect.The EventStream attributes and visitor attributes are enriched by the event sent from the function.
\nacxiom_function_event with the attributes required to enrich the visitor attributes.The function works best when the Acxiom Real Tag tag is installed. This identifier increases the confidence rating for the visitor.
\nTo create the function:
\nYou can test the function with the Test feature and a tool such as Postman API Workbench.
\nFor more information on creating a function, see Managing Functions.
\nThe test example function included below attempts to match a visitor profile based off of the attributes you send to it:
\n| Attribute | \nDescription | \n
|---|---|
acxiom_function_event | \nEvent Spec name | \n
realId | \nAcxiom rTag | \n
address | \nUser’s address | \n
phone | \nUser’s phone number | \n
email | \nUser’s email address | \n
fullName | \nUser’s full name | \n
The function returns any additional user data for profile enrichment.
\nThis code is currently in beta.
\n// In an event scoped function, the following modules are available for use: event, auth\nimport { event, store, tealium } from "tealium";\n(async () => {\n \n // These endpoints will be specific to your setup with Acxiom.\n const access_url="https://mydomain.com/metrics/access_token"\n const query_url="https://mydomain.com/metrics"\n const query_name="demo_dsapi_match"\n\n // Uncomment this to find out exactly what is available to use in your event object\n //console.log('Data available:\\n', JSON.stringify(event, null, 2));\n\n const data = {};\n data.tealium_account = event?.data?.udo?.tealium_account;\n data.tealium_profile = event?.data?.udo?.tealium_profile;\n data.visitor_id = event?.data?.udo?.visitor_id;\n data.trace_id = event?.data?.firstparty_tealium_cookies?.trace_id;\n data.acxiom_real_id = event?.data?.udo?.acxiom_real_id || "";\n data.customer_email = event?.data?.udo?.customer_email;\n data.customer_first_name = event?.data?.udo?.customer_first_name;\n data.customer_last_name = event?.data?.udo?.customer_last_name;\n data.customer_full_name = `${data.customer_first_name} ${data.customer_last_name}`\n\n // Check if acxiom_real_id is available\n // if (typeof data.acxiom_real_id === "undefined") {\n // console.error("acxiom_entity_id is unavailable.");\n // return;\n // }\n\n // Pull in refresh token from global variables\n const refresh_token = store.get("acxiom_refresh_token")\n console.log("refresh_token: ", refresh_token)\n\n // Generate access token\n const access_token_request = await fetch(access_url, {\n method: "POST",\n headers: {\n "Content-Type": "application/json",\n "Authorization": `Bearer ${refresh_token}`\n },\n body: `{"grant_type":"refresh_token","refresh_token":"${refresh_token}"}`\n })\n .catch((error) => {\n console.error('Error:', error);\n });\n const access_token_response = await access_token_request.json();\n // console.log("access_token_response:", JSON.stringify(access_token_response));\n const access_token = access_token_response.jwt_token;\n // console.log("access_token: ", access_token)\n\n // Fetch query_execution_id from Acxiom PAIL with acxiom_real_id\n const response = await fetch(`${query_url}/named_queries/${query_name}/execute`, {\n method: "POST",\n redirect: "follow",\n headers: {\n "Content-Type": "application/json",\n "Authorization": `Bearer ${access_token}`\n },\n body: `{\n "realID": "${data?.acxiom_real_id}", \n "address": "${data?.customer_address}", \n "phone": "${data?.customer_phone}", \n "email": "${data?.customer_email}", \n "fullName": "${data?.customer_full_name}"\n }`\n })\n .then(res => {\n console.log("Res: ", JSON.stringify(res))\n return res\n })\n // .then(response => console.log("Response: ", JSON.stringify(response)))\n .catch(error => console.error('Error: ', error.message));\n const body = await response.json();\n const query_execution_id = body.query_execution_id\n \n // console.log("Status: " + response.status);\n console.log("Body: " + JSON.stringify(body, null, 2));\n\n // Check if Acxiom response data is available\n if (!response.ok) {\n console.error("Acxiom response data is unavailable.");\n return;\n }\n\n // Fetch data from Acxiom PAIL with query_execution_id\n const payload = await fetch(`${query_url}/query_executions/${query_execution_id}`, {\n method: "GET",\n headers: {\n "Content-Type": "application/json",\n "Authorization": `Bearer ${access_token}`\n }\n })\n .then(res => {\n console.log("Res: ", JSON.stringify(res))\n return res\n })\n // .then(response => response.json())\n // .then(response => console.log("Response: ", JSON.stringify(response)))\n .catch(err => console.error(err));\n\n const user_data = await payload.json();\n console.log("user_data: ", JSON.stringify(user_data))\n\n let data_object = {};\n for (let i=0; i < user_data.column_info.length; i++) {\n data_object[user_data.column_info[i].name] = user_data.data[0][i]\n }\n // data_object = JSON.stringify(data_object)\n\n let newEvent = {};\n newEvent = { ...data_object }\n newEvent.tealium_event = "acxiom_function_event";\n newEvent.visitor_id = data.visitor_id;\n newEvent.tealium_trace_id = data?.tealium_trace_id;\n newEvent.customer_email = data_object?.email;\n \n console.log("newEvent: " + JSON.stringify(newEvent, null, 2));\n\n // Send data received from Acxiom to Tealium\n tealium\n .sendCollectEvent(newEvent, data.tealium_account, data.tealium_profile)\n .then(response => {\n console.log('Status code: ', response.status);\n return response;\n })\n .then(data => console.log('Result: ', JSON.stringify(data, null, 2)))\n .catch(error => console.error('Error: ', error.message));\n})();\n