How attribution works
Tamari credits each signup and activation to the DevRel activity that came before it, and says plainly when it cannot.
One developer, many identifiers
A developer can show up as a visitor ID from the snippet, a GitHub account, a Discord account, an email address and your user ID. When two of these arrive together, for example in an identify call, a signup with an email, or Discord's /connect, Tamari links them to one developer. Records that turn out to be the same person are merged. Matching is exact: Tamari never guesses that two similar identifiers belong together.
Page views from a visitor who has not been linked to anyone yet are kept, and credited once the visitor is identified.
What counts as a touch
For each signup or activation, the touches are the same developer's activities inside the attribution window before it: page views, GitHub and Discord activity, event registrations and attendance. Activity at the same moment or after does not count. Product events you send, such as an earlier signup, are not touches.
The window is 90 days by default. Owners and admins can set it from 1 to 365 days in Settings.
Models
Every conversion is credited under four models. Each splits exactly one conversion between its touches.
| Model | How credit is split |
|---|---|
| First touch | All of it to the earliest touch |
| Last touch | All of it to the latest touch |
| Linear | Evenly across every touch |
| Time decay | More to recent touches: a touch loses half its weight every 7 days (the half-life, 0.5 to 90 days in Settings) |
Content, Sources and Events let you switch models. The monthly report ranks top content and the top event by activated developers under linear attribution.
Match rate
The match rate is the share of signups with at least one touch in the window. Signups without one are counted as untraced. They get no credit, and Tamari does not estimate where they came from. The report calls a month's numbers reliable when the match rate is 70% or higher.
To raise it, make sure signups carry an identifier Tamari has seen before: an email, a GitHub username, or the user ID passed to identify.
When numbers change
Credit is recalculated as soon as a related event arrives, including late events and merged developers, and again every night. Changing the window or half-life applies to all conversions within minutes.