A4T Mismatched SDID (Target vs Analytics Calls) | Community
Skip to main content
A
adspio3
October 13, 2022
Solved

A4T Mismatched SDID (Target vs Analytics Calls)

  • October 13, 2022
  • 1 reply
  • 1375 views

Hi All, 

 

First post, hoping someone might be able to clear up my confusion.  Thanks in advance!

 

Summary:

I have a client who implemented code outside of Launch to append cross-domain links with MCID/SDID.  However, I found an issue with their code which causes "SDID" to not match between the /delivery POST reqeusts for target, and the b/ss GET calls for analytics.

 

I see in documentation it says they 'must' match, but I'm quite confused because A4T reporting inside Workspace still appears to work. (https://experienceleague.adobe.com/docs/target/using/integrate/a4t/before-implement.html?lang=en#section_2C1F745A2B7D41FE9E30915539226E3A)

 

EDIT: To add if it matters, the "ECID" value does match for /delivery and b/ss tracking calls.


My questions:

What exactly does this break if I can see the data in Workspace and also the "reports" tab in Target?

 

While we already have a fix getting tested now that will solve this mis-match, how can we interpret the data already collected?  Is A4T in Workspace not going to know which experience was served?  Or what side-effect(s) can be explained?

    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 AbuSh1

    Hi 
    Let's clarify some concept (Analytics and Target reports are not same)

    • Target reports gives you the data based experience deliver to destination pages (Not rendered experienced). If multiple campaign qualified for same placement with same priority Target will deliver both campaigns to the page and Page script will render one campaign randomly.
    • SDID (tnta in mobile apps) on the other hand based on campaign rendition. Data collected via the analytics will inform analytics to forward the data to Target. This way Analytics will be added forward to target for reporting

    if you implement the SDID/tnta it will make the A4T works better; but there will be always some differences due to delivery approach vs rendering approach 

     

    Thanks

    Abu

    1 reply

    A
    AbuSh1Accepted solution
    Level 4
    October 17, 2022

    Hi 
    Let's clarify some concept (Analytics and Target reports are not same)

    • Target reports gives you the data based experience deliver to destination pages (Not rendered experienced). If multiple campaign qualified for same placement with same priority Target will deliver both campaigns to the page and Page script will render one campaign randomly.
    • SDID (tnta in mobile apps) on the other hand based on campaign rendition. Data collected via the analytics will inform analytics to forward the data to Target. This way Analytics will be added forward to target for reporting

    if you implement the SDID/tnta it will make the A4T works better; but there will be always some differences due to delivery approach vs rendering approach 

     

    Thanks

    Abu

      Amelia_Waliany
      Adobe Employee
      Amelia_WalianyAdobe Employee
      Adobe Employee
      November 30, 2022

      Hey there @abush1 thanks for posting this comprehensive Answer to @adspio3 's first Question posted in the Target Community, and for making this important distinction! Welcome @adspio3  😃🙌  If you found @abush1 's answer to be helpful, please do mark it as "Correct" or feel free to follow up for clarification from him or another Target community member ✅

      In the meantime, you might find some related helpful information on A4T here in one of our latest webinars + accompanying Community Q&A Coffee Break chats on the topic 😊 Hope this helps!

       

      Terms & ConditionsAccessibility statement

      Loading footer...