Consent Mode v2 plus server-side tagging is a strong pairing once you understand how the consent state needs to travel with the event.

The short version: measurement that respects consent without quietly dropping data is mostly a matter of doing the obvious thing carefully. Set the default state on the page, propagate it as part of every payload to your server container, and let the destinations decide what they are allowed to do.

You will write more configuration than you would like, but the audit trail is worth it. That trade-off is the one most teams underweight when they plan the work, and it is the one that quietly determines whether the project ships on time.

If you want a longer treatment, we have a deeper post in the series. For now, the takeaway is small enough to fit on a sticky note: Once it is wired up correctly, Consent Mode v2 stops being something you think about and starts being something the system handles.