Skip to content
DnsLister Forum

Where domain hunters compare notes

How to tell which channel actually sold each ticket for your events: one tracked link per placement

The morning after a campaign you know how many tickets you sold. What you usually don't know is which of the six things you did sold them – the newsletter, the poster with the QR code, the partner's website, the paid ad, the artists sharing to their own followers, the free listing someone put up. So next time you do all six again, because you can't prove any of them is dead weight.

Quick context so this reads clearly: we build Entase, an event ticketing and commerce platform. What follows is the attribution workflow we walk organizers through. The mechanics are ours; the thinking works anywhere you can tag an order.

The whole thing rests on one habit: never post the same link twice. Give every placement its own.

In practice you generate a short link in one of two places, and they behave differently. A link made from the event points at the event's information page – poster, description, every scheduled date with a buy or register button next to it. A link made from a specific date in your program skips all that and opens seat and ticket selection for that one date. Rule of thumb: information page for a season announcement or a run with several dates, direct checkout link for the single night you're pushing this week or a social post where the date is already in the copy. Both are generated from the same panel: Short links and social sharing

Before you copy the link, attach a label to it. We call these segments – each one is a color, a short code like nl-oct or poster-qr, and a name a human can read. Pick one from a dropdown in the sharing panel and the link rewrites itself to carry it. From then on, every order placed through that link is tagged with that label, and stays tagged. Setup and naming conventions: Creating and managing segments

The rule that decides whether the report is useful: one label per thing you could stop doing. If the newsletter and the partner hotel share a label, the number can't change a decision. Separate them, and write names you'll still understand in three months.

Counter sales belong in the same report. Staff can apply the same labels at box office checkout, so the walk-up holding a flyer lands next to the online buyers. On top of that, every order automatically records whether it was sold online or in person, and who handled it – the cashier's name at the window, the referring domain online: Channels and operators

If your checkout is embedded on your own website, you can pass campaign parameters straight through to the order, including a segment code. Two things worth knowing before you debug them the hard way: the tracking call replaces the whole parameter object rather than merging into it, and the client does not read your page's query string, so forward your own utm values yourself. The embed widget does that for you for a fixed list. Tracking and consent with the JS client

Then you read it back in one place: statistics, broken down by segment, order counts and revenue side by side.

One thing attribution won't tell you, and it matters as much: how far the buyer has to travel between interest and done. Keeping checkout on your own page rather than sending people somewhere unfamiliar mid-decision, and pointing a link at seat selection for the actual date instead of a homepage, isn't a growth trick. It's just less room to change your mind.

Which brings me to the part we can't see. We can measure what happens after the click. What made someone click is your knowledge, not ours.

So: which marketing moves genuinely sell tickets for your events, and which ones look busy and produce nothing? Is the newsletter still the strongest thing you have? Do partner and cross-promotion links pull their weight? Have you ever had tracked data reverse a decision you'd already made – cutting a channel, or putting money back into one you'd written off?

Source: r/Entase · by /u/entasecom

Leave a Reply

Your email address will not be published. Required fields are marked *