Support

Omea Consent · Troubleshooting

Conversions API events missing? Check these first

Meta, TikTok, LinkedIn, Snap or GA4 server events not arriving from WordPress? Check consent, the token, the test code, the mapping and the log.

Updated · Omea Consent 1.0.2

On this page
  1. 1. The visitor didn’t consent
  2. 2. A test event code is still set
  3. 3. The token is missing or wrong
  4. 4. The conversion isn’t mapped to the platform
  5. 5. The server-side event has no matching conversion
  6. 6. Platform-specific requirements
  7. 7. The same event was sent already
  8. 8. Too many test events in a row
  9. Still missing?

Start with the platform card under Omea Consent › Integrations: Latest server events shows the newest events with a Sent or Error badge. Nothing there means nothing was sent; an error means the platform refused it. Then work through this list.

Server events follow consent:

API Needs
Meta, TikTok, LinkedIn, Snap Marketing
GA4 Measurement Protocol Statistics

When testing, accept all cookies in a private window first. A visitor who rejected produces no server events – that’s by design.

2. A test event code is still set

For Meta and TikTok, while a Test event code is set, events go to Test events only and aren’t counted. The card shows Test mode – not counted. Clear the code and save.

3. The token is missing or wrong

The API can’t be switched on without a token – you’ll see “… was not switched on: paste the access token first.” If you paste a new one, it replaces the saved token; leaving the field empty keeps the old one. If the platform rejects the token, generate a new one in its events manager and paste it again.

4. The conversion isn’t mapped to the platform

A conversion is sent only to platforms with a value in its Send to ad platforms row. Under Omea Consent › Conversions, edit the conversion and set the Meta, TikTok or Snap event, the LinkedIn conversion ID or the GA4 event name.

5. The server-side event has no matching conversion

A server-side event such as purchase or signup reaches ad platforms only if a conversion with the same name exists with the trigger Custom event. Click Make conversion next to the event in Server-side events.

Also check that the event is switched on: sign-ups, logins and comments are off by default; the WooCommerce events are on.

6. Platform-specific requirements

  • LinkedIn needs the visitor’s hashed email or the li_fat_id click ID. Without either, the event is skipped.
  • GA4 needs the visitor’s _ga cookie to link the event to a session – so GA4 itself must be running with Statistics consent.
  • GA4 only receives server-side conversions this way. Browser conversions go through the GA4 tag, not the Measurement Protocol.

7. The same event was sent already

Each event ID is sent once per day, so a reloaded thank-you page or a repeated test with the same order doesn’t create duplicates. Test with a new order or a new form submission.

8. Too many test events in a row

To protect your site, browser-triggered server events are limited to 20 per 10 minutes per visitor. Wait a few minutes between bursts of testing.

Still missing?

Pro includes priority email support: write to info@cultmetrics.com with your site address, the platform, and what Latest server events shows.