A4T - How to control SDID sharing prior to at.js version 2.1 | Community
Skip to main content
W
Willian_27Z
Level 2
December 28, 2022
Solved

A4T - How to control SDID sharing prior to at.js version 2.1

  • December 28, 2022
  • 1 reply
  • 720 views

Hello,

 

I need to control when to stitch the SDID parameter between Target and Adobe Analytics (A4T) based on user consent. I've seen in this link that I can do that by doing this:

window.targetGlobalSettings = { analyticsLogging: "client_side" };

 Although this only works from version 2.1 and up.

 

How can I achieve the same result in prior versions? I'm using at.js v1.8.2 via the Adobe Target Launch extension (not the v2)

    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 JacobTo1

    The page might have been updated - looks like the client side logging support was only introduced in at.js v2.1+
    ----

    You can control how and when to send analytics data related to Target to Analytics for reporting purposes. If you do not want to opt in to the default settings of having Target and Analytics automatically stitch the analytics data via the SDID, set analyticsLogging = client_side via window.targetGlobalSettings. Note: any versions below 2.1 do not support this approach.

    1 reply

    J
    JacobTo1Accepted solution
    Level 4
    June 28, 2023

    The page might have been updated - looks like the client side logging support was only introduced in at.js v2.1+
    ----

    You can control how and when to send analytics data related to Target to Analytics for reporting purposes. If you do not want to opt in to the default settings of having Target and Analytics automatically stitch the analytics data via the SDID, set analyticsLogging = client_side via window.targetGlobalSettings. Note: any versions below 2.1 do not support this approach.

      Terms & ConditionsAccessibility statement

      Loading footer...