Ticket sales tracking links: a small-event worksheet
Use ticket sales tracking links to compare event promotions. Build a source worksheet, separate visits from orders and tickets, and test the buyer journey.

Ticket sales tracking links help an organizer connect a recorded purchase with the promotion link used to reach the event. Give the studio newsletter, a venue partner and a poster separate links, then check which results the ticketing service can report. Keep a plain event link available too, with unattributed sales visible in the worksheet.
For one dated workshop or small performance, start with three or four placements you can maintain. If the event itself is still being prepared, complete the workshop ticket sales checklist before adding promotion links.
Decide which promotion you need to identify
Write the next decision first. You might need to decide whether to ask the same venue partner to share the next workshop, whether a printed poster brought recorded purchases, or which newsletter placement to repeat. A source label should distinguish the placements relevant to that decision.
“Instagram” may be enough when there is one post and one link. If a studio's profile link and a partner's story both lead to the event, give them separate labels. If you deliberately reuse one link in several places, keep those results together and describe the row accordingly. You cannot later divide a combined total using the number of likes on each post.
Record the event and session date with every link. A link to last month's workshop can still open successfully while directing buyers to the wrong session. Reusing an old naming scheme is fine; reusing a destination without checking it can send customers to closed sales.
Check what the provider records
Providers offer different ways to connect promotion with purchases. Freshtix documents a campaign parameter and a ticket-sales report. MyVisito's Hebrew organizer guide describes named links with views, registrations and sales. These examples show what to ask your provider; they do not establish that another service has the same reports.
Before creating links, find answers to these questions:
- Does the report connect a source to a visit, a completed order, individual tickets, or several of these?
- If a buyer opens two different promotion links, which one receives the recorded purchase?
- How long can a purchase remain associated with a link?
- What happens when the buyer returns on another device or pays manually?
- How are cancelled purchases, test orders and purchases without a known source shown?
Write the answers and report names beside the worksheet. If a tool only counts link openings, use it to compare recorded openings. A click counter cannot tell you which visitor bought two tickets later.
Keep one link register for the event
Create a small register before distributing anything. Use stable labels with consistent spelling. A colleague should be able to find the exact link that belongs on the poster without guessing between several saved messages.
| Placement | Internal label | Person sharing it | Checks before sharing |
|---|---|---|---|
| Studio newsletter | studio_newsletter | Studio owner | Correct session and working purchase route |
| Venue partner's message | venue_partner | Partner contact | Separate supported tracking link |
| Poster at the venue | venue_poster | Reception lead | Printed QR opens the correct public sales page |
| Plain event address | unattributed | Anyone using the plain address | Retained as a separate reporting category |
Add the actual public link, creation date, planned sharing date and test result to your working copy. The labels above are planning examples, not working links or settings you can paste into a particular service.
Keep private ticket access out of this register. A promotion link should open the public offer. An order-access link may expose purchased tickets and must stay with the relevant buyer. The confirmation-email guide explains the separate job of private ticket delivery.
Use UTM parameters only with a supported measurement setup
UTM parameters label a campaign link. Google's campaign URL documentation defines source, medium and campaign, plus a content field for distinguishing placements. Parameter values are case-sensitive, so agree on a consistent naming convention.
For a planning example, a studio might record source as studio_newsletter, medium as email and campaign as printmaking_november. A second link in that email could have a different content value if that distinction will change a decision. Use the provider's documented link builder or campaign setup rather than adding guessed parameters.
Appending labels to an address does not install analytics or create a purchase report. Confirm that the destination reads the parameters and that the supported purchase measurement retains the needed source. Where the journey crosses a separate payment page, test the complete journey before assuming the source survives.
Use public campaign labels. Leave buyer names, email addresses, order numbers and admission credentials out of promotion parameters. Keep any analytics setup within the consent configuration appropriate to the site. This worksheet can also be used with a provider's existing source report without adding a new advertising pixel.
Test the exact link buyers will receive
Open each link from the actual placement on a phone. For a poster, scan a proof of the printed QR. For a newsletter, open the received test email. Check the event date, language, ticket availability and checkout destination. A correctly spelled label is little help if a redirect drops it before it reaches the service that records it.
Use the provider's supported preview or test-purchase process. Record the test reference, expected source, quantity and observed result. A two-ticket test should produce the documented distinction between one order and two admissions. Follow the provider's process for excluding test records from the live report.
If there is no supported purchase test, ask the provider how to verify attribution before treating the first campaign as measured. Do not insert invented card details into live checkout. A manual-payment route needs its own check; a source attached to a reservation may be handled differently when payment is later confirmed.
Work through a 24-place workshop
The following figures are fictional. A workshop has a participant limit of 24. At one recorded snapshot, there are 20 paid issued admissions, two complimentary admissions and two active reservations awaiting payment. No order in this example has a refund or partial cancellation.
The source report assigns each paid order to one category. All three measured placements use the same definition of a recorded visit and the same reporting period.
| Reported source | Recorded visits | Paid orders | Paid tickets |
|---|---|---|---|
| Studio newsletter | 200 | 5 | 8 |
| Venue partner | 80 | 4 | 7 |
| Venue poster | 40 | 2 | 3 |
| Unattributed | Unknown | 1 | 2 |
| Total | Not comparable | 12 | 20 |
The newsletter has five paid orders containing eight tickets. The partner has four orders containing seven tickets. Counting orders as people would reduce the paid-attendance figure from 20 to 12. Adding visits to purchases would mix unrelated units.
The capacity check is separate: 20 paid admissions + 2 complimentary admissions + 2 held places = 24 allocated places. The complimentary places stay outside paid-sales totals, and the reservations stay outside completed paid orders until confirmation. Use the manual-payment guide for checking holds and confirmation.
The recorded visits total 320 across the three measured rows, but the unattributed row has no comparable visit count. Leave the overall visit total uncalculated rather than treating Unknown as zero. These figures describe this fictional report; they do not show what would have happened without any promotion.
Resolve mismatches before choosing the next campaign
Compare the source report with the event's order record for the same cutoff time and time zone. Check that every paid order appears once under the report's allocation rule. Keep unresolved, refunded or partially changed orders in a reconciliation list until their treatment is clear. Source attribution and payment status answer different questions.
If the ticket totals disagree, inspect the event filter, reporting period, test records and definition of a sale. Check whether one report counts issued admissions while another retains cancelled sales. Preserve the original export and note each correction. Do not move unattributed orders to a partner's row because someone remembers seeing that partner's post.
A source report records the credit assigned under its rules. A forwarded newsletter link may retain its original label; the label cannot prove who persuaded the buyer. Multiple visits, device changes and unavailable source information can also limit interpretation. Keep an optional buyer answer such as “How did you hear about this?” in a separate column if you collect it; do not silently replace the measured field with that answer.
At the next review, write one concrete decision beside each placement: repeat it, repair the link and test again, or gather another event's evidence before changing the plan. For an event you hope to manage with Skedful, contact the team with the date, country, payment route and source-reporting needs. Confirm ticketing availability and the supported measurement options before including attribution in your launch plan.
About this article
Skedful is the publisher and corrections contact. Our editorial checklist covers product availability, source dates, worked examples and the limits of each claim.
About this articleWorked examples and sample calculations describe hypothetical scenarios. When an article cites research or customer results, follow the source for its context and limits.
Found an error? Send us the article link and the passage that needs a correction.
Report an error to SkedfulReminders come with every Skedful plan, on a schedule you set once. PricingSkedful vs Fresha vs Booksy