17 ad + analytics platforms, one schema
TrackLayer standardizes conversion-grade events once, then maps them into seventeen platform-specific APIs without forcing your team to relearn naming, consent logic, identity handling, or payload rules for every destination in the stack.
Platform table
Deduplicated purchase and lead events for Meta Pixel plus server-side CAPI delivery.
Click-aware Events API forwarding for web conversion and catalog-ready event streams.
Enhanced Conversions and click conversion uploads with first-party identity normalization.
Measurement Protocol delivery for revenue, lifecycle, and consent-aware event replay.
Server-side conversion routing for catalog, remarketing, and upper-funnel campaign measurement.
Pixel-linked Conversions API delivery with hashed identifiers and deterministic event IDs.
B2B-safe conversion event forwarding for lead, MQL, pipeline, and revenue milestones.
Server-side purchase and lead events for Reddit Ads with pixel-linked event ingestion.
Conversion uploads for X campaigns using hashed identifiers and twclid-aware matching.
Offline conversion submission for Bing and Microsoft Advertising conversion actions.
Search ads conversion delivery for app and keyword-driven acquisition programs.
Off-Amazon conversion feeds for retail media teams that need server-confirmed sales signals.
Simple event delivery for lower-volume lead generation and research-heavy conversion paths.
Commerce-grade event forwarding into Criteo's event layer for audience and campaign feedback.
Advertiser transaction posting for affiliate-driven sales with browser click reference preservation.
Publisher-side conversion posting for performance editorial and native acquisition programs.
Native and publisher conversion delivery for content discovery campaigns and post-click revenue tracking.
Category breakdown
Paid media destinations that need conversion-grade purchase, lead, and funnel events with consistent IDs, consent handling, and value fields.
Measurement destinations where the canonical TrackLayer event becomes a clean reporting event without rebuilding instrumentation per tool.
Networks and publisher endpoints that depend on stable click references, transaction values, and deterministic postback timing.
What we do not yet support
Our platform taxonomy
TrackLayer starts from a canonical event model, not from Meta's purchase schema, GA4's ecommerce object, or an affiliate postback's parameter list. A purchase, qualified lead, refund, or subscription event exists once inside TrackLayer with one stable name, one event ID, one event time, and one business meaning.
From there, the destination layer translates that canonical event into native requirements. Meta wants event_name, event_id, and user_data. Google Ads wants conversion actions and click-aware uploads. GA4 wants Measurement Protocol payloads. Affiliate and publisher endpoints want click references, transaction IDs, and commission-safe order values. The upstream business event stays the same even while the downstream contract changes.
That separation is what keeps the system maintainable. Product and engineering teams instrument once against a durable vocabulary, while destination-specific logic lives at the edge where TrackLayer can enforce consent policy, normalize identity fields, preserve deduplication, and version mappings without forcing a rewrite every time a platform changes its API.
FAQ
Because direct point-to-point mappings drift fast. A canonical schema lets the product own event naming, value handling, consent state, and identity normalization once, then translate outward in a controlled way.
No. They receive the same business event expressed through TrackLayer's model, then mapped into platform-native field names, endpoint rules, and identifier requirements.
Those destinations are already in the platform surface, but the public long-form setup guide is still being packaged. The implementation path exists today; the dedicated landing guide is catching up.
GA means the platform is part of the stable operating path for standard ecommerce and lead events. Beta means the adapter exists and works, but account-specific validation, docs depth, or operational polish is still maturing.
No. This page is the current inventory, not a fixed ceiling. The roadmap section shows the next candidates already under discussion with customers and partners.
Next reads
See which identifiers matter most once one canonical event fans out to many ad destinations.
Understand how browser and server events collapse into one conversion across mixed destination setups.
Read how click IDs, emails, external IDs, and consent state become a usable event graph.