PostHog as a destination

Use this when you want survey activity from getuserfeedback.com to appear in PostHog next to the rest of your product analytics.

Each enabled survey event is sent to PostHog's batch capture API. We use the event's userId first, then anonymousId, as PostHog distinct_id.

1. Create the integration

1. Open Integrations and click New integration.
2. Under Data out, choose PostHog.
3. Click Continue.
4. Enter your PostHog Project API key.
5. Choose the PostHog endpoint for your project:

6. Choose which events to send and how they should be named in PostHog.
7. Click Create integration.

The destination starts paused. Open the integration detail page, review the settings, then turn it on.

2. Send a test event

1. Open the PostHog destination in getuserfeedback.com.
2. Click Send test event from the actions menu.
3. Confirm the request succeeds.
4. In PostHog, open Activity or Events and look for the destination event name you configured.

What we send

Each PostHog batch item includes:

{"event": "Response Submitted","properties": {"distinct_id": "user_123","$insert_id": "msg_123","app_id": "app_123","organization_id": "org_123","response_id": "response_123","flow_id": "flow_123","page_path": "/survey","locale": "en-US"},"timestamp": "2026-06-21T00:00:00.000Z","uuid": "018f5d75-2222-5000-9000-abcdefabcdef"}

The request body also includes your PostHog project API key as api_key.

What can break

• PostHog rejects the request. Check that the project API key belongs to the selected PostHog project and that the endpoint matches your PostHog region.
• The event is skipped before sending. The event needs a userId or anonymousId so we can set PostHog distinct_id.
• You don't see the event in PostHog. Confirm the event is enabled in the destination settings and that the destination is turned on.

Next

• Event payloads
• Identity resolution