Tracking & Attribution
Orders tracked on the server, not guessed in the browser
Orders reach Admetriva straight from the store's server, with their real value and products, linked to the ad click. And tracking health is always visible.
What it solves
- A browser tag can be blocked, duplicated or tampered with, so the order value is no longer reliable.
- Duplicate or missing conversions are found late, after they have shaped budget decisions.
- Order items do not always match catalogue IDs, so product-level reporting breaks.
What you get
-
Server-to-server events
The order is read from the store's database and sent signed, with a secret unique to the project.
-
Duplicate protection
Each transaction is accepted once; repeated or stale requests are rejected.
-
Click identifiers
gclid, gbraid and wbraid are kept from the visit to the order.
-
Items matched to the catalogue
Order items are matched to Merchant Center IDs, for product-level reporting.
-
Tracking health
Accepted and rejected events, missing click IDs, unmatched products, duplicates.
-
Consent respected
Marketing data is only sent for the categories the visitor agreed to.
What it looks like in practice
The store sends the order when it reaches the status you chose, for example "paid". Admetriva checks the signature, records it once and links it to the click and the products. If an order arrives without a click ID or with an unknown product, you see it in tracking health.
Admetriva never changes anything in your campaigns.
See your campaigns clearly, in one place
Create your account, connect your platforms and get your first signals after the first sync.