Cookie Consent via Adobe Experience Platform Tags in
|

The Launch article notes unpublished rules never reach production. Confirm the rule is saved, included in a built library, and published to the environment you are testing.

Double-check that both scripts are present in the Custom HTML action. Also look for other tags or hard-coded snippets that set cookies before your Secure Privacy rule executes.

Yes—that is the point of the integration. As long as Launch loads on the page, you can inject Secure Privacy without editing your CMS templates, subject to your internal governance.

No. Launch and GTM solve similar problems for different stacks. Many enterprises run both; coordinate sequencing so only one CMP loads unless your architecture intentionally requires otherwise.

Follow Secure Privacy’s Google Consent Mode v2 Advanced guide for GTM when Google tags are in play. Adobe Launch handles injection, while GCM wiring may still use the CMP template path.

Run a fresh Secure Privacy scan, update your cookie declaration, and monitor analytics for unexpected drops that could signal ordering issues.

Assign ownership to whoever already manages Launch—typically marketing ops or a tag governance team—with change control similar to other high-risk tags.

Yes. Experience Platform Tags is the current name for the Launch tag management product referenced throughout Adobe documentation.

Start with the Secure Privacy support article linked on this page, then contact Secure Privacy support if you need implementation assistance beyond the guide.