Server-side tracking on WordPress without Stape or sGTM
Send conversions from your WordPress server to Meta, TikTok, LinkedIn, Snap and GA4 – no tagging server to host, and only with the visitor's consent.
Browser pixels lose conversions: ad blockers stop them, Safari limits their cookies, and visitors close the tab before the thank-you page finishes loading. Server-side tracking fixes that by sending each conversion from your own server, where none of that applies.
The usual route is a server-side Google Tag Manager container hosted by Stape or on Google Cloud – another system to set up, run and pay for. Omea Consent Pro does it from inside WordPress instead.
How it works
- A conversion happens – a WooCommerce order, a form, a sign-up.
- The browser pixel sends it (if the visitor consented), with an event ID.
- Your WordPress server sends the same conversion to the platform’s API with the same event ID.
- The platform sees two copies with one ID and counts it once. If the browser copy was blocked, the server copy still arrives.
Events are sent after the page has been delivered, so visitors don’t wait for them.
Supported platforms
| Platform | API | Consent needed |
|---|---|---|
| Meta | Conversions API (CAPI) | Marketing |
| TikTok | Events API | Marketing |
| Conversions API | Marketing | |
| Snapchat | Conversions API | Marketing |
| Google Analytics 4 | Measurement Protocol – server-side conversions only | Statistics |
| Google Ads | Enhanced conversions (through the browser tag) | Marketing (ad consent) |
Each one is switched on inside its platform card under Omea Consent › Integrations, with an access token or API secret.
Consent comes first
Server-side tracking is often sold as a way to get around the cookie banner. Omea does the opposite:
- Every event is checked against the visitor’s consent on the server, from their consent cookie. No consent, no event.
- For events completed later, such as an order marked paid in the admin, Omea uses the consent recorded on the order at checkout.
- Personal details – email, phone, name, address – are hashed with SHA-256 before they leave your server. The IP address and browser details are sent as they are, because the platforms require them for matching.
What gets sent
- Browser conversions you’ve defined under Conversions are sent server-side too, through a small endpoint on your site.
- Server-side events – WooCommerce purchases, checkouts and add-to-carts, sign-ups – are sent directly from WordPress, with no browser involved.
See what was sent
Each platform card shows Latest server events: the last few events with a Sent or Error badge, the event name and when it went. No personal data is stored in this log. If something is missing, see Conversions API events missing.
Frequently asked questions
Do I need a server-side GTM container?
No. Omea Consent Pro sends the events straight from WordPress to each platform’s API. There’s no tagging server to set up, host or pay for.
Is server-side tracking a way around consent?
Not with Omea. Every server-side event checks the visitor’s consent on the server first. Without consent, nothing is sent.
Does it slow my site down?
Events are sent after the page has been delivered to the visitor, so they don’t add waiting time to the page.