Expand my Community achievements bar.

SOLVED

Moving from App to website on same device

Avatar

Level 2

Dear Community,

we're having an app where we use the mobile SDK and are linking to our website via little ads. As we want to follow the user journey, we need to establish a (kind of) sync of the MCVID so that we recognize the same user tracked on our website which came from the native app. (Somehow similar to web views)

We were following these introductions: https://github.com/Adobe-Marketing-Cloud/mobile-services/blob/master/docs/ios/reference/hybrid-app.m... but when looking at the data in AA, we can't see anybody opening the website with an existing App Id. When doing so, we see the query param "adobe_mc" attached. Visitor ID Service is in place. When reading the tracking call, should I expect the MID to be the same as attached in the param? Or is it stitched in the background? I found that pretty tough to debug/analyze.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

It should be the same as the passed param... I haven't used this myself, we haven't had enough app to web traffic to warrant implementing this feature yet, but from what I have read, this is supposed to regernerate the ECID cookies on the web with the app ECID.. (however, I would think that there would also be some sort of backend stitching during that overwrite for the old ECID to the new ECID during that process.)

 

This is similar to Cross-Domain Tracking: 
https://experienceleague.adobe.com/docs/id-service/using/id-service-api/methods/appendvisitorid.html...

 

The passed ID should be the ID that is used to track the user....

 

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

It should be the same as the passed param... I haven't used this myself, we haven't had enough app to web traffic to warrant implementing this feature yet, but from what I have read, this is supposed to regernerate the ECID cookies on the web with the app ECID.. (however, I would think that there would also be some sort of backend stitching during that overwrite for the old ECID to the new ECID during that process.)

 

This is similar to Cross-Domain Tracking: 
https://experienceleague.adobe.com/docs/id-service/using/id-service-api/methods/appendvisitorid.html...

 

The passed ID should be the ID that is used to track the user....