Tracking where your event audience comes from
Registrations are arriving, and nobody can say whether they came from the mailing, a partner or a colleague's message.
The short answer
Audience source tracking means giving each invitation route a short code and recording that code against each registration, so you can count registrations by source. It tells you which routes to repeat or drop.
Keep it as simple as the decisions need. If you will not change anything based on the answer, do not collect it.
Decide what you want to learn first
Start with the decision: which partner to ask again, which segment is behind, whether a personal approach beats a mailing. Then choose the least data that answers it.
Counts by source are usually enough. You rarely need to follow individual people to answer those questions.
Three practical ways to record the source
| Method | How it works | Watch for |
|---|---|---|
| Route-specific link | Each partner or mailing gets a registration link carrying a short source code. | Links get forwarded, so the code shows the route, not always the person's first contact. |
| Optional form question | Registration form asks how the person heard about the event, from a short list. | Self-reported and approximate. Make it optional, and keep the list short. |
| Owner log | Each segment owner records who they personally invited and who replied. | Depends on owners keeping the log current. |
Privacy questions to ask before you start
Whether and how you may track sources is a question for your organisation's data protection contact. Take these questions to them and record the answers.
- Is a source code in a link, or a source question on the form, acceptable for our event and our audience?
- Do we need to tell people how we use it, and where is the right place to say so?
- Who has access to the registration data and the source log, and for how long is each kept?
- May partners see registrant details, or only counts per link?
- Is any tool we plan to use for links or forms storing data outside our control, and does that need checking?
Set it up
- Write the list of sources: each partner, each mailing, each personal outreach owner, open channels.
- Give each a short code, such as the partner's initials and a number.
- Add the code to the link, or add an optional question to the form. Use the form field minimiser to justify the field and name who keeps the data.
- Record in the invitation sequence planner which code goes with which invitation.
- Count registered and confirmed by source on the same day each week, using your funnel definitions.
Read the results carefully
- A source with few registrations may still be valuable if it reached the right segment. Compare against audience quality, not only volume.
- Unknown is a legitimate category. Do not reallocate it to the largest source.
- Counts per source are not a forecast. For scenarios, use the attendance scenario planner with your own assumptions.
- Small numbers vary a lot week to week. Wait before making big changes.
Worked example · Fictional example
A fictional forum reads its source counts
Fictional organisation and figures, written to show the level of detail that is useful.
A fictional lawyers' association gave each of four routes a code: member mailing (MM), university partner (UP), president's personal invitations (PR), and open social posts (SO). After three weeks the log showed 41 registered: MM 18, PR 11, UP 4, SO 3, and 5 unknown.
The committee read this as: the personal route is doing a lot with a short list, the university partner needs a reminder and a clearer link, and the unknown five should be asked. They did not conclude anything about future numbers, only about what to do next week.
Use this yourself
Source tracking log
Copy this table. Add a row per route and update the counts on your weekly count day.
| Source code | Route and owner | Link or form method | Registered | Confirmed | Count date | Privacy answer recorded (who, date) |
|---|---|---|---|---|---|---|
| MM | Member mailing, secretariat | Route link | ||||
| UP | University partner, committee member | Route link | ||||
| Unknown | No source recorded | None | Not applicable | |||
Handle it in-house, or bring in help?
Your team can usually handle this when
- A few routes, each with a clear owner.
- The registration form can take a source code or one optional question.
- The data protection contact has answered your questions.
Outside planning help earns its fee when
- Many partners, tools and forms, with no single source of registration data.
- Owners are not recording personal outreach and counts do not reconcile.
- The committee wants decisions from the counts but no one has set up the rules.
Want the source log set up and read with you?
A conference project lead can set the source codes with your partners, keep the weekly counts consistent with your funnel definitions, and bring you a short reading of which routes to repeat or change. Questions about permission and data handling go to your data protection contact. Send your current registration routes.
Questions organisers ask
Do we have to track sources at all?
No. If you will not act on the answer, skip it. For small, invitation-only events, a simple owner log may be enough.
Is a source question on the form allowed?
Ask your data protection contact. Whatever they advise, keep the question optional and the answer list short.
Should partners see who registered through their link?
Share counts first. Whether named details may be shared is a question for the data protection contacts on both sides.
How do we handle forwarded links?
Accept that the code shows the route the link travelled, not always the first contact. Treat it as an indication, and combine it with the owner logs.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.