Can we migrate to ECID from visitorID and not lose Visitors?

[DanielWo8]

Hi, I read all threads about the subject and I haven't found clear answer.

Let's say we have Adobe Analytics implementation with vsitorID (server side by Tealium EventStream)

We would like to migrate to Adobe Cloud ID (ECID) identifiers.

My understanding was that we can enable ECID in parallel to visitorID, have some months of traffic with both identifiers and then turn off visitorID to smoothly migrate visitors which came to the website in between. But the way how it works in our test is following:

Scenario (values are created by me)
1. Visit with visitorID=123 only
2. Visit with visitorID=123 and ECID=abc => the same Visitor
3. Visit with ECID=abc (without visitorID) => NEW (2nd) VISITOR

Why visitor with the same value as ECID is not stitched before and after turning off visitorID?

Is there a way to migrate from visitorID to Adobe Cloud ID without completely loosing existing Visitors?

[bjoern__koth]

Hi @DanielWo8 ,

so, yes, you can set the visitorID on the AppMeasurement extension as described here.

This under the assumption that your Tealium server-side visitor ID is known and accessible through a cookie.

https://experienceleague.adobe.com/en/docs/analytics/implementation/vars/config-vars/visitorid

BUT that being said, I do not know if this is a wise idea, at least I don't think there is an actual deduplication of the events happening.

In other words, you may keep the same number of users but duplicate your tracking calls.

To be honest, I would aim for a big bang switch away from TiQ SFF to Analytics client-side, since we are talking about a major technology shift.

Test your new tracking impementation by sending into a dummy report suite, and if the numbers are comparable, switch over from TiQ.

And from there on just use the Experience Cloud ID service to handle the ECIDs.

This way you can make sure other Adobe tools like Target and Audience Manager work as expected.

[DanielWo8]

Hi bjoern__koth

thank you for answer. My need is little bit different. We already have Adobe implementation by client side Event Stream with visitorID.

We would like to switch to ECID on the same implementation.

I know how to technically enable it but the problem is that if we enable both identifiers (let's say for few months) I would expect that Visitors reported in requests with both visitorID and ECID in the future will be stitched to requests where only ECID is reported.

So my expectation is:

1. Visit with visitorID=123 only => Visitor A
2. Visit with visitorID=123 and ECID=abc => Visitor A (the same Visitor)
3. Visit with ECID=abc (without visitorID) =>Visitor A (the same Visitor)

While Adobe is doing this:

1. Visit with visitorID=123 only => Visitor A
2. Visit with visitorID=123 and ECID=abc => Visitor A (the same Visitor)
3. Visit with ECID=abc (without visitorID) =>Visitor B (NEW Visitor)

Does it make sense to you? What would be effect of grace period described here? How to achieve smooth transition from visitorID to ECID?

[FarazHusain · Accepted solution]

Hey @DanielWo8 In the example that you have shared, 3. Visit with ECID=abc (without visitorID) =>Visitor A (the same Visitor); the issue is if the visitor ID (set by s.visitor ID) is not present, then Adobe doesn't know if this is the same visitor reason being the ECID is based on the cookie and s.visitor ID is set JS. There is no seeding happening to link s.visitor ID with ECID, and I also don't think this is possible currently with respect to VisitorID. 

Hence, when a user lands with ECID only, then it will be treated as a new visitor in this case because there is no link between s.visitorID and ECID.

[DanielWo8]

thanks for clarifying.