Funnels

Funnels let you define ordered steps (a journey) and see how many players complete each step in sequence within a conversion window. In the PlayerAtlas web app, open Affiliate → Funnels (URL pattern: /p/<projectId>/affiliate/funnels).

Funnels are a Pro feature. If your plan does not include them, the dashboard shows an upgrade prompt instead of the funnel editor.

What a funnel measures

• Players enter when they satisfy step 1 during the chosen time range.

• Each next step counts only players who already completed the previous step in order, and whose next step occurs within the conversion window after the previous step’s time.

• You see drop-off and conversion rates between steps.

Conversion window

The conversion window is how long a player has to move from one step to the next. You can set it between 60 seconds and 90 days (in seconds in the underlying definition).

Step types

You can mix these step kinds in one funnel:

Kind	Meaning
First session	A player’s first session on a server (optionally filtered by campaign and/or server).
Custom event	A custom event with a given eventKey. Optional filters: specific servers, and parameter filters on event properties.
Payment	A payment recorded for the project (optional campaign filter, optional minimum value).

Custom event steps

• Event key must match the same naming rules as event keys.

• Server IDs (optional): limit the step to events from selected servers.

• Parameter filters (optional, up to 16): restrict by property key with operators equals, not equals, greater than or equal, less than or equal, or contains (string). Filter keys use letters, numbers, and underscores only.

Labels and IDs

Each step has a label (shown in the UI) and an id (stable identifier). The definition format uses version 1 and supports 1 to 8 steps.

Sending events for funnel steps

• Custom event steps use the same events your game servers send via Using Java API or Using Commands.

• First session and payment steps use data the platform already records (sessions and store integrations).

Tips

• Name eventKey values consistently across environments so funnel steps match production data.

• Use parameters on custom events when you need to split funnels by difficulty, product tier, or similar (via parameter filters on the custom event step).