Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

As we're quickly taking off into 2023, our Adobe Target Product teams want to hear your top interest areas for learning opportunities and value realization with Adobe Target ~ to fill out the survey with your suggestions, experience, and feedback, follow the link to the right.

analyticsLogging: "client_side" doesn't work

Avatar

Level 2

Hello all,

 

Has anyone ever got this to work?

https://experienceleague.adobe.com/docs/target/using/integrate/a4t/a4timplementation.html?lang=fr#st...

 

I need to control whether or not to share de SDID between Analytics and Target, so I'm triggering this code when I don't have the user's consent to avoid sharing the SDID:

 

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

 

 

This is done in Launch before the "Load Target" Action is triggered but Target doesn't take it into consideration, I'm still getting the SDID in the following analytics hits, and I don't get the analytics payload in the response from the target call, even though I have this in the target call:

 

Willian_Z_0-1673901108593.png

 

I discovered I can block the analytics hit from getting the SDID if I do this:

 

s.visitor._isAllowedFlag = false;
//or in doPlugins:
s.visitor._supplementalDataIDCurrent = "";

 

But I don't know what could be the side effects of this (nowhere to be found in the documentation) and I prefer to stick to standard implementations.

 

Can anyone help me or Adobe take a took on this?

 

Many thanks,

Willian.

 

0 Replies