storing adobe marketing cloud visitorID in an Tealium Variable

Silver Contributor
Silver Contributor

I am trying to set eVar17 to the Adobe Marketing Cloud ID. 

I do this with a "set data values" extension setting a UDO element to "s.marketingCloudVisitorID"

This does not set eVar17 on initial page load, but with a subsequent utag.view() call in console, eVar17 sets just fine. 

Is this a problem with referencing the s object in an extension before s is actually created? How is this done? 

Thanks!

4 REPLIES 4

storing adobe marketing cloud visitorID in an Tealium Variable

Silver Contributor
Silver Contributor

The way I fixed this was a set Data Values extension and set the UDO relevant UDO variable to Visitor.getInstance("A0D53D675A4612EA0A495D83@AdobeOrg").getMarketingCloudVisitorID();

unfortunately just trying to reference s.marketingCloudVisitorID does not work on pageload. 

storing adobe marketing cloud visitorID in an Tealium Variable

Bronze Contributor
Bronze Contributor

Hi @schampernowne. You can do this by setting the eVar in the doPlugins code.  The doPlugins code could be a javascript extension scoped to your adobe tag.

doPlugins() are the last thing that get called before the beacon is set.  That means the Adobe tag loads, the extentions loads, doPlugins fire, then image request is sent.

storing adobe marketing cloud visitorID in an Tealium Variable

Gold Contributor
Gold Contributor

Hi @schampernowne,

 

An alternative would be to use the set data extension to set the evar to "D=mid" (without the quotes).

When Adobe is processing the data it will replace the D=mid to the correct value.

A second alternative is to use processing rules in Adobe to set the evar to the maketing cloud id.

Both of these would have the advantage that you are not subject to race conditions or other javascript issues.

The downside is that you are less flexible in defining fallbacks if the visitor would not have an mid...

storing adobe marketing cloud visitorID in an Tealium Variable

Moderator
Moderator
@schampernowne you could reuse the code I added to the Adobe UDH connector article to help you do this. If you use Tealium's proxy to Visitor.getInstance() in an extension scoped to the Marketing Cloud Visitor ID Service template (vAPI.getInstance), it works like a subscriber, and will only call the callback function once the visitor ID has been successfully returned from Adobe. This eliminates any timing issues. Be sure to use the latest version of the Marketing Cloud ID template. Link: https://community.tealiumiq.com/t5/Universal-Data-Hub/Adobe-Analytics-Connector-Setup-Guide/ta-p/221...
Check out our new Swift integration library for iOS, macOS, tvOS and watchOS: https://github.com/Tealium/tealium-swift with updated
documentation https://community.tealiumiq.com/t5/Swift/tkb-p/swift.
Public