Hi guys,
Situation
Problem
Client-side pixel
Datastream setup
AAM setup in the datastream
REMARK:
As seen above, it's a noscropt=1 i.e., the Facebook library is not loaded, no cookies sent nor written, yet the request is going out.
so from a legal standpoint, this is may be a gray area. However, I still think this behavior is not reflecting the consent I just sent.
Now, should Adobe not respect its own Adobe v2.0 consent categories?
Or asked differently, if this seems to be not working, what keeps Adobe Analytics event forwarding from sending data as well?
Please can anyone from Adobe give a statement on this? I spoke to a Adobe trainer last week and according to him, this should be respected internally.
So, should these consent categories not also be automatically applied to internal tools and not just in AEP segment activation?
Best regards
Björn
Solved! Go to Solution.
After talking to Adobe support, they said I should switch to an IAB consent banner since in there you can opt out of AAM. Respecting the user's consent with the Adobe 2.0 consent is currently not possible.
Recommendation is to disable the segment forwarding on AAM side.
Closing this one for now, hoping Adobe will respect the user consent in the near future.
Views
Replies
Total Likes
After talking to Adobe support, they said I should switch to an IAB consent banner since in there you can opt out of AAM. Respecting the user's consent with the Adobe 2.0 consent is currently not possible.
Recommendation is to disable the segment forwarding on AAM side.
Closing this one for now, hoping Adobe will respect the user consent in the near future.
Views
Replies
Total Likes