Events get lost on the way
Some conversions never reach the platform: a blocker eats the script, the request fails, the page closes too early. In the ad account it simply looks like the campaign stopped working.
Conversion tracking you can actually trust
Valkiria puts its own pixel on your site, accepts server-side events and reconciles them with Meta Pixel and the Conversions API. You get the numbers plus a trust score for them: sync freshness, token status and conversion collapses.
Why your reports and your ad account disagree about conversions
Pixel and server both count the sale
Without a shared event_id the browser event and the server event arrive as two separate conversions. The algorithm optimises against an inflated number and moves budget the wrong way.
Nobody notices the day it breaks
The pixel quietly dies after a site release and it gets spotted a week later, through an odd CPA jump. Checking every platform by hand every morning never actually happens.
Three steps to working tracking
Create a pixel
Create a Valkiria pixel with a name and description. The setup wizard walks through the remaining steps and marks what is already done.
Put the code on the site
Paste the generated JS snippet into the site head or your tag manager. From then on page views, leads and purchases go into the Valkiria conversion queue automatically.
Connect platforms and verify
Configure conversion events for Google Ads and Meta, then run diagnostics: it shows whether events arrive and whether they are being counted twice.
What the tracking module gives you
Your own pixel, no middleman
The code goes in once and the events land on your Valkiria instance, not in someone else's analytics product.
Server events with deduplication
The conversion reaches Meta carrying a shared event_id, so the browser hit and the server hit merge into one instead of doubling the count.
Meta Pixel and CAPI diagnostics
Five checks: CAPI configuration, event_id deduplication, server event delivery proof, domain verification and the evidence needed to audit them.
The conversion queue in plain view
How many events are waiting, how many were sent and how many failed — with a button to process the queue by hand.
A trust score for the data
Sync freshness, OAuth token status and conversions collapsing while clicks hold are rolled into one score per platform.
Checks never touch the account
Diagnostics is read-only: it hands you steps and ready-made snippets, and what actually changes stays your call.
In numbers
- 5
- Meta Pixel and Conversions API checks in one diagnostic run
- 0
- changes written to your ad account by a tracking check
- 13
- ad platforms in one control room
Questions about conversion tracking
Do I need a developer to install the pixel?
Usually not. Valkiria generates a JS snippet with your pixel id already filled in — paste it into the site head or your tag manager. A developer is only needed for server-side events, which your backend sends from the order or lead handler.
How is this different from Google Analytics?
Google Analytics answers what people did on the site. Valkiria tracking answers whether the conversion reached the ad platform and whether its numbers can be trusted. That is why it ships a sending queue, event deduplication and Meta Pixel plus Conversions API diagnostics.
How do I verify that the Conversions API really works?
The Meta diagnostic checks five things: whether the CAPI configuration is enabled, whether event_id deduplication is proven, whether server event delivery is confirmed, whether your domains are verified, and whether there is enough evidence to audit any of it. Each finding comes with the evidence and concrete steps.
What do I do when conversions are counted twice?
Double counting almost always means the browser event and the server event travel without a shared event_id. The diagnostic flags it as its own issue and shows a snippet where the same event_id goes to both the pixel and the server request — after that Meta merges them itself.
Does a tracking check change anything in my ad account?
No. Tracking diagnostics is read-only and writes nothing to the platform. Everything it offers is local: copy a snippet, fire a test event, or open the relevant screen in the platform's own interface.
See whether your conversions arrive
The diagnostic changes nothing in the account — it only shows where the signal is lost and what to repair first.