Event Intelligence is a request workflow for event-specific targeting help. It keeps event context, audience notes, and follow-up history inside Satua instead of scattered across email or chat.
What It Does
Through Requests -> Help with Event Intelligence, your team submits an event brief. Satua's account team can use that brief to help scope an event-specific audience and return guidance or tagged results according to your account's plan and data permissions.
Satua does not sell event attendee lists or act as a data broker. Event workflows use account-supplied context, account-approved sources, and CRM tagging so your team can work records responsibly.
Inputs You Should Provide
The request form asks for:
- Event name.
- Event website or registration page.
- Start and end dates.
- Event location.
- Audience types: attendees, exhibitors, sponsors, and/or speakers.
- Whether to use your current ICP or a different target.
- Specific sessions, booths, tracks, or companies to focus on.
- Any additional notes.
The more precise the brief, the easier it is to scope a useful event segment.
Access And Limits
- Requests must be enabled for your account.
- account admins have request access by default.
- Non-admin users need request permission from a account admin.
- Only one pending Event Intelligence request is allowed per event.
- Event requests should be submitted at least a week before the event where possible.
Working Event Results
When event-tagged records are available in your account:
- Open Dashboard.
- Use the Event filter to isolate the event tag.
- Save a dashboard view for the event.
- Assign owners and log first touchpoints.
- Use lists or campaign selection when email is enabled and legally appropriate.
- Track outcomes through lead and company statuses.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Event request is unavailable | Request feature or permission not enabled | Ask a account admin to enable request access |
| Submit button is blocked | Required event fields are missing or event date is in the past | Complete the form with a valid current/future event |
| Duplicate event request rejected | A pending request already exists for that event | Edit the pending request instead of creating another |
| Event-tagged leads are not visible | Filter mismatch or results not yet loaded | Check request status, clear filters, and search by event tag |
| Too few relevant records | Event brief or ICP was too narrow | Submit a follow-up note with broader audience guidance |
Recommended Workflow
- Submit the event brief at least 1 week before the event.
- Use the current ICP unless this event needs a clearly different audience.
- Include exclusions so low-fit records do not enter the CRM workflow.
- Save an event-specific dashboard view after results are tagged.
- Assign owners before launching outreach.
- Review consent, opt-out, and jurisdiction rules before sending.