The problem this solves
Registrants are the warmest audience an event produces and the most expensive one to keep advertising to. Before the event they should see the reminder and the agenda; after it they should see the follow-up; and at no point should the acquisition campaign keep paying to reach people who already signed up. Both needs come from the same CSV, and both are usually neglected because the file sits in the events tool.
Enrichment makes the audience more useful than the raw registrations. Company and title on each registrant let the follow-up campaign speak to roles, and let sales see which accounts sent people. The suppression file is the mirror image: the same registrants formatted so they can be excluded from every campaign that is still hunting for them.
How the mission runs
- Read the registrant CSV. The Audience Agent reads the attached file for <event>, identifies the identifier columns and dedupes registrants who signed up twice, keeping the earliest registration date.
- Enrich each registrant. Company and title are added through people search and firmographics from the email domain and name, so the audience and the follow-up can be segmented by role and by account.
- Build the LinkedIn matched audience. The registrants are staged as a LinkedIn contact-matched audience on your connected ad account, named for the event, shown with the count and created on approval, with the matched size reported once LinkedIn finishes.
- Produce the suppression export. The same registrants are exported as a suppression file in the formats your acquisition campaigns need, saved to Google Drive, with a note on which campaigns to attach it to and the count of rows.
The prompt
This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.
What comes back
A LinkedIn contact-matched audience of <event> registrants on your connected ad account with the matched size reported, an enriched registrant list with company and title per person saved in the workspace, and a suppression export in Google Drive ready to exclude registrants from acquisition campaigns. The report shows the registrants read, the duplicates removed and the share enriched with company data.
Make it yours
- Build a company-matched audience of the registrants' employers to reach the rest of each account.
- After the event, split attendees from no-shows and create two audiences for different follow-ups.
- Push the enriched registrants to HubSpot with the event as the source.
- Build the audience for the follow-up webinar series at the same time, excluding people who attended.
Frequently asked questions
Can the registrants come straight from a form rather than a CSV?
Yes. If the event ran on a LinkedIn Lead Gen Form, the leads playbooks pull the registrants directly; otherwise export the CSV from your events tool and attach it.
How is the suppression file used?
Attach it as an exclusion audience on the acquisition campaigns; the note names the platforms and formats produced.
Does enrichment change the registrant data?
No. Company and title are added as new columns; the original registration fields are preserved.
Can it separate speakers and sponsors from ordinary registrants?
Yes. If the CSV carries a type column, or if you attach the speaker and sponsor lists, those people are excluded from the audience or placed in their own, since they need different treatment.
Will the audience be refreshed as registrations continue?
Attach a new export each week and only new registrants are added to the audience and the suppression file; the mission keeps the earlier members.
Can it enrich registrants with a fit score?
Yes. Each registrant's company is scored against your ICP so the follow-up can prioritize accounts, and the score is kept on the enriched list.