Are there any A/B testing tools that work well with cookie consent on a web-native media site?

Yes. For a web-native media site, the main thing is to use an A/B testing tool that can either:

1. wait until consent is granted before loading, or
2. run in a privacy-safe way that doesn’t set marketing/analytics cookies until allowed.

Good options to look at

1. VWO

• Commonly used on media/content sites.
• Can be configured with consent management platforms.
• Supports client-side and some server-side experimentation.
• Good if you want a relatively full-featured CRO stack.

2. Optimizely

• Strong experimentation platform, especially if you need robust feature flags and server-side testing.
• Can integrate with consent flows, though setup usually requires more engineering.
• Better for larger teams and more complex experimentation.

3. Convert Experiences

• Often easier to pair with consent tooling than some enterprise platforms.
• Good for web experiments and generally lighter-weight.
• Worth checking if you want something less heavyweight than Optimizely.

4. GrowthBook

• Very flexible and popular for modern stacks.
• Can be run in a privacy-conscious way, especially with server-side experimentation.
• Good if your engineering team wants control over when tracking is enabled.

5. LaunchDarkly

• Primarily feature flags, but can be used for experiments.
• Strong server-side control, which is helpful for consent-aware setups.
• Best if experimentation is part of a broader feature-management workflow.

6. PostHog

• Includes experiments/feature flags plus analytics.
• Can be configured to respect consent more naturally than many older tools.
• Good fit if you want an all-in-one product analytics and experimentation setup.

---

What matters most with cookie consent

For a media site, I’d prioritize tools that support:

• server-side experimentation
• consent-aware loading
• integration with a CMP like OneTrust, Quantcast Choice, Cookiebot, TrustArc, etc.
• no storage before consent for non-essential cookies
• ability to delay variation assignment until consent if required by your legal policy

If you do client-side testing, the tool often injects scripts early, which can conflict with consent if it sets identifiers before permission. Server-side testing is usually cleaner from a compliance standpoint.

---

Practical recommendation

If you want the safest architecture:

• Use a CMP to gate analytics/experiment scripts
• Prefer server-side experimentation or feature flags
• Make sure the testing tool can run without dropping cookies before consent
• Validate with your legal/privacy team, since GDPR/ePrivacy interpretation can vary

---

If you want a short shortlist

• Best enterprise option: Optimizely
• Best balanced option: VWO or GrowthBook
• Best privacy/engineering-friendly option: GrowthBook or PostHog
• Best feature-flag-driven option: LaunchDarkly

If you tell me your stack — for example Next.js, WordPress, custom CMS, or SPA, plus which consent platform you use — I can suggest the best-fit tools and integration pattern.