Adobe Target

Pablo_Lago_Sanchez-MartinO · 10/22/24

Hi, im trying to do a use case to share info between two differents domains when i use the same scrip of Adobe Target and the same endpoint, i got a cookie with the same ID call DOMAIN!mboxPC and its the same number in my two domains, i need to send some info between them is it possible to modify the cookie in one side so in the other side it also modifies, or does anyone know how can i solve this. I tried create targetPageParams() and returning a param but only creates in one domain and it does not persist inthe other( im seeing the delivery).

Thanks!!

Gokul_Agiwal · 10/23/24

Hi @Pablo_Lago_Sanchez-MartinO

Before approaching the above use case, could you please tell how your Adobe target implementation has been setup?

- Is it using at.js ( either enable adobe target through Adobe tag manager or calling at.js directly) or

- Is it using web sdk?

- are you trying to implement cross domain via subdomains (For ex. www.test.com and abc.test.com) or entirely two different domains ( For ex: siteA.com and siteB.com)

- are you using ECID service?

Let us know so we can dig more in details on this use case. Thanks

Gokul_Agiwal · 10/23/24

Hi @Pablo_Lago_Sanchez-MartinO

while I'm looking for response from you for above queries, meantime Please have a look below resources.

If you're using at.js then - Cross-domain tracking makes it possible to see sessions on two related sites, but with different domains, as a single session. You could create a Target activity that spans siteA.com and siteB.com and the visitor would remain in the same experience when they crossed domains.

for more info - https://experienceleague.adobe.com/en/docs/target-dev/developer/client-side/at-js-implementation/atj...

If you're using Web SDK - then the appendIdentityToUrl command allows you to add a user identifier to the URL as a query string. This action allows you to carry a visitor’s identity between domains, preventing duplicate visitor counts for datasets that include both domains or channels.

https://experienceleague.adobe.com/en/docs/experience-platform/web-sdk/commands/appendidentitytourl

and Using ECID - https://experienceleague.adobe.com/en/docs/id-service/using/id-service-api/methods/appendvisitorid

Hope this helps.

Pablo_Lago_Sanchez-MartinO · 10/24/24

Good morning @Gokul_Agiwal I'm using the same at.js script in both profiles in a tag manager and they are different domains siteA.com siteB.com, i read the info u sent but i was not able to solve my problem. The point is sending a param between the target profile i thought that if it was the same user maybe there are some attributes in common that persists, i was able to activate crossDomain so as i mention before i have the same DOMAIN!mboxPC in both that may help right?

Thanks!

Gokul_Agiwal · 10/24/24

Hi @Pablo_Lago_Sanchez-MartinO Good Morning,

Could you please confirm what at.js version you're using in both domains?

Pablo_Lago_Sanchez-MartinO · 10/24/24

Hello again @Gokul_Agiwal , we're using 2.11.4

Gokul_Agiwal · 10/24/24

@Pablo_Lago_Sanchez-MartinO Ok thanks

so In this case, you have to mboxSession parameter must be passed.

Here is the scenario -

Users cross domains and you want to track and test their behavior across these domains.

Example: A user comes to your site to shop but checks out through Yahoo stores. Three approaches (work with your account representative to determine the best approach):
- Enable first- and third-party cookies.
- Enable third-party only (very rare, but has the benefit of keeping the at.js cookie out of your domain).
- Enable only first-party cookies and pass mboxSession parameter when crossing domain.
  
  The mboxSession parameter must be passed to a landing page with at.js referenced. It cannot be an intermediate redirector page.