PostHog / PostHog/posthog

Simplified Retrieval of Converted People from Funnel Insights API

Open
#31,398 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
7h 27m
Merged PRs (30d)
222

Description

Feature request

Is your feature request related to a problem?

Yes. Previously, the PostHog Insights API endpoint for funnel insights included a convenient converted_people_url field in the results array, allowing us to easily retrieve the list of converted people by simply making a GET request to $json.result[i].converted_people_url. However, this field was removed in an API update over 6 months ago.

Without this field, retrieving converted people now requires a complex POST request to the query endpoint, significantly increasing complexity, particularly when using tools like Zapier or n8n.

Describe the solution you'd like

Restore or provide an equivalent simplified way to programmatically retrieve the list of converted people directly from a funnel insights API response, such as reintroducing the converted_people_url field or a similarly straightforward approach.

Describe alternatives you've considered

Currently, the only method recommended by PostHog support involves reverse engineering the UI request, requiring a complex query structure. For reference, the current UI sends a POST request to the query endpoint as follows:

{
    "query": {
        "kind": "ActorsQuery",
        "source": {
            "kind": "FunnelsActorsQuery",
            "source": {
                "kind": "FunnelsQuery",
                "series": [
                    {"kind": "EventsNode", "name": "Signed Up", "event": "Signed Up"},
                    {"kind": "EventsNode", "name": "Status page created", "event": "Status page created"},
                    {"kind": "EventsNode", "name": "Status page activated", "event": "Status page activated"}
                ],
                "dateRange": {"date_from": "-30d", "explicitDate": false},
                "properties": {"type": "AND", "values": []},
                "funnelsFilter": {
                    "layout": "horizontal",
                    "exclusions": [],
                    "funnelVizType": "steps",
                    "funnelOrderType": "ordered",
                    "funnelStepReference": "total",
                    "funnelWindowInterval": 14,
                    "breakdownAttributionType": "first_touch",
                    "funnelWindowIntervalUnit": "day"
                },
                "breakdownFilter": {"breakdown_type": "event"},
                "filterTestAccounts": true,
                "aggregation_group_type_index": 0
            },
            "funnelStep": 3,
            "includeRecordings": true
        },
        "select": ["actor", "matched_recordings"],
        "limit": 100
    },
    "refresh": "blocking"
}

This approach is overly complex, making automation or integration cumbersome, especially for no-code or low-code environments.

Additional context

We've discussed this issue with PostHog support. They suggested opening this GitHub issue to formally document our need for a simplified solution.

Thank you for considering this feature request!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the funnel insights API endpoint and the query endpoint used for retrieving converted people, then compare their current response and request shapes with the historical converted_people_url behavior described here. Done means the API provides a documented, straightforward programmatic way to retrieve converted people from funnel results without requiring the complex UI query.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
analytics, api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.