Product
OverviewHow the layer sits on top of your ticketingStubs and momentsWhat the object is and how it reaches fansSets and rewardsWhat makes fans attend a second eventSponsorshipsVerified actions in place of impressionsTicketingSDK and primary, when you want itPartners
IntegrationsWhat we plug into, and what is in progressOperatorsWho runs on stubs.fun todayProof
Case studiesWhat happened at real eventsStart a pilotWhat a first season includes, and what it asksAbout
AboutWho builds this and whyYour greatest moments, here.
Fans own the moments they were there for. You own the reason they come back.
The event ends. The relationship does not.
Most events send fans home with a scanned QR code and nothing else. A stub turns the hour after the final whistle into the start of the next event.
Every attendee gets one to claim. Claiming is the point: it is how a fan takes ownership of a night they were actually at, and it puts them ahead of everyone who was not.
Fans tap to reveal what they got. Each stub draws across six tiers. The reveal is what makes it worth opening, and the tier decides what sits behind it.
Points and rewards carry forward. Status accumulates across events instead of resetting at the gate, so showing up twice is worth more than showing up once.
Sets create the reason to come back. A missing stub is held by somebody who went to the night your fan skipped. Completing the set is what opens the real reward.
Attendance is the only way in.
A stub is a souvenir. A set is a season-long reason to keep showing up, keep the ticket, and chase the reward before somebody else does.
Six tiers. One of them is the only one.
Every event issues the same six tiers in its own images, and the 1 of 1 exists a single time.
Every tier carries points, a reward, or access. You set what sits behind each one and how often it drops, and we publish that distribution to fans before the first stub is claimed.
What this does to a season.
Three charts, all drawn from the figures you put in below, so nothing here is our number pretending to be yours.
Claim rate is the lever, and it is a decision rather than a constant. A QR code nobody points at converts in single digits. Staff the activation and it multiplies. Issue the stub with the ticket and holding one stops being something a fan has to go and do.
You do not have an attendance problem. You have it on some nights.
Sorted highest to lowest, every season looks like this. The top dates are full and the bottom of the list is the part nobody has a lever for.
The empty seats are already yours. Nothing has to be bought to use them.
capacity − average attendance, times home games. The curve is illustrative. The total is not, and it does not depend on the curve.
Every claimed stub is a named fan you keep.
A ticket ends when the game does. A stub stays in a wallet with a person attached to it, and the count only goes one direction across a season.
This is the figure a rights holder can price, because every point on the line is a person and a placement rather than an estimate.
Then they start trading to finish the set.
A fan one piece short of a set goes looking for it. That is the pressure the set design creates, and trading is how you see it happening.
An assumption until a season runs. The price below is yours to set, because a real market has not set one for your building yet.
Totals are yours. The game by game shape is an even distribution scaled to the average you entered, because we do not have your manifest yet. Send three dates and we will run it on the real one.
No athlete, no moment.
They are the reason the night was worth being at. Give them a page of their own and the audience that follows them starts arriving at yours.
Athletes post because the page is theirs and the moments carry their name. You get the traffic without running the account, writing the captions, or paying for the reach.
Every athlete gets a page
Their own page inside your event, with their moments on it. They post to it the way they already post everywhere else.
Their following shows up
The audience an athlete brings is one you have never been able to reach through a ticketing email. It arrives because they posted, not because you bought it.
The noise is measurable
Threads, holders, and volume on their page. You can see which athletes actually move people and which ones just have followers.
It lands back in your building
Every route out of a page ends at your next home game, because the moments they are posting about only exist if someone attends.
The placement a fan has to finish to reach.
A sponsor rides the stub, funds what sits at the end of the set, and gets a count of everyone who got there.
Branded stubs
Sponsors sit inside rivalry games, promotional nights, and milestone events that fans want to keep.
Fan-amplified reach
Shared stubs carry the sponsor into social feeds, group chats, and fan groups on their own.
Measurable engagement
Claims, opens, clicks, shares, and redemptions, all attributable to the placement.
Longer sponsor value
The placement keeps running through saved stubs and everything fans do with them later.
Turn every moment into a revenue engine.
Keep the ticketing provider you already use and add fan engagement on top of it. We handle setup, distribution, and optimization, so nobody on your side has to run it.
- Moments free to distribute across your entire first season
- SDK or hosted deployment
- Moments, rewards, and messaging included
- Community page with marketplace, rewards, and engagement
- Dedicated team to launch and optimize the pilot
We partnered with Ticket Tree because we share the same mission, to give the fans a better experience.
Which stub will be yours?
A place your fans come back to
Every event issues a moment worth claiming. Sets pull fans across your calendar. Trading, rewards and a page of their own all sit on a site that carries your name, and none of it asks you to change how you sell tickets.
What we build, and when.
The community page, the set design and the distribution are ours to build and ours to tune. The reward at the end is the one call you make.
CommonUncommonRareEpicLegendary1 of 1You received a stubYou received a stubYou received a stubProven where fandom runs hottest.
This was built and proven in high intensity events where fandom runs deep, on nights people still argue about afterwards. A season calendar gives the same mechanic more to work with.
A page with your name on it.
Your own address, your own community, and a marketplace running on inventory you already own.
Not a ticketing switch
You keep the provider you already use. We read attendance and write nothing back, and the claim route works even before that connection exists.
A page fans return to
Their moments, the sets they are chasing, the rewards in front of them and the people they can trade with. Open in a browser, or in the app if they want it on their home screen.
A line on your revenue
Every trade runs through a marketplace on your own inventory, and five percent of the fee comes back to you. That is before a sponsor has paid you anything.
See it against one of your own events.
Send us a past event and we will show you what the stub, the set, and the reward would have looked like for it.
- Moments free to distribute across your entire first season
- SDK or hosted deployment
- Moments, rewards, and messaging included
- Community page with marketplace, rewards, and engagement
- Dedicated team to launch and optimize the pilot
We partnered with Ticket Tree because we share the same mission, to give the fans a better experience.
IRL moments, owned by fans
A stub is proof they were there, and then it keeps going. Something they own outright, in the images from that specific night, that they can hold, trade, and come back to for as long as they care about your program.
Every tier carries points, a reward, or access. You set what sits behind each one and how often it drops, and we publish that distribution to fans before the first stub is claimed.
Claimed, then revealed, then kept.
The stub arrives face down. The reveal is the moment worth having, and what happens after it is the reason anyone comes back.
Theirs to own
Not a receipt and not a badge. It sits in their collection, it carries the seat and the date, and it cannot be bought by somebody who was not in the building.
A living asset
It gains a place in a set, a value in a marketplace and a story once the season is over. A ticket stops working at the gate. This one is still doing something in June.
A reason to talk
Fans trade with the people who were at the nights they missed. That trade is the introduction, and the community is what it turns into. You decide whether trading is on at all.
Put your greatest moments on it.
Send one event's photos and we will build the six tiers so you can see your own night on them before you commit to anything.
- Moments free to distribute across your entire first season
- SDK or hosted deployment
- Moments, rewards, and messaging included
- Community page with marketplace, rewards, and engagement
- Dedicated team to launch and optimize the pilot
We partnered with Ticket Tree because we share the same mission, to give the fans a better experience.
A rewards destination for inventory nobody uses
One stub is a souvenir. A set is a destination. Every seat you did not sell, every upgrade nobody bought and every experience a sponsor can open a door to now has somewhere to go, and a reason a fan works toward it.
Complete the set. Claim the reward.
Stubs group into sets. Finish one and the reward behind it opens. The stubs a fan is missing are held by the people who were at the events they skipped.
What a set looks like once you build one.
Winter series
Five stubs across three of your sports
Student section
Four stubs, home games only
Rivalry week
Three stubs, one weekend
Completion states here are illustrative. The sets, the spread, and the reward behind each one are yours to set before the first stub goes out.
Two kinds of inventory, both of them idle.
You are already sitting on the first kind. Your rights holder and your sponsors are sitting on the second. Neither has had anywhere useful to put it.
Inventory nobody bought
Empty seats on a Tuesday, upgrades that never sold, presale windows, tunnel access, a place on the field before warmups. It costs you nothing you were going to earn, because nobody was buying it.
Experiences only a brand can open
Product a category sponsor already makes, gear with their mark on it, an experience their budget can unlock. They fund it because completion is the only way to reach it, and every fan who does is a name they get back.
The reward decides whether the set works.
Cheap for you
Seat upgrades, presale windows, and early access cost inventory you already control, not cash.
Scarce for them
A reward available to everybody is not a reward. Completion has to be the gate.
Visible before they start
Fans need to see the reward on day one. A surprise at the end does not drive a second ticket.
Pick one reward and one set.
Three games is enough to watch a set form and a fan come back for it. The reward can be something you already own and were never going to sell.
- Moments free to distribute across your entire first season
- SDK or hosted deployment
- Moments, rewards, and messaging included
- Community page with marketplace, rewards, and engagement
- Dedicated team to launch and optimize the pilot
We partnered with Ticket Tree because we share the same mission, to give the fans a better experience.
How this pays without touching your rights deal
Frictionless inventory for rights holders, high value placement for brands. A logo on a stub does not come down at the end of the night. It is a living asset fans hold, trade and show each other for years, and owning a placement inside that is worth more than owning a wall.
A placement a fan has to finish to reach.
Signage is seen. This is used. The category sponsor rides the stub, funds the thing at the end of the set, and gets a count of who reached it.
Their mark rides the stub
The stub is the thing a fan keeps. The placement stays on it long after the night the ticket was for.
They underwrite the set
Their category is attached to the whole set, so the brand is present at every claim a fan makes on the way to finishing it.
The reward is theirs to give
Completion opens something the sponsor funds or you already control. The redemption is the receipt, and it is attached to a name.
They buy one placement. A category sponsor takes a season, the way they would take signage.
It rides every stub issued. Not one wall in one building. Every moment that leaves the event carrying their mark.
Every one lands with a name. Held, opened and kept by a person you can identify, not an impression you estimated.
And it keeps moving. Traded, gifted and resold for years. The placement goes with it, and so does the record of who is holding it.
You own the inventory
The stub is yours. If your rights holder controls an asset, we do not touch it.
The placement outlives the event
Fans keep stubs and show them to people. A printed ticket stops working at the gate.
Every action is attributable
Claims, opens, shares, and redemptions, each tied to the placement that carried them.
No inventory we can resell
We do not broker, package, or resell your sponsor slots. The relationship stays yours.
Verified actions, not estimated impressions.
| Printed ticket | Sponsored stub | |
|---|---|---|
| Impressions | Estimated | Counted |
| Who saw it | Nobody knows | Named fan record |
| Actions after the event | None | Opens, shares, redemptions |
| Reported back | Not reported | Per event, per placement |
Rates and mechanism only. We do not publish a per-event sponsor figure, because the right number depends on your market, your attendance, and what your rights holder already controls.
How many verified actions is a season worth.
We are not going to hand you our figure and call it yours. Put in your attendance, pick how you would run the claim, and see what a verified action would have to be worth to you.
A verified action is a named fan who opened a stub, redeemed an offer, or came back for a second event. Every one of them is attached to a person and a placement, which is the part your rights holder can price.
The report your partnerships office carries into a renewal.
Impressions are why renewal conversations stall. A named fan who opened a stub, redeemed the offer and came back for a second game is a different kind of sentence, and it is the one that renews a category at a higher number.
Renewals
Walk in with what the placement actually did rather than what the model estimated it might have done.
New categories
A brand that has never bought signage will buy a verified action, because it is the only thing on your rate card that behaves like the rest of their spend.
Proof mid-season
Fan records persist, so a partner can see what happened in February instead of waiting for a wrap report in June.
Every claim, open and redemption, attached to a name.
Season to date, on the attendance and mechanism you set above. The shape is the point: the audience a sponsor bought does not reset when the night ends.
| Home game | Claims | Opens | Redemptions | Season to date |
|---|
Bring a sponsor who wants proof.
Run one event with a placement inside the stub and hand them the actions report afterwards.
- Moments free to distribute across your entire first season
- SDK or hosted deployment
- Moments, rewards, and messaging included
- Community page with marketplace, rewards, and engagement
- Dedicated team to launch and optimize the pilot
We partnered with Ticket Tree because we share the same mission, to give the fans a better experience.
The fan identity layer for live events
Unifying ticketing, fan data and social gaming into one revenue engine teams own. Ticket Tree preserves the full chain of custody across issuance, transfer, secondary markets, redemption and post-event fan activity.
One place for the whole calendar.
Events, tickets, fans, sponsors and attendance in one workspace. Every number on it is the same fan record, so the finance view and the audience view stop disagreeing with each other.
Identity at three depths.
Every one of these resolves a fan. What changes is how early in the journey we can do it, and how much of the revenue that fan generates stays inside one system.
Drop-in checkout for any stack.
A script tag and a container. The widget mounts checkout inline, keeps the buyer on your page, and writes to the same event record the dashboard reads. No redirect, no rebuild, no migration.
- Mounts on a CMS, a static page, or a framework
- Inline or popup, with an optional confirmation redirect
- Drops to a plain iframe where scripts are locked down
1<script src="https://embed.tickettree.us/widget.js" async></script>2 3<button data-tickettree4 data-org-id="YOUR_ORG_ID"5 data-event-id="YOUR_EVENT_ID">6 Buy tickets7</button>1<script src="https://embed.tickettree.us/widget.js" async></script>2 3<div data-tickettree-inline4 data-view="event"5 data-org-id="YOUR_ORG_ID"6 data-event-id="YOUR_EVENT_ID"7 data-confirmation-url="/thank-you"></div>1TicketTree.init({2 mode: 'inline',3 container: '#tickettree-inline',4 orgId: 'YOUR_ORG_ID',5 view: 'event',6 eventId: 'YOUR_EVENT_ID',7});1<!-- if the host site cannot run javascript at all -->2<iframe3 src="https://embed.tickettree.us/embed/checkout?orgId=YOUR_ORG_ID&eventId=YOUR_EVENT_ID&view=event&display=inline"4 width="100%" height="720" loading="lazy"></iframe>The engagement layer, not just the checkout.
Most ticketing stops at the transaction. The reason a fan shows up early, comes back, or brings somebody happens before and after it.
Polls before checkout
Ask the room who they want to see, then let them buy. The vote is the reason a fan opens the page early, and every answer lands on the fan record.
Guest list, waitlist, presale
Invites, a waitlist for the night that sold out, and presale codes for the people who earned them. One list, and it stays yours.
Tracking links
A link per channel, so you know which post sold the ticket rather than guessing. Views, sales and conversion per source.
The people promoting you, on commission.
Send one application link. Approve who you want, set the rate, and everyone gets their own link and a running ledger. A tracking link tells you which post sold the ticket. An affiliate has a reason to keep posting.
| Affiliate | Rate | Sales | Commission | Tickets |
|---|---|---|---|---|
| A. Reyes | 10% | $2,140 | $214.00 | 26 |
| Campus Radio | 10% | $1,455 | $145.50 | 18 |
| J. Whitfield | 12% | $980 | $117.60 | 12 |
| 21 more affiliates | $7,905 | $806.90 | 94 |
Rates are yours to set and yours to change, per affiliate or once across the whole event. Your revenue and your incentive structure, with full control of both. Figures shown are illustrative.
Ticketing and moments together is the revenue engine.
Two systems means two half-pictures. One system means every ticket, every claim, every trade and every redemption is priced off the same fan, and the ceiling moves.
You can finally see who came back.
Every sale in the shape of your season, split by the one thing a ticketing report cannot tell you. Whether the buyer had been there before.
| Event | New fans | Repeat rate | Tickets |
|---|---|---|---|
| FB/football/home opener | 3,104 | 38% | 12,480 |
| MBB/basketball/rivalry night | 1,290 | 71% | 6,215 |
| WSOC/soccer/senior night | 640 | 44% | 2,870 |
| BSB/baseball/midweek | 212 | 29% | 944 |
Illustrative shape, not a customer report. Repeat rate is the share of a night's crowd that had attended at least one earlier event in the same season.
Build, compare, send.
Pick the metrics you need, add past events for a side by side read, and generate. Export to CSV or push it into Google Sheets without leaving the dashboard.
Pick what goes in it. Ticketing, express registration, attendance and sponsors, chosen per report and changed before you generate.
Compare against any past event. Anything on your calendar, read side by side instead of one event at a time.
Send it to anyone. A CSV, a live Google Sheet, or a link the rest of the staff can open. Build report sits in the event menu, next to embed and QR.
If you do move, this is what moves with you.
Not a lighter version of what you run now. The parts an operator actually leans on, on event night and in the week after.
Seat level inventory. Real charts and seat identity, several configurations per venue, reserved and general admission in one build.
Box office and scanning. Day of sales, will call and gate scanning that has cleared a full house inside an hour.
Controlled resale. Resale on your own inventory, so you earn on it and the buyer arrives as a fan record instead of a stranger.
Fans, not orders. One record per person across every event they have ever attended, which is the thing a set and a sponsor both run on.
The case, without the hedging.
Every provider sells tickets. The difference shows up in the eleven months of the year when you are not selling any.
Your provider stores orders
An order is a transaction that ends. A fan record is a person who has been to nine of your events and can be reached before the tenth. We built on the second one.
Resale happens either way
The only question is whether it happens on your inventory or somebody else's. On ours you earn on it and the buyer arrives as a name you already hold.
Two systems is the tax
Ticketing in one place and engagement in another means reconciling them forever. On one system attendance needs no import, because it never left.
And the part that has not changed: a pilot never touches your ticketing agreement, your fees, or your rights deals. You can run stubs for a full season without moving anything.
See it against what you run now.
Send us a season off your current provider and we will show you the same calendar on ours, reconciled.
- Moments free to distribute across your entire first season
- SDK or hosted deployment
- Moments, rewards, and messaging included
- Community page with marketplace, rewards, and engagement
- Dedicated team to launch and optimize the pilot
We partnered with Ticket Tree because we share the same mission, to give the fans a better experience.
Will this break what I run
No. We read attendance and write nothing back. If the connection ever goes down, your ticketing keeps running and stubs go out late.
It reads. It does not write.
Attendance comes out of the system you already run, a stub goes to the fan, and nothing travels back the other way.
Whatever you sell tickets on, this sits on top of it.
Connected means attendance flows today. In progress means we are building the direct connection and run a scheduled export until it lands. These are the systems we read, and none of them is a partnership claim.
Where every connection actually stands.
| Provider | Status | How |
|---|---|---|
| Ticket Tree | Native | Attendance, orders, and fan records. |
| Ticketmaster | Works today | Attendance via scan export. |
| Eventbrite | Works today | Direct API. |
| AudienceView | Works today | Direct API. |
| Paciolan | In progress | Scheduled export in the interim. |
| Hometown Ticketing | In progress | Scheduled export in the interim. |
| Tixr | In progress | Scheduled export in the interim. |
| Jump | In progress | Scheduled export in the interim. |
| Vivenu | In progress | Scheduled export in the interim. |
| CSV or scan export | Works today | The fallback for anything else. |
If your provider is not here, ask. We will tell you where the connection really stands rather than saying yes and finding out later.
Tell us what you run.
We will confirm the connection before you commit to anything.
- Moments free to distribute across your entire first season
- SDK or hosted deployment
- Moments, rewards, and messaging included
- Community page with marketplace, rewards, and engagement
- Dedicated team to launch and optimize the pilot
We partnered with Ticket Tree because we share the same mission, to give the fans a better experience.
Who else does this
Colleges, promotions, and independent leagues, mostly in the northeast, mostly running between 8 and 40 events a season. The rooms differ. The mechanic does not.
The numbers below came from combat sports, a touring show, and a waterfront festival, because that is who ran it first. An athletics department is the easier version of the same problem: more events, more sports, one calendar, and a set that can span all of it.
"We partnered with Ticket Tree because we share the same mission, to give the fans a better experience."
Mike, Founder and CEO, Cage Titans
Different rooms, same mechanic.
Cage Titans
Regional combat promotion
WWE NXT
Touring show, Plymouth Memorial Hall
Sail4th 250
Five days, 15+ locations citywide
Join them for one event.
Every operator on this page started with a single pilot.
- Moments free to distribute across your entire first season
- SDK or hosted deployment
- Moments, rewards, and messaging included
- Community page with marketplace, rewards, and engagement
- Dedicated team to launch and optimize the pilot
We partnered with Ticket Tree because we share the same mission, to give the fans a better experience.
Did it work
Three operators, three different problems, none of them a college. The numbers below are theirs, and the mechanic underneath them is the one that spans a department calendar.
WWE NXT
A touring show with no local list. The stub was the only thing that turned a one-night crowd into records the venue still has.
Cage Titans
Eleven events across a season. Sets ran across the whole card, so a fan who missed a night could see exactly what they were missing.
Sail4th 250
The largest American celebration festival in history, run across 27 events over five days and more than 15 locations around the city, powered end to end by us. The stub gave a free festival a reason to collect contact details people actually gave, at a scale most ticketed events never reach.
Ask us for the one that looks like you.
We will put you in touch with the operator directly rather than reading you their numbers.
- Moments free to distribute across your entire first season
- SDK or hosted deployment
- Moments, rewards, and messaging included
- Community page with marketplace, rewards, and engagement
- Dedicated team to launch and optimize the pilot
We partnered with Ticket Tree because we share the same mission, to give the fans a better experience.
Turn every moment into a revenue engine
Keep the ticketing provider you already use and add fan engagement on top of it. We handle setup, distribution, and optimization, so nobody on your side has to run it.
Book a demo.
Twenty minutes, screen shared, your programs on it. You do not need numbers, a provider answer, or an internal decision to sit through one.
Got it.
Almost nothing you do not already have.
Three games is the whole commitment. Everything below either already exists inside your building or costs you nothing to hand over.
A scan export or a CSV after each game is enough to start. Our team runs the ingest and the activation around it, so none of it lands on your staff.
The photos already on your camera roll. The shot everyone remembers from that night is the one worth owning.
Seats, access, a presale window. It does not have to cost cash, and it is the thing the whole set is built toward.
Read only, and it replaces the file step entirely. Worth doing once you know this works, and never a condition of starting.
Any category partner sitting on inventory they would rather move than waste, or an experience only they can open a door to. They fund the reward, you keep the relationship, and the placement rides every moment issued.
The file route exists so nothing has to be scheduled with your provider before you know whether this works. If you would rather connect your ticketing on day one, we can do that instead.
Three things a pilot does not cost you.
Your ticketing
Unchanged. We read attendance and write nothing back.
Your sponsor inventory
We do not broker, package, or resell anything your rights holder controls.
Your fan data
Records built during the pilot are yours, exportable, and yours to keep if you stop.
Three numbers decide whether this worked.
We settle these with you before the first game, which is what makes it a pilot rather than a favor. If they do not move, you have lost a two-week setup and a handful of file exports.
Claim rate
The share of scanned attendees who claim their stub. This tells you whether the mechanic works in your building at all.
Trade volume
How many trades happen between fans. This tells you whether the set you built was worth finishing.
Cross-event attendance
How many fans turned up to an event they had never attended before. This is the number that pays for everything else.
Three games is the whole ask.
If it does not work across three, you have lost a two-week setup and a handful of file exports.
- Moments free to distribute across your entire first season
- SDK or hosted deployment
- Moments, rewards, and messaging included
- Community page with marketplace, rewards, and engagement
- Dedicated team to launch and optimize the pilot
We partnered with Ticket Tree because we share the same mission, to give the fans a better experience.
Tell us what to bring
Pick what you want on the call and we will build it before we speak. Three required fields, and the rest only matters if you asked for something that needs it.
What happens after you send it
- We build what you picked. If you gave us numbers it runs on yours, otherwise it runs on a building your size.
- We come back with times and tell you where your ticketing connection really stands rather than saying yes and finding out later.
- If it still looks worth doing, we scope three games. That is the whole commitment.
Sent.
Your mail client should have opened with everything filled in. If it did not, send the same details to hello@stubs.fun and we will pick it up there.
Want the short version first.
The pilot page lays out the entire ask on one screen.
- Moments free to distribute across your entire first season
- SDK or hosted deployment
- Moments, rewards, and messaging included
- Community page with marketplace, rewards, and engagement
- Dedicated team to launch and optimize the pilot
We partnered with Ticket Tree because we share the same mission, to give the fans a better experience.
The fan identity layer for live events
Ticket Tree is built data first for schools that want to activate their fan base through rewards based experiences, and stubs.fun is the part of it a fan actually holds.
Nobody owns the fan.
An operator builds an audience every season and hands the record of it to a vendor. When the contract ends, the audience does not come along.
A ticket changes hands and the record of who is actually in the seat stops at the reseller.
The audience shows up every week and the building still cannot describe it.
The data exists. It is scattered across systems that were never meant to talk to each other.
Ticketing, CRM, email, donor, retail, app. Each one holds a fragment and none of them holds the fan.
Figures describe the category, not any one operator we work with.
Before the QR code, you kept the stub.
It sat in a drawer or a shoebox and it proved you were there. The barcode replaced it with something that expires at the gate.
Then
The stub was a physical thing. You could hold it, show it, trade it, and lose it. Nobody had to verify it because it was obviously real.
Now
A screenshot proves nothing. AI can produce a photo of a night that never happened, so the record of a real one is worth less every year.
What we do about it
A moment is issued against real attendance at a real event. It is the one thing in a fan's phone that a host can vouch for and a fan can keep.
Moments belong to the people who were there.
Two things follow from that, and they point the same direction. Hosts get a first party record of their own audience instead of a fragment held by six vendors. Fans get real ownership of the nights they showed up for, in something they can look back on, trade, and use.
stubs.fun is a product built by Ticket Tree to give fans ownership over every IRL moment. 3 Tree Labs Inc., Boston.
Talk to the people who built it.
A pilot conversation is with the team that runs it, not a sales layer on top of it.
- Moments free to distribute across your entire first season
- SDK or hosted deployment
- Moments, rewards, and messaging included
- Community page with marketplace, rewards, and engagement
- Dedicated team to launch and optimize the pilot
We partnered with Ticket Tree because we share the same mission, to give the fans a better experience.
What is stubs.fun?
A free digital stub from an event you actually went to. It is proof you were there, it is yours to keep or trade, and it never costs you anything.
Every stub lands at one of six tiers. The rarer it is, the more it carries: points, rewards, or access to things the event runs later.
Show up, and the rest happens on its own.
There is no version of this where you have to do paperwork. You went to the game. That is the part that counts.
You go to the event
Nothing to install and nothing to sign up for. Going is the whole qualification.
Your stub arrives
It lands at one of six tiers, and which one you get is luck. Same night, same seats, different stub.
You collect the set
Every event you go to adds to it. Sets run by season, by sport, by rivalry, or by a night nobody forgets.
The set unlocks something
Finish one and the reward behind it opens. Seats, access, presales. The event decides what it puts up.
You trade for what you missed
The stub you need is held by somebody who went to a night you skipped. That is the only place it comes from.
I cannot find my stub
Check the email address you used to buy the ticket, including the promotions folder. If it is still missing, tell us the event and we will find it.
I need help with a ticket, not a stub
Contact the event or the venue directly. We do not have access to their ticketing unless they run on us.
Can I sell one
You can trade with other fans who went. What a completed set unlocks is set by the event, not by us.
Run an event yourself?
If you put on shows, games, or festivals, this is the same thing from the other side.
- Moments free to distribute across your entire first season
- SDK or hosted deployment
- Moments, rewards, and messaging included
- Community page with marketplace, rewards, and engagement
- Dedicated team to launch and optimize the pilot
We partnered with Ticket Tree because we share the same mission, to give the fans a better experience.