How to Request Your PostHog Owner to Configure the Unify Integration

Last updated: April 2, 2026

Overview

Setting up the PostHog → Unify integration requires a small action from your team’s PostHog owner (typically a Data PM, Front-End Engineer, or Analytics Manager). This article gives you everything you need to make that request — and make it easy for them to say yes.

Setup time: less than 30 minutes!

Before you send the request

Before looping in your engineering contact, make sure you have:

  1. Your top 3–5 events identified — the specific product signals most relevant to your GTM motion (e.g., paywall_hit, upsell_flow_started, teammate_invited). Work with your Unify PGS if you need help narrowing these down.

  2. The integration docs link — PostHog Integration Docs

  3. Your Unify routing key — found in Settings → Integrations → Web & Product Data in Unify. You’ll include this in your message so your PostHog owner can paste it directly into the destination setup.

Template: Message to send your PostHog owner

Copy, fill in the brackets, and send directly — via Slack, email, or however your team communicates:

Subject: Quick setup: connecting PostHog to Unify

Hey [Engineering Contact],

Our GTM team has been working with Unify (our outbound platform) and they’ve built a native integration that lets us trigger GTM actions from our product events.

To get started, we need to forward events like [x, y, z] from PostHog to Unify. Here’s the setup guide: PostHog integration docs

Here’s our Unify routing key to paste in: [your routing key from Unify Settings]

It should take under 30 minutes. It’s enabling a forwarding destination in PostHog, not building a new pipeline. The Unify team is available if you hit any snags.

This will be valuable because [e.g., “we’ll automatically reach out to free users the moment they hit their credit limit instead of finding out a week later”].

Thanks!

What your PostHog owner will do

Once they receive your message, here’s what the setup looks like on their end (share this with them if helpful):

  1. In PostHog, navigate to Data & Destinations.

  2. Find the Unify destination and select it.

  3. Paste in the routing key you provided.

  4. Click Create and Enable.

  5. Use Event Matcher to select only the specific events to forward to Unify (e.g., paywall_hit, upsell_flow_started). Add filters to exclude internal users.

  6. Click the Test Function button (green icon = success) to confirm the connection.

Events will start flowing into Unify within ~5 minutes of the destination being enabled.

After the integration is live

Once events are flowing, your Unify PGS will help you:

  1. Validate in the Event Console (Data → Event Console) that the right events are arriving and attached to the correct contacts.

  2. Build your first Plays using the product events as triggers.

  3. Create Audiences based on product behavior for prospecting and campaigns.

Troubleshooting tips for your PostHog owner

Issue

Fix

Events not showing up in Unify

Confirm the forwarding destination is enabled and that real activity is firing on the instrumented pages/flows

Events not attached to people in Unify

identify() calls are required — these must fire on login or form submission so Unify can link events to known contacts

Duplicate events

Confirm events are only being forwarded from one source per event type (not both PostHog and Segment)

If issues persist after 15–20 minutes, the Event Console in Unify is the best place to debug. Your Unify PGS can also join a short call with your engineering contact if needed.

Resources