Pingado and PostHog

PostHog is a product analytics suite. It can send events to ad platforms through its data pipeline destinations, and its marketing analytics imports ad spend, so both halves of ad tracking are there, built from events you capture in PostHog.

Checked against PostHog's documentation and the source of its ad destinations, 29 September 2026.

Where they differ

• Where conversions come from. A PostHog destination sends events you capture in PostHog, after you filter the stream down to conversions and map each field for each platform. Pingado takes trials and purchases from your payment provider, so the type, value and currency come from the payment itself, and leads from forms on your site.
• Browser and server. PostHog's destinations send from the server. Running each platform's browser pixel is up to you, and for the platform to count the pair once, your pixel code has to reuse PostHog's event ID. Pingado loads the official pixels for you and sends the browser and server copies of each conversion with one shared ID.
• Connecting accounts. For Meta, TikTok and Reddit, PostHog asks you to create an access token in each platform and paste it in. For Google it connects your account, and you create the conversion action in Google Ads yourself. In Pingado you connect each ad account from settings and map each conversion to an event or conversion action there.
• What each platform receives. By default PostHog's Meta destination sends no IP address, and its TikTok and Reddit destinations do not send the browser ID their own pixels set. Platforms use these to match a conversion to an ad click. Pingado keeps them for each visitor and sends them when the visitor allowed ad tracking.
• Joining spend to revenue. PostHog's marketing analytics matches campaigns to conversions by utm_campaign and utm_source. Pingado uses the click ID each platform adds to the ad click, with UTMs as a fallback.
• Timing. A PostHog destination reads person data as it is when the event is processed, so an email identified after the conversion is not sent. Pingado holds an unattributed conversion briefly and links the visitor from the order confirmation page.
• Maturity. PostHog's ad destinations are marked alpha in its source code, its documentation calls the Google Ads destination experimental and without official support, and marketing analytics is an opt-in beta.
• Ad platforms. PostHog has destinations for LinkedIn, Microsoft and Snapchat, which Pingado does not connect today.

If you don't use PostHog yet

• A whole analytics suite for one job. Sending conversions through PostHog means installing it, capturing conversion events, filtering the stream and mapping fields for each platform. Pingado is one snippet, plus connecting your payment provider and ad accounts.
• Conversions from the payment. Trial or purchase, value and currency come from your payment provider, not from events someone has to instrument correctly.
• Browser and server from the start. Pingado loads each platform's pixel and sends both copies of every conversion with one ID.
• Built for this. In PostHog the ad destinations are alpha and marketing analytics is a beta. In Pingado they are the core of the product, not an add-on.
• Price follows ad spend. Pingado is free up to $500 of monthly ad spend. PostHog is priced by usage across its products.

If you already use PostHog

Pingado sits next to PostHog, it does not replace it. It takes on the parts you would otherwise build and maintain yourself:

• Pixels and deduplication. PostHog sends from the server. Someone still has to run the Meta, TikTok, Reddit and Google pixels and make each one reuse PostHog's event ID, or the platforms count conversions twice.
• Conversions that match your payments. Unless you send your payment provider's events into PostHog and map them, a purchase is whatever the frontend captured. That can miss the charge after a trial, or carry the wrong value or currency.
• Match data by default. Pingado sends the visitor's IP to Meta, the browser IDs TikTok's and Reddit's pixels set, and Google's app and iOS click IDs (gbraid, wbraid), which PostHog's templates leave out.
• Attribution by click ID. One ad with a mistyped utm_campaign drops out of PostHog's spend report. Pingado matches on the click ID first.
• No late-identify gap. Pingado links a conversion to the visitor from the order confirmation page, even when the email becomes known after checkout.
• Platform upkeep. Ad platforms change their APIs and rules. PostHog's Reddit template calls Reddit's v2.0 Conversions API, while Reddit's current version is v3. With Pingado that upkeep is ours.

When PostHog is enough

• You already run PostHog and have engineers who will build and maintain the pixels, the event mappings and the deduplication.
• You advertise mostly on LinkedIn, Microsoft or Snapchat.

They can run side by side: PostHog for product analytics, Pingado for what goes back to the ad platforms.

Sources

• Google Ads destination, PostHog documentation
• Meta Ads destination, PostHog documentation
• Reddit Conversions API destination, PostHog documentation
• TikTok Ads destination, PostHog documentation
• Marketing analytics, PostHog documentation
• Ad destination templates, PostHog source code
• About the Conversions API, Reddit Ads Help

All comparisons

• Pingado and DataFast
• Pingado and the Meta app for Stripe
• Pingado and PostHog
• Pingado and server-side GTM
• Pingado and Stape