Each automation says what success means: purchases, attendance, resolution or engagement. For purchases, Trybe claims revenue when its code is redeemed or a link is clicked, and shows inferred sales separately.
Four goals: Purchases, Attendance, Resolution, Engagement
Certain revenue: a promo code minted by the run, or a link that was clicked
Inferred purchases within 7 days shown separately, never mixed in
Per currency, never summed; unknown shows as “—”, never as 0
Every send is also a campaign: delivered, opened, clicked, purchased
Automation revenue attribution tells organizers and promoters which automations actually produced sales, and refuses to guess. Each automation declares what success means, Purchases, Attendance, Resolution or Engagement, and only the goals it can really measure are offered. For purchases, Trybe claims revenue in tiers. Certain: a promo code the run created for that person was redeemed, which claims the whole order, or the person clicked a link in the message before buying. Inferred: the person bought a ticket to the event after the message, shown separately with a note. The window is 7 days from the send, capped at the event start, and editable. Revenue is shown per currency and never summed across currencies; when Trybe doesn't know, it shows “—”, never 0. Every automated send also runs as a campaign, so you get delivered, opened, clicked and purchased for each step, plus a per-run trace. Conversions are counted per automation, so a fan who sits in two automations and buys once counts for both. Attribution needs tickets sold on Trybe, since orders are counted at Trybe checkout.
Pick Purchases, Attendance, Resolution or Engagement, or let Trybe derive it from how the automation is built.
Each run records the promo code it minted, the tracked links it sent and the person it reached.
An order that redeems the code or follows a click is certain; one that merely follows the message is inferred and shown apart.
The automation page shows revenue, conversions and tokens spent, per currency, with “—” wherever Trybe cannot be sure.
In tiers. Certain: a promo code created by that run was redeemed, or a link in the message was clicked before the purchase. Inferred: the person bought the event within the window after the message, shown separately so you can judge it yourself.
7 days from the send by default, and never after the event starts. You can change the window per automation.
Because “—” means Trybe doesn't know, while 0 would mean it checked and found nothing. Engagement-only automations, for example, are never measured on revenue.
Purchases (did they buy?), Attendance (did they show up?), Resolution (was the request handled?) and Engagement (delivered, opened, clicked, nothing more claimed). Only goals the automation can actually measure are offered, and the goal changes what is measured, not what the automation does.
Yes. Conversions are counted per automation, so a person who went through two automations and bought once appears in both, and the column is not meant to add up. When one of your own campaigns and an automation both reach the same buyer, the campaign gets the credit.
Yes. Orders are counted at Trybe checkout, so revenue and purchases only appear for events ticketed on Trybe. For events sold elsewhere through Launches, automations still report delivered, opened and clicked.
Flows that run on their own when fans follow, buy, abandon a cart or have an event coming up
Percentage or fixed discounts with limits, dates and tier targeting, shareable as a link that applies the code
For every token spent, what a campaign earned: revenue over time, average order value, revenue per recipient
Free for organizers hosting on Trybe. No credit card, two-minute setup, works in English and French.