Seeka sends your event data to Meta through two channels: browser-side, via the pixel tag on your website, and server-side, via the Meta Conversions API. The server-side feed is the important one - it's first-party and much harder to block.

In Events Manager, when both channels are flowing you'll generally see the source shown as "multiple". The exact wording varies between versions of Meta's interface, so you may also see "Conversions API" or "Pixel and Conversions API".

This is the most common one, and it's almost always about how ViewContent is being used rather than anything being broken.

ViewContent is an e-commerce event, so Meta expects a dollar value attached to it. Plenty of businesses use it for lead generation instead - firing it when someone simply visits a page, where there's no value to send. Meta then flags the mismatch.

The fix: in Seeka, go to Apps → Settings → Tracking Defaults and set a value to be used in place of an empty one (many people use $1). That way no empty-value event is sent and the warning goes away.

Meta started requiring a value on Lead events at some point - it wasn't always enforced, which is why this can appear on a setup that's been running happily for a while.

The fix: two options, whichever suits you. Set a default value in Apps → Settings → Tracking Defaults if the same value applies every time, or configure it per-event in the Express Setup Tool if your Lead events carry different values.

There's nothing for you to configure here. This one sits on Meta's side and isn't something you can change from Seeka.

Meta is receiving the same event from two sources. The usual culprits:

For the full detail on this, see Understanding Pixel Implementation and Duplicate Firing Pixel Events.

Worth knowing before you spend an afternoon on it: all platform event managers are subject to bugs, and a good number of the warnings you'll see appear and then vanish with nothing having changed. They aren't necessarily connected to your data flow at all. Unknown errors around currency and values very often fall into this category.

If there is a genuine known issue with an event or a platform, we'll always surface it in the Seeka interface, so if you're not seeing a notice from us, an intermittent Meta warning is usually safe to leave alone.

Use Seeka's own diagnostic tool: Settings → Diagnostics. If Seeka looks healthy there, any remaining warnings in Events Manager are Meta-side configuration, not a Seeka data problem.

Still stuck? Start a conversation with us and include the exact error message — we'll dig into it. 🙂