GDPR worries when you sell to event planners
Could you show where each contact came from if someone asked? Here is how people who sell to event planners fix it.
Could you show where each contact came from if someone asked?
Rules such as the GDPR expect you to know where personal data came from and to respect objections. With loose spreadsheets that is hard to prove.
It hits harder when you sell to event planners. Event planners range from freelance wedding planners to agencies running conferences and corporate events. They book venues, suppliers and technology on behalf of clients, so they are both buyers and gatekeepers for many other businesses.
Uncertainty makes you hold back on outreach, or take risks you would rather avoid. A request to see or delete data becomes a scramble.
Source, date and opt-out on every record.
Riftjaw keeps the source and date on every record and has an opt-out register. Unsubscribed contacts are never mailed again, and you can export or delete a contact on request. Data stays on your account's own server; this is not legal advice, but it gives you the records to work with.
- Fields that fit event planners, such as event types
- Email prefixes that fit, like hello@, info@, events@ and enquiries@
- Status, tags and a segment on every record
Fixing it in Riftjaw
- Import with a source. Every imported record keeps where and when it came in.
- Respect opt-outs. Unsubscribes land in the opt-out register and are skipped in every campaign.
- Handle requests. Export or delete a contact when someone asks.
Other walls when prospecting event planners
Planners are on site at events and slow to reply.
Open tracking shows who read your mail, so a short follow-up goes only to the interested ones.
Wedding planners and corporate planners are mixed in one list.
Tag event types and save a filter per type.
Relationships grow over several seasons.
Notes and history on each contact keep the context when you reach out again next year.
Fields worth recording for event planners
Add these as fields in your lead file. Any column in your import can become a field.
| Field | Why it helps |
|---|---|
| Company name | The key field. Duplicates are checked on it or on the website. |
| Website | Needed to derive an email when the export has none. |
| Event types | Weddings, corporate events and festivals need different suppliers. |
| Event size | Typical guest numbers shape what they book. |
| Area covered | Planners work locally, nationally or abroad. |
| Preferred suppliers | Whether they keep a supplier list you could join. |
| Lead planner | The person who chooses suppliers. |
Questions people ask
Reach out outside their peak season with examples of relevant work, then follow up. In Riftjaw you track each step with statuses, tags and notes.
Yes. Add tags or a field for event types and save a filter for each group.
If your file has an email column, that wins. If it only has websites, tick the prefixes you want, such as hello@, info@, events@ and enquiries@, and Riftjaw derives addresses from each domain. Derived addresses are good guesses, not verified, so start with small batches.
Yes. The Free plan runs the whole pipeline on one list with small campaigns, and you do not need a credit card. Move to Pro when you want more lists, segments and bigger campaigns.
Build the list in a city
Event Planners in PhoenixArizona, United StatesEvent Planners in HoustonTexas, United States
Event Planners in San FranciscoCalifornia, United States
Event Planners in BostonMassachusetts, United States
Event Planners in BelfastCounty Antrim, United Kingdom
Event Planners in SeattleWashington, United StatesBuild a database you own
Create your account, import your first list and see it turn into records you can work.
No credit card · cancel any time · your data stays yours