Question

A retail company is migrating from client-side JavaScript tags to a server-side tagging architecture, where a single first-party endpoint receives events from browsers and then forwards them to marketing, analytics, and advertising vendors. The privacy engineer must ensure that a user's declined consent for advertising still prevents advertising vendors from receiving data. Which design approach BEST enforces the user's consent decision in this architecture?

Accepted Answer

Propagate the user's granular consent state to the server-side container and configure per-purpose forwarding rules that suppress vendor calls when the corresponding consent is absent

Answer

Rely on each downstream vendor to honor a consent flag included in the forwarded payload according to its own contractual commitments

Answer

Continue collecting all events at the server endpoint and apply consent filtering in a nightly batch job before data is used for advertising

Answer

Set browser cookies with a shortened expiration for users who decline advertising so that vendor tags naturally stop firing