Front-end and server-side tracking statuses

In the conversion detail panel, the Front-end tracking and Server-side tracking sections each show a status per ad platform. This article explains what those statuses mean.

Where you’ll see them
Reporting → click a conversion row → Metrion Technology section. Each ad platform (Google Ads, Meta Ads, TikTok Ads) appears with its own status under both Front-end tracking and Server-side tracking.

What the statuses mean

Eligible
The conversion is suitable to be uploaded to the platform. This does not guarantee the platform actually accepted it — the destination has its own validation and may reject the record after upload (for example, because of a missing required field). Eligible means Metrion did its part correctly.

Not fired
The pixel did not fire for this platform on this conversion. For front-end tracking this can have several causes: the user blocked the script, the page navigated before the pixel finished, the consent banner blocked it, or the platform’s pixel isn’t installed on the page. Server-side tracking is the safety net for exactly these cases — even when the front-end didn’t fire, the server-side upload usually still goes through.

How to read the panel

• Front-end Not fired + Server-side Eligible. The healthy fallback case. The page-side pixel didn’t fire, but Metrion’s server-side upload picked up the slack. Common, especially with strict consent setups or ad blockers.

• Both Eligible. Best case — both layers worked, and the destination has the richest possible data.

• Both Not fired. The conversion can’t be sent to that platform. Investigate the conversion’s consent state and the click ID first.

Why front-end and server-side both exist
Front-end tracking gives ad platforms behavioural signals (page-level firings, audience signals) they can’t get from server-side. Server-side tracking gives them complete, consent-respecting conversion records that can’t be blocked by the browser. Run both for the most robust setup.