Know which events
can still match.
TrackLayer measures fbp_presence_rate, fbc_presence_rate, and identifier_match_rates, then applies the consent firewall before routing. Teams can see whether identity is improving, degrading, or blocked by policy.
Built from the product surface, not brochure claims.
What the team actually gets.
Identifier inventory
Track hashed email, hashed phone, external_id, fbp, fbc, gclid, ttclid, and GA client ID by event.
Presence rates
fbp_presence_rate and fbc_presence_rate make browser and click continuity visible.
Consent firewall
Routing honors consent state before payloads leave TrackLayer for ads, analytics, or lifecycle tools.
Match-rate trends
identifier_match_rates show whether a checkout, theme, or consent change actually improved identity.
How it compares to ordinary tracking work.
- fbp_presence_rate
- tracked
- fbc_presence_rate
- tracked
- identifier_match_rates
- per identifier
- Consent firewall
- pre-route
- Identity alerts
- identity_gaps
- fbp_presence_rate
- manual
- fbc_presence_rate
- tag debug
- identifier_match_rates
- EMQ only
- Consent firewall
- tag rules
- Identity alerts
- manual
- fbp_presence_rate
- platform UI
- fbc_presence_rate
- limited
- identifier_match_rates
- partial
- Consent firewall
- app settings
- Identity alerts
- platform symptoms
Real merchant-shaped cases and measurable signals.
The references an operator can inspect.
Where this matters in production.
The new checkout stopped reading fbc on the order domain.
fbc_presence_rate fell immediately and identity_gaps pointed to affected purchase events.
Lead forms had strong external_id but weak phone coverage.
identifier_match_rates showed which enrichment field sales ops needed to add.
Regional consent rules needed to block ad enrichment while allowing analytics.
The consent firewall split routing by destination without changing source events.