
Case study · Own WordPress plugin, consent & server-side tracking
Omea Consent Pro – cookie consent and the Conversions API in one WordPress plugin
We designed, built and run our own consent platform for WordPress: a free plugin on WordPress.org, a Pro plugin that sends conversions from the site’s own server, a cloud scanner that checks what slips through, and the licensing service behind it all.
The starting point
Omea started in our analytics consulting work, where every client setup needed the same stack: a consent tool, Tag Manager, a pixel plugin and often a tagging server for the Conversions API. Four things to configure, pay for and keep in step with each other. Omea Consent puts that stack into one WordPress plugin. It is our own product, not a client project.
What we built
- Omea Consent, free on WordPress.org: the banner and preferences window in four layouts, script blocking, a consent log with CSV export, an auto-updating cookie policy, Google Consent Mode v2, Global Privacy Control and multilingual texts with Polylang or WPML.
- Omea Consent Pro: one-click tags for eight ad and analytics platforms, Conversions APIs sent from WordPress, rules per region and the banner on pages outside WordPress.
- A cloud scanner that visits the site like a first-time visitor and reports what still loads before consent.
- A licensing and billing service at account.cultmetrics.com – a lightweight PHP service with Stripe, outside WordPress – plus a knowledge base at support.cultmetrics.com.

Paste an ID – every tag waits for the right consent
Instead of a Tag Manager container and a consent tool that have to agree with each other, the plugin owns both sides:
- Google Analytics 4, Tag Manager, Google Ads, Meta, TikTok, Microsoft Advertising, LinkedIn and Snap are added by pasting an ID.
- Google tags run with Consent Mode v2; the others load only after Marketing consent.
- Tags already hard-coded on the site are found and moved into the integrations with one click.
- Microsoft UET and Clarity and HubSpot get their own consent signals too.
Conversions from the site’s own server
Ad blockers and browser limits hide part of every pixel’s data. The usual fix is a server-side tagging host. We built the server side into WordPress itself:
- One event, counted once. The browser pixel and the server send each purchase, lead and sign-up with the same event ID, so Meta deduplicates them. TikTok, LinkedIn and Snap work the same way.
- Google too. GA4 Measurement Protocol and Google Ads enhanced conversions are included.
- WooCommerce found for you. Purchases, checkouts and add-to-carts are suggested as conversions automatically.
- Consent first. Customer data is normalised and SHA-256 hashed, and sent only with the visitor’s Marketing consent. The endpoint that receives browser events validates every event ID and is rate-limited.
A scanner that checks the banner actually blocks
A banner that looks right can still let trackers through. The cloud scanner loads the site in a real browser as a first-time visitor in the EU, with three fresh profiles: before any choice, after “Reject all” and after “Accept all”. It lists every cookie (names only, never values), storage key and third-party script in each phase, and recognises the buttons of other common consent tools as well as Omea’s own. The free plugin includes one scan; Pro scans every month and emails when something new shows up.
Technical quality that holds up
- Rules per region: opt-in in the EU, UK and Switzerland, a US opt-out notice with “Do Not Sell or Share My Personal Information”, and a choice for everywhere else – working with page caching.
- One line in the header of a HubSpot blog or landing page tool shows the same banner there and runs the same tags after the same consent.
- An end-to-end release gate in Playwright tests what a site owner assumes each feature does – banner, consent models, GPC, embeds, regions – and checks that the WordPress.org package matches the source.
- Everything in the free plugin stays free; Pro only adds.
Need consent and tracking that hold up?
Omea Consent is what we know about consent, Consent Mode and server-side conversions, packaged as a product. If your setup needs the same thinking – or a plugin of its own – let’s talk.
Omea Consent and Omea Consent Pro are Cultmetrics products. Screenshots: the Omea Consent product page and a demo site. This case study describes the plugins as built and shipped.