Adobe Visitor Service Module

The Adobe Visitor Service module interfaces directly with Adobe’s REST API to retrieve and maintain the Experience Cloud ID (ECID) for visitors. The ECID identifies the same visitor in different parts of the Adobe ecosystem, such as Adobe Target and Adobe Analytics, and identifies unique visitors.

If you are migrating from the Adobe tracking SDK to the Tealium SDK, use the Adobe Visitor Service module to pass an ECID in the tracking payload. The new ECID in the data layer may be mapped in the server-side Adobe connectors in Tealium EventStream or Tealium AudienceStream. The Adobe Visitor Service module provides a seamless transition to the Tealium SDK by reusing the existing ECID if it exists and generating a new one if it doesn’t, ensuring an accurate count of visitors in your app.

Supported platforms

The following platforms support the Adobe Visitor Service module:

• Tealium for Android
• Tealium for iOS
• Tealium for React Native

Use Cases

Migrating to Server-Side Analytics

Migrate your Adobe integrations server-side and map the ECID to the marketingCloudVisitorID parameter in the connector using Adobe Analytics server-side through EventStream, and need a valid ECID for multiple Adobe products to work together. The Tealium SDK requests the ECID from Adobe before sending any calls to EventStream, and the ECID is mapped to the marketingCloudVisitorID property in the Adobe Analytics connector.

Tealium iQ Tag Management

We recommend using Tealium iQ Tag Management to generate the ECID when using the Adobe Analytics tag. This guarantees the ECID is readily available, persisted in storage, and independent of the cookie store in the hidden webview.

Migrating from Adobe SDK to Tealium SDK

Migration from the Adobe SDK to the Tealium module is seamless. If your app currently relies on the Adobe SDK to manage the ECID, we recommend having a transition period during which the Adobe SDK is present in the app alongside the Tealium SDK. If the visitor has an existing Adobe ECID, pass it to the Tealium module via the config.adobeVisitorExistingEcid property. If the property is set during initialization, then the existing ECID is used. If the property is not set, the Tealium module retrieves a new one from the Adobe API.

Tracking different visitors on the same device

If you detect different visitor accounts in your app, reset the ECID to ensure each visitor is tracked separately by calling tealium.adobeVisitor?.resetVisitor(). This resets the current ECID and a new one is automatically requested from the Adobe API.

Set your own visitor ID and authentication state

There are several methods for passing your own visitor ID to the Visitor API so that the ID service matches the anonymous ECID to a known ID.

Set a known visitor ID

If you know the visitor’s ID and authentication state when you initialize, use the configuration property adobeVisitorDataProviderId which sets the visitor’s known ID when the module starts:

config.adobeVisitorDataProviderId = "01" // Data provider ID for this type of visitor ID
config.adobeVisitorAuthState = AdobeAuthState.AUTH_STATE_AUTHENTICATED
config.adobeVisitorCustomVisitorId = "customeremail@emailprovider.com"

config.adobeVisitorDataProviderId = "01" // Data provider ID for this type of visitor ID
config.adobeVisitorAuthState = .authenticated
config.adobeVisitorCustomVisitorId = "customeremail@emailprovider.com"

The module automatically requests a new ID if needed, and subsequently sends an additional API call to link the ECID to the known ID supplied in the TealiumConfig properties.

If you need to pass the ID and authentication state when the visitor logs in, call the following method to link the visitor’s known ID to the anonymous ECID:

tealium.adobeVisitorApi?.linkEcidToKnownIdentifier("myidentifier", "123456", AdobeAuthState.AUTH_STATE_AUTHENTICATED, null)

tealium?.adobeVisitorApi?.linkECIDToKnownIdentifier("myidentifier", adobeDataProviderId: "123456", .unknown)

Troubleshooting

The following lists the different API failure behaviors:

• Missing Adobe organization ID
  If the module is enabled but an Adobe organization ID has not been passed in the TealiumConfig object, the module is disabled and tracking calls continue without an Adobe ECID.

• Invalid Adobe organization ID
  The module attempts to retry up to the retry limit (default: 5). After the retry limit has exceeded, tracking calls continue as normal without the ECID, and any queued requests are sent immediately.

• Adobe API returns an error or an empty response
  In the event that an error is returned while sending a request, such as connectivity failure, the module attempts to retry up to the retry limit (default: 5). After the retry limit has exceeded, tracking calls continue as normal without the ECID, and any queued requests are sent immediately.

• The module encounters either (2) or (3) above, but the visitor’s previous ECID has been provided on the TealiumConfig object. After the maximum retries, the module uses the provided visitor ID value and does not block any requests.

If your top priority is getting data to Tealium, then set the number of retries to 0 to skip retrieving the ECID in case of failure. The number of retries is controlled by the config.adobeVisitorRetries property.

Data Layer

The following variables are added to the data layer:

URL Decoration

Adobe products loaded in a web context, such as the Adobe Analytics JavaScript tag, automatically use an Experience Cloud ID. This ID is passed in the query string of the web page when passed in the adobe_mc parameter. The adobe_mc parameter contains multiple values, separated by the pipe character (|).

The resulting URL is:

https://tealium.com/?adobe_mc=MCMID=1234|MCORGID=12345@AdobeOrg|TS=1655826247

The adobe_mc parameter is URL-encoded.

The Adobe Visitor Service module provides two methods to support this feature, which are described below.

Tag Management Module

The adobe_mc parameter is automatically appended to the URL used by the Tealium webview in the Tag Management module.

Custom Webviews

If your app uses webviews to display content, you need to make the Adobe ECID available in that webview so that all Adobe products loaded in the webview know the user’s ECID. This prevents the user from appearing as two different users in the native app and in the webview.

The Adobe Visitor Service module provides a method to decorate a webview URL with a query string parameter. This causes Adobe Analytics to use the ECID generated by the module instead of using the Experience Cloud ID Service JavaScript tag. As shown in the example, you must pass the URL to the decorateURL method and then load the returned URL when you want to load a webview in your app.

This method preserves any query parameters already present on the URL

val url = adobeVisitorModule.decorateUrl(URL("https://tealium.com/?myparam=abc&myparam2=bcd"))
// Resulting URL = https://tealium.com/?myparam=abc&myparam2=bcd&adobe_mc=MCMID%3D1234%7CMCORGID%3D12345%40AdobeOrg%7CTS%3D1655826247
// Only for demonstration purposes; launch your app's webview with the resulting URL
myApp.launchWebview(url)

let url = URL(string: "https://tealium.com/?myparam=abc&myparam2=bcd")!
tealium.adobeVisitorApi.decorateURL(url) { url in
    // Resulting URL = https://tealium.com/?myparam=abc&myparam2=bcd&adobe_mc=MCMID%3D1234%7CMCORGID%3D12345%40AdobeOrg%7CTS%3D1655826247
    // Only for demonstration purposes; launch your app's webview with the resulting URL
    myApp.launchWebview(url)
}