New MID generated even with Old one instanciated in URL | Community
Skip to main content
S
Swanan_
Level 4
October 20, 2021
Solved

New MID generated even with Old one instanciated in URL

  • October 20, 2021
  • 1 reply
  • 2214 views

Hi community,

 

I'm currently not able to track my visitor from my app to the webview.

 

I already found a lot of documentation like this one and this one. But it didn't fix my problem.

Currently, my third-party cookies are disabled (included demdex cookie) and I can't enable them. So I need to find a way to track the visitor without it.

When my user is on the app environment, a MID is generated. See the screenshot below from app context:

I achieved to save this ID in the URL when the user goes from the App context to the Webview context.

But my problem is that when the user is landing on the webview, a new MID is being generated even if the first one is instantiate in the URL.

See screenshot below from webview context:

You can see on the mid variable a new MID being generated. While the first one is stored in the URL in the g variable.

We reached Adobe customer care to learn more about that. They told us to use the method overwriteCrossDomainMCIDAndAID but it didn't help us here.

 

Does anyone have any suggestion?

Thank you

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Andrey_Osadchuk

@swanan_ ,

Customer Care suggested the right option. I have reviewed the property "da**v2" and the option overwriteCrossDomainMCIDAndAID is not enabled now in live. Could you confirm that it was set to true while you were testing that scenario?

 

1 reply

Andrey_Osadchuk
Andrey_OsadchukAccepted solution
Level 10
October 20, 2021

@swanan_ ,

Customer Care suggested the right option. I have reviewed the property "da**v2" and the option overwriteCrossDomainMCIDAndAID is not enabled now in live. Could you confirm that it was set to true while you were testing that scenario?

 
S
Swanan_Author
Level 4
October 22, 2021

Hi @andrey_osadchuk 

So yes, I checked and the test has been done correctly.

 

Even if we set the option overwriteCrossDomainMCIDAndAIDto true, it's still generating a new MID when we are landing on the webview.

Is there any other settings I can modify to be sure that the MID will be catch from the URL and used as the "main MID" ? Or maybe anyother option to stop the generation of a new MID when we land on the webview ?

 

Is it a problem if the ECID i always the first rule triggered on each pages ? And especially when we land on the webview ?

 

Thanks a lot for your help

 

S
Swanan_Author
Level 4
November 2, 2021

Hi @andrey_osadchuk,

Do you have any though about my last answer?

 

Thanks a lot

Terms & ConditionsAccessibility statement

Loading footer...