Supported Platforms

TrackStack routes canonical events to these conversion APIs. Use the ID column in platformParams for per-platform overrides.

Platform overview

Platform	ID	CAPI / API status	Typical mapping targets	Official docs
Meta (Facebook)	meta	✅ CAPI	Purchase, Lead, CompleteRegistration	Conversions API
Google Ads / GA4	google	✅ GA4 MP + Enhanced Conversions	purchase, sign_up, custom conversions	GA4 Measurement Protocol
LinkedIn	linkedin	✅ Conversions API	Conversion rules with value/currency	LinkedIn Conversions API
Reddit	reddit	✅ Conversions API	Standard conversion events and custom labels	Reddit Conversions API
TikTok	tiktok	✅ Events API	Web events with contents and value fields	TikTok Events API
X (Twitter)	x	✅ Conversion API	Conversion IDs and values	X Conversion API
Microsoft Ads	microsoft	UET (client-side)	UET + conversion goals	Microsoft UET
Quora	quora	✅ Conversions API	Lead and purchase conversion signals	Quora for Business

Where this appears in the platform UI

• Onboarding (/dashboard/onboarding) lets teams pick initial conversion destinations.
• Settings -> Platforms (/dashboard/settings/platforms) controls per-key enable/disable and event filters.
• Settings -> Event Mapping (/dashboard/settings/event-mapping) controls canonical event allowlists by platform.
• Platforms health (/dashboard/platforms) is the operational delivery view.

Platform override pattern

Use platformParams when your ad account requires a specific mapping, conversion rule ID, or destination override:

trackstack.capture("SignUp", {
  eventId: "evt_signup_01",
  email: "jane@example.com",
  platformParams: {
    linkedin: { conversionRuleId: "signup_started" },
    google: { sendTo: "AW-XXXX/YYY" },
  },
});

eventId is optional; include it when you need cross-system dedup parity.

Per-platform notes

• Meta — Use content_type, content_name, content_ids for catalog optimization. TrackStack handles destination-compliant identity formatting at the edge. Dedup window: 48h.
• Google — sendTo for GA4 measurement IDs. transaction_id for conversion dedup. TrackStack handles GA4-compatible server payload shaping. Dedup window: 24h.
• LinkedIn — conversionRuleId for conversion rules. conversionValue with amount and currencyCode for value. Optional first-party click identifiers are supported through platform overrides.
• Reddit — Standard conversion events and custom labels. Use click_id for attribution.
• TikTok — contents array for product catalog. event_source_id for custom tracking.
• X — conversion_id for conversion tracking. Use value and currency for revenue events.
• Microsoft Ads — UET-style tracking (client-side). Configure via dashboard; keep UET tag and conversion goals in sync.
• Quora — Lead and purchase conversion signals. CAPI available.

Integration notes

• Prefer canonical event mappings first; add overrides only when your ad account requires them.
• Keep destination credentials in dashboard settings, never in client code.
• Validate mappings in API playground before production rollout.
• For Microsoft Ads, configure UET from the dashboard and monitor health status there.

Next steps

• B2B SaaS events — Canonical event naming and payloads
• SDK setup — Production integration patterns
• Integrations — Analytics, auth, payments, frameworks