Cross domain tracking/implementation with Adobe Web SDK extension | Community
Skip to main content
S
sidhant24
New Participant
August 16, 2023
Solved

Cross domain tracking/implementation with Adobe Web SDK extension

  • August 16, 2023
  • 2 replies
  • 2599 views

I know we can use appendVisitorIDsTo to cross domain ID tracking. But is there a possibility that I can read values of variables for that user in the new domain based on that ID? If yes how?

    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 kamlesh-maddheshiya

    Hi @sidhant24 ,

     

    You'll need to set up the Adobe Web SDK extension on all domains involved.
    Configuration: You need to configure the Adobe Web SDK to include the user identifier (e.g., user ID) and other relevant variables in the tracking requests. This might involve using Adobe's APIs or configuration options to include custom data in your tracking calls.

    Data Mapping: Please ensure that the data being sent to Adobe Analytics includes the user's unique identifier and any other variables you want to track across domains. This can often be done through custom events, eVars, or other Adobe-specific tracking mechanisms.

    2 replies

    Jennifer_Dungan
    Jennifer_Dungan
    New Participant
    August 17, 2023

    It really depends on what you mean by "read values of variables"... if you are talking about one domain has set variables, then you move to the next domain, unless your developers have passed post data on the transfer (like an SSO implementation to know who the user is and info about them), then @kamlesh-maddheshiya is right that you should be able to keep some info about them server side.

     

    However, without WebSDK, maybe you are using an eVar with a Visit level expiry... if the eVar was set on domain 1, and then the user is sent to domain 2 (within the same visit), so long as you don't overwrite that eVar, then the value you set will continue to track without any fancy implementation.

     

    But, like I said, if this second domain is something that is part of your standard flow... like Domain X > purchase flow on Domain Y > user returned to Domain X; then your developers should already be passing information to properly identify the user in the journey and you should be able to leverage that in your tracking.

     

    Like most things, the more context and information we have about what you are trying to do and how your site is set up will help us to help you better.

      S
      sidhant24Author
      New Participant
      September 6, 2023

      Hi @jennifer_dungan @kamlesh-maddheshiya ,

       

      We have several properties with legacy client side implementation and few with Websdk. If user goes from domain A in legacy implementation to domain B in web sdk or legacy and vice vera, we pass some information using storage spanner from search discovery. Storage spanner is going away and we need another solution to pass on the information so that we can fill the evars and props on page view of domain b such as tool target(example evar101 : domain a > domain b and previous page names). 

      Jennifer_Dungan
      Jennifer_Dungan
      New Participant
      September 6, 2023

      Try reviewing https://experienceleague.adobe.com/docs/experience-platform/edge/identity/id-sharing.html?lang=en (Cross Domain ID Sharing)

      kamlesh-maddheshiya
      kamlesh-maddheshiyaAccepted solution
      New Participant
      August 16, 2023

      Hi @sidhant24 ,

       

      You'll need to set up the Adobe Web SDK extension on all domains involved.
      Configuration: You need to configure the Adobe Web SDK to include the user identifier (e.g., user ID) and other relevant variables in the tracking requests. This might involve using Adobe's APIs or configuration options to include custom data in your tracking calls.

      Data Mapping: Please ensure that the data being sent to Adobe Analytics includes the user's unique identifier and any other variables you want to track across domains. This can often be done through custom events, eVars, or other Adobe-specific tracking mechanisms.

      Terms & ConditionsAccessibility statement

      Loading footer...