Once you've added your pixel, it's worth verifying events are firing before you pour budget into ads. Two easy ways: Meta's Test Events tab in Events Manager, or the Meta Pixel Helper browser extension. Either will pick up your Link's PageView and ViewContent events.
What about the "missing price and currency" warning?
Meta sometimes flags ViewContent events with a warning about missing price and currency info. That warning is built for e-commerce sites, where ViewContent means someone is looking at a product page (with a price). SubmitHub Links aren't selling anything, so there's nothing to attach. We've confirmed with Meta directly that it's safe to ignore.
What about the IPv4 vs. IPv6 warning?
Meta sometimes flags that your CAPI events are sending IPv4 addresses while the browser pixel is picking up IPv6, and recommends switching. We already prioritize IPv6 when it's available in the request headers from your visitor. If we're sending IPv4 anyway, it's because the visitor's connection didn't expose an IPv6 address that we could pick up server-side. Safe to ignore.
What about the "events aren't being deduplicated" warning?
They are. We fire each event twice on purpose: once from the visitor's browser through Meta's pixel, and once server-side through the Conversions API. Both carry the same event ID, which is how Meta pairs them and counts the event once.
Why the warning shows up anyway: a lot of visitors run ad blockers or browser tracking protection that block the browser pixel but not the server-side call. Those events reach Meta only from our servers, with no browser copy to pair against, so Meta can't confirm they were deduplicated and flags it. Nothing is double-counted. If anything, the Conversions API is recovering conversions the browser pixel would have missed. Safe to ignore, and there's nothing to change on your end.
Using Meta Pixel Helper
If both events appear with your Pixel ID attached, your setup is working.
If nothing shows up
Still stuck? Reach out to us and we'll take a look.