Separating event notices from marketing permissions
Delegates registered for a conference and now receive the association's membership offers, a sponsor's newsletter and the event app's promotions.
The short answer
Sort every message into two groups: messages needed to run the event the delegate registered for, and messages that promote something. Ask for permission to send the second group separately, with its own question, who will send it and what it will contain.
Which messages fall in which group, and how permission must be asked and recorded, is a decision for your data protection contact. The organiser's job is to make the separation visible and operate it.
Why separation helps
A delegate who ticks one box to register and then receives promotions from three organisations has not been given a clear choice. Keeping event messages and marketing apart makes the form easier to read and makes complaints easier to resolve.
It also protects the event: a delegate who has asked to stop promotions still needs the joining details.
Message map: what goes where
| Message | Likely group | Question to confirm |
|---|---|---|
| Registration confirmation and receipt | Event | Does anything promotional sit inside it? |
| Joining instructions, venue changes, schedule changes | Event | Is the sender the organiser or a supplier? |
| Post-event certificate or feedback request | Event, check | Is the survey linked to marketing? |
| Next year's early-bird offer | Marketing | Separate permission and wording? |
| Association membership promotion | Marketing | Is the sender the same legal entity as the event organiser? |
| Sponsor or exhibitor newsletter | Marketing, sharing | Is a delegate's detail passed on, or does the organiser send on the sponsor's behalf? |
Design the form to keep them apart
- Put marketing questions after the registration details, with their own heading.
- Use one question per sender or purpose rather than a single bundled box.
- Leave marketing choices unticked by default, unless your data protection contact advises otherwise.
- Say in plain words what will be sent, how often and by whom.
- Make changing the choice easy in every later message.
Operate the choices
- Record each delegate's choices in separate columns, with the date and the wording they saw.
- Build the mailing lists from those columns, never from the full registration export.
- Check suppliers and sponsors: whose list is it, and who sends?
- Honour opt-outs and withdrawals promptly and check before every send.
- Review the log after the event and before any new campaign uses the list.
Questions for your data protection contact
- Where is the line between an event message and a marketing message for our event?
- How should permission be asked, in which languages, and how long is the record kept?
- What may sponsors or exhibitors send to delegates, if anything, and on whose behalf?
- Who handles withdrawals and how quickly?
Worked example · Fictional example
Separating three streams of email for a regional summit
Fictional organisation and figures, for illustration only.
A fictional chamber hosts a one-day summit. Its form had one box covering event updates, chamber promotions and sponsor offers. After mapping messages, the secretariat splits it into event messages with no box, chamber promotions with their own box, and sponsor offers sent only if the delegate takes a separate step.
The data protection contact reviews the wording and tells the secretariat what to record. The mailing list for the post-event offer is built only from the chamber column.
Use this yourself
Message and permission map
One row per message or sender. Share the finished table with your data protection contact.
| Message or sender | Event or marketing | Who sends | Where permission is asked | What is recorded | Contact's decision |
|---|---|---|---|---|---|
| Joining instructions | Event | Secretariat | Not applicable, to confirm | Send date | |
| Early-bird offer | Marketing | Secretariat | Separate form question | Choice, date, wording | |
| Sponsor newsletter | Marketing, sharing | Sponsor or organiser, to confirm | To be decided | To be decided | |
Handle it in-house, or bring in help?
Your team can usually handle this when
- One sender, a short list of message types and an approved wording.
- You can send each stream from a separate list.
- Your contact has already approved the form layout.
Outside planning help earns its fee when
- Several organisations want to contact delegates.
- Past events mixed lists and nobody can tell who chose what.
- Sponsors expect lists as part of their package.
Need the streams separated before registration opens?
An Event Blueprint can map each message and sender, lay out the form and list structure, and hand your data protection contact a question pack for the boundaries. The wording and decisions remain with your organisation's contact.
Questions organisers ask
Is a confirmation email with an offer in the footer a problem?
Ask your data protection contact. The safer working practice is to keep event messages free of promotion and send offers separately to those who chose them.
Can the sponsor email delegates after the event?
That depends on what delegates were told and what they chose, which your data protection contact decides. See the sponsor data-sharing review for questions.
How do we handle someone who withdraws?
Record the date, remove them from the marketing list, and keep event-essential messages going until the event ends. Confirm the handling with your contact.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.