conversion-tracking

Track Stripe webhook conversions by sourcing paid-lifecycle events and shipping them to PostHog, which then forwards the conversion events to Meta Ads and Google Ads via destinations. This unifies payment data with ad platform attribution.

Deterministic deduplication for conversion tracking works by enforcing unique dedupe keys on every event. This ensures analytics remain reliable by preventing duplicate records from webhook retries or multiple in-app route actions.

Yes, you can capture in-app user lifecycle events alongside Stripe paid conversions. Tracking code is centralized in tracking/.server and browser namespaces to unify both event classes into PostHog with correct team and project grouping.

The best way to attribute PostHog events to Meta Ads and Google Ads is by using PostHog destinations to forward the unified conversion events. This end-to-end workflow supports proper attribution and downstream ad-platform delivery.

Yes, conversion tracking supports backfilling historical paid-lifecycle events. The attribution model maintains timestamp accuracy from original event times and attaches team and project groups during the backfill process.

Conversion tracking instrumentation uses fire-and-forget error handling with try/catch blocks to keep user actions fast. This ensures analytics tracking never blocks application performance or disrupts the user experience.