Attribution evidence
Live
Postback Engine
Accept operator and tracker events, match them to clicks or funnels, and preserve the evidence needed for reconciliation.
Postback Engine
/connect
/api/postback
rotator_postback_events
conversion_events
funnel_events
Route
Data
Bounds
Implementation map.
This scaffold only names routes, tables, RPCs, and APIs that already exist in the product code path.
Data map
- /api/postback
- rotator_postback_events
- conversion_events
- funnel_events
- campaign_postback_attribution
Workflow
- 1Receive signed postback payloads from operator or tracker systems.
- 2Match click ids, visitor ids, funnel ids, and campaign attribution where present.
- 3Feed analytics, billing, insights, and campaign review surfaces from the same event trail.
Bounded gaps
- Operator-specific template setup still happens per integration.
- Malformed or unsigned payloads stay diagnostic; they are not treated as payable events.
Claim boundary
The engine records and reconciles evidence; it does not guarantee operator-side approval.