Guides
Attribution
How shown, clicked, dismissed and converted are recorded and credited.
Every decision fetched gets a row in the decision log with a logId. These outcomes are recorded against it.
Outcomes#
| Outcome | Meaning | Sent by |
|---|---|---|
shown | The message rendered. This is the serve that is billed and capped. | SDK components, or you |
clicked | The user pressed the button. | POST /feedback |
dismissed | The user closed it. | POST /feedback |
converted | The user reached the goal afterwards. | Tug, automatically |
How conversions are credited#
A serve converts when the user fires the goal's target event with an occurredAt at or after the moment it was shown, within 30 days. Tug records it right after the event is stored.
- Serves that were fetched but never shown don't count.
- Backfilled events from before the showing don't count.
- The latest such serve per message gets the credit, in whichever group the user is in (shown the message, or held back).
Where to see results#
Per-message stats (shown, clicked, converted, and the message against its holdout) are on Recommendations. The project overview has 7-day serve, click and convert totals.