Ad blockers suppress 25-35% of client-side revenue events
Server-side attribution for publishers, newsletter operators, and content businesses
TrackLayer connects article views, newsletter clicks, paywall moments, and subscription revenue into one server-side event stream — with Square POS, custom HTTP ingest, consent firewall, and GDPR/CCPA jurisdiction. It keeps source article, author, category, consent, and subscriber value intact before Meta, Google, Reddit, and X receive the payload.
Why media needs this
Subscription signups get attributed to last-click instead of the source article
Newsletter-driven subscribers die in Meta's attribution window without server-side help
What TrackLayer ships for media
Article-level attribution
Track which article, author, section, and campaign drove a subscription instead of stopping at sitewide signup counts.
Newsletter lifecycle events
Newsletter subscribe, confirm, and unsubscribe are normalized as canonical events with stable event IDs.
Paywall metering events
Capture article_viewed, paywall_hit, and paywall_bypass so subscription intent is visible before checkout.
Subscription tier tracking
Track free, digital, print+digital, and group tiers with plan metadata that travels downstream.
Revenue-weighted subscription events
Send LTV estimates at signup so acquisition platforms optimize toward subscribers that retain.
CMP + Consent Mode bridge
Carry IAB TCF 2.2 and Consent Mode state through routing so EU traffic stays compliant.
Installation in 3 steps
Drop the TrackLayer script in your theme or CMS: WordPress, Ghost, Substack proxy, or Prose
Map CMS events to TrackLayer's canonical media taxonomy
Forward server-side CAPI events to Meta, Google, Reddit, and X
Webhook to CAPI
{
"event": "subscription.created",
"cms": "wordpress",
"occurred_at": "2026-04-23T14:36:00Z",
"subscriber": {
"email": "reader@example.com",
"country": "US",
"tier": "digital",
"estimated_ltv": 186.00
},
"source": {
"article_id": "post_18472",
"title": "Inside the new creator economy",
"author": "Maya Chen",
"category": "Business",
"url": "https://publisher.com/business/creator-economy",
"newsletter": "Morning Brief"
},
"attribution": {
"utm_source": "newsletter",
"utm_campaign": "morning-brief-0423",
"fbclid": "IwAR3..."
}
}{
"event_name": "Subscribe",
"event_time": 1776954960,
"event_id": "wordpress_post_18472_sub_9183",
"action_source": "website",
"event_source_url": "https://publisher.com/business/creator-economy",
"user_data": {
"em": ["a8f5f167f44f4964..."],
"fbc": "fb.1.1776954600.IwAR3...",
"client_ip_address": "203.0.113.42",
"client_user_agent": "Mozilla/5.0 ..."
},
"custom_data": {
"currency": "USD",
"value": 186.00,
"subscription_tier": "digital",
"source_article_id": "post_18472",
"source_author": "Maya Chen",
"source_category": "Business",
"newsletter": "Morning Brief"
}
}From $99/mo
Publisher proof
"We finally know which articles drive subscribers. Our editorial team can optimize what they commission."
Director of Product at a top-50 US publisher
FAQ
Does TrackLayer work with WordPress, Ghost, Substack, and custom CMS setups?
Yes. TrackLayer can run from a theme, tag slot, server-rendered template, CMS webhook, or custom event bridge. Substack usually needs a proxy or export-driven flow because the native surface is more constrained.
Can newsletter platforms like Beehiiv, Ghost, Substack, and SendGrid be integrated?
Yes. Subscribe, confirm, click, unsubscribe, paid conversion, and renewal events can be mapped into a single subscriber timeline before routing to ad platforms.
Do paywall vendors like Piano, Memberstack, and Tinypass work?
Yes. TrackLayer can ingest paywall impressions, meter hits, registration prompts, bypass events, checkout starts, and subscription completions from paywall vendors or your own gating logic.
Is EU IAB TCF 2.2 supported?
Yes. TrackLayer can carry CMP consent strings, purpose grants, vendor grants, and Google Consent Mode state so events are routed only when the configured policy allows it.
Can we measure without cookies or without consent?
TrackLayer does not bypass consent. It can still support modeled, aggregate, or consent-safe server events where your legal basis and CMP configuration permit that measurement.
Built for Media
Consent firewall
GDPR/CCPA-aware routing blocks non-consented events before platform delivery.
Square POS + custom HTTP
In-store and online events unified in one canonical stream.
GDPR/CCPA jurisdiction
Region-aware processing and data residency for publisher compliance.