Postbacks
Postbacks in the Marketing area (Attribution) — route /marketing/postbacks.
Postbacks lives in the Marketing area of the dashboard, under Attribution.
At a glance#
| Dashboard route | /marketing/postbacks |
| Area | Marketing (marketing) |
| Group | Attribution |
| Platforms | Mobile apps only (iOS, Android, React Native, Flutter). Hidden for web apps. |
What it does#
The partner postback delivery log, in both directions:
Outbound — accepted events forwarded to the partner that drove the install, so the network can attribute and optimise.
Inbound — postbacks received from partners.
Each row shows what was sent or received and when.
When to use it#
When a network says it is not receiving your conversions, and when a network's optimisation is underperforming for no visible reason. Ad platforms optimise against the conversions you send them; a partner receiving no post-install events can only optimise for installs, which is why campaigns sometimes deliver volume and no value.
This log is how you prove which side the gap is on.
Workflow#
Confirm outbound deliveries exist for the events you care about
If your purchase events are not being forwarded, the network is optimising blind.
Check what is mapped
Which of your events reach which partner is configured on Partner event mapping. An unmapped event is never forwarded.
Read failures, not just successes
A failed delivery is a conversion the partner does not know about.
Compare counts with the partner's own dashboard
Where they differ, the log tells you whether you sent it.
Permissions and prerequisites#
Requires a connected partner and event mappings. Only accepted events are forwarded — an event rejected at ingestion never reaches a partner.
Limits and edge cases#
Only attributed installs get outbound postbacks. An unattributed install has no partner to notify.
Delivery is best-effort with retries; a partner outage can produce failures that are not your fault.
Partners deduplicate on their own terms, so their count may be lower than your delivery count legitimately.
Web uses a different mechanism — see Server conversions.
Troubleshooting#
No outbound rows for an event. It is not mapped to that partner, or the install was never attributed to them.
Deliveries succeed but the partner reports nothing. Check their expected event names — a mapping can deliver successfully to the wrong event name.
Where the data comes from#
Only accepted events are eligible for forwarding, and only for installs attributed to that partner.
Served by
Tracking