TrackStack Docs
TrackStack Docs
DashboardPricingTrackStack DocsQuickstartExamplesSDK SetupB2B SaaS EventsEvent Payload ContractPlatform Event MappingRouting PolicySupported Platforms
API Playground
GitHub

Platform Event Mapping

Canonical event to destination-specific event name reference.

TrackStack maps each canonical event to platform-native names at the edge. The dashboard Configure → Events tab shows the mapped name as a subtitle when you select events.

Core mappings (blueprint §4)

CanonicalMetaGoogleLinkedInSignUp family
SignUpCompleteRegistrationsign_upSign Up—
StartTrialStartTrialbegin_checkoutStart Trial—
PurchasePurchasepurchasePurchase—
LeadCapturedLeadgenerate_leadLead—
DemoBookedSchedulegenerate_leadLead—
PageViewPageViewpage_viewPageView—
ContentViewViewContentview_itemViewContent—
AddPaymentInfoAddPaymentInfoadd_payment_info——
PlanUpgradePurchasepurchasePurchaseMaps to purchase family
SubscriptionRenewSubscribepurchasePurchase—

Refund and chargeback events map internally but are excluded from default platform allowlists — route to warehouse/CRM only unless you explicitly enable them.

Default platform allowlists (blueprint §15)

These are applied when you click Reset to platform defaults in the dashboard. A blank allowlist means all 66 canonical events.

PlatformDefault events
MetaPageView, ContentView, LeadCaptured, DemoBooked, SignUp, StartTrial, FirstAction, AddPaymentInfo, Purchase, PlanUpgrade, SubscriptionRenew
Google AdsLeadCaptured, DemoBooked, SignUp, StartTrial, FirstAction, Purchase, PlanUpgrade, SubscriptionRenew (PageView/ContentView via GA4 separately)
LinkedInPageView, ContentView, LeadCaptured, DemoBooked, SignUp, StartTrial, SalesQualifiedLead, OpportunityCreated, Purchase
RedditPageView, ContentView, LeadCaptured, SignUp, Purchase
TikTokPageView, ContentView, LeadCaptured, SignUp, Purchase
MicrosoftPageView, LeadCaptured, DemoBooked, SignUp, Purchase
QuoraLeadCaptured, DemoBooked, SignUp, Purchase
PinterestPageView, ContentView, SignUp, Purchase
SnapchatPageView, SignUp, Purchase
XPageView, ContentView, LeadCaptured, SignUp, Purchase

Mapping templates

Events not listed in §4 use logical templates:

TemplateUsed forExample platforms
Page viewHighIntentPageView, AdLandingPageView, ReturningVisitorMeta PageView, Google page_view
Content viewDocsInteraction, IntegrationViewed, ApiDocsViewedMeta ViewContent
LeadFeatureUsed, DemoIntent, activation eventsMeta Lead, Google generate_lead
ScheduleDemoBooked, MeetingHeldMeta Schedule
Sign upSSOLogin, EmailVerified, WorkspaceCreatedMeta CompleteRegistration
CheckoutCheckoutStartedMeta InitiateCheckout
PurchaseRevenue events, CreditsPurchasedMeta Purchase, TikTok PlaceAnOrder
CustomProduct ops events, ChurnedPlatform custom event names

Overrides

Override per capture when your ad account requires specific IDs:

trackstack.capture("SignUp", {
  eventId: "evt_001",
  email: "user@example.com",
  platformParams: {
    linkedin: { conversionRuleId: "12345678" },
    google: { sendTo: "AW-XXXX/YYY" },
    meta: { test_event_code: "TEST12345" },
  },
});

Related docs

  • Supported platforms — Credentials and CAPI status
  • Routing policy — Ads vs warehouse
  • Event payload — Full payload contract

Event Payload Contract

Universal TrackStackEvent shape for SDK capture and edge ingestion.

Routing Policy

What goes to ad platforms, CRM, and warehouse by default.

On this page

Core mappings (blueprint §4)Default platform allowlists (blueprint §15)Mapping templatesOverridesRelated docs