What are the capability differences between implementing the WebSDK client-side and utilizing Event forwarding compared to using the Server Side API for things like data collection and/or deployment of 3rd Party Tags?
Are there any differences specifically related to things like 3rd Party Cookie Deprecation (will one method protect you better from this), Safari / Apple ITP, and setting FPID that are enabled by one method or another?
hello @yuhuisg First of all thanks and I really appreciate your time. In the context of client-side collection web SDK advisable & data streams.
But my Q was from the server-side AA data collection as we face a lot of data-loss due to cookie consent messaging!
So it has to be either events forwarding or server-side API ingestion, correct? for clickstream I am leaning towards events forwarding. Thanks
Since you have cookie consent, then I would expect that there would be data loss because some users deny consent to be tracked. And if users are denying consent, then shouldn't you respect their decision instead of trying to overcome it by collecting their data anyway?
I'm not a lawyer nor legally trained. I'm sharing the above based on what I understand to be the expected outcome for having cookie consent.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.