Step-by-Step Guide: Event Intelligence
Step-by-Step Guide: Event Intelligence Setup & Usage
This guide provides a step-by-step walkthrough for setting up and using the Event Intelligence (EI) platform,
Phase 1: Administrative Setup (Organization Level)
Overview
The Account Settings section is the first step in configuring Event Intelligence. These settings are configured once during the initial setup and are reused across campaigns, eliminating the need to enter the same information repeatedly.
The Account Settings page allows you to define your organization and build reusable data that the AI and Campaign Builder will use later.
It contains three main sections:
Company Information
ICP (Ideal Customer Profile) Criteria
Account Map
1. Company Information
The Company Information section introduces your organization to the AI.
The information entered here is later used as context when the AI generates:
Outreach messages
Personalized emails
Customer communications
AI-generated content
Instead of entering the company description each time a campaign is created, this information is stored once and automatically reused.
Information to Complete
Typical company information includes:
Company Name
Website
Industry
Headquarters
Company Description
Additional business information.
Best practice: Provide accurate, detailed information to improve AI-generated outreach quality.
2. ICP (Ideal Customer Profile) Criteria
The ICP Criteria section defines the companies and contacts you want to target.
Instead of entering the same targeting criteria for every campaign, configure it once here and reuse it.
This reduces data entry and ensures consistency across campaigns.
Available Attributes
The system offers a wide range of targeting attributes, including:
Locations
Job Titles
Industries
Company Size
Job Functions
Seniority Levels
Revenue
Technologies
Additional business attributes
Campaign Builder uses these attributes to create audience segments.
Field Types
Different fields use different input controls depending on the type of data.
Multi-Select Fields
Some fields allow selecting multiple values from a predefined list.
Examples:
Location
Industries
Company Sizes
These fields support autocomplete for faster searching.
Custom values (add new)
Some fields include an Add New option.
This option appears when the predefined list lacks certain values.
For example:
Custom industries
Custom job titles
Specialized categories
Additional values can be added beyond the default list.
Note: Some fields (such as countries) lack an Add New option because their values are fixed.
Importing Values
Instead of entering long lists manually, upload a file.
Requirements:
One column only
Plain text values
One value per row
This makes importing large keyword lists quick and easy.
Reusing ICP Criteria
A key advantage of configuring ICP Criteria in Account Settings is reusability.
Saved criteria can be reused in future campaigns instead of being recreated.
3. Account Map
Overview:
The Account Map organizes companies related to your business.
Think of it as a structured map of your business ecosystem.
The Account Map is divided into four categories:
Target Accounts
Customers
Competitors
Partners
These lists represent your organization's data.
For example, if your company is T. Mobile, the Account Map stores:
Your target accounts
Your existing customers
Your competitors
Your business partners
Campaigns and AI features can reference this information later.
Importing Account Data
The Account Map allows Target Accounts, Customers, Competitors, and Partners to be populated using one of two import methods:
Import from File
Import from CRM
Method 1: Import from File
Importing from a file is the standard method for adding account records into Event Intelligence.
Step 1: Download the Template
Select Import from File and download the provided import template.
The template contains the required columns and formatting needed for a successful import.
Step 2: Upload the File
After completing the template, upload the spreadsheet to Event Intelligence.
The system supports the standard file import workflow.
Step 3: Duplicate Handling
During the import process, a duplicate management option must be selected to determine how duplicate records will be handled.
Available options include:
Update – Update existing records with the imported information.
Overwrite – Replace the existing record values.
Ignore – Skip records that already exist.
Duplicate matching is performed using the Company Website as the unique identifier.
Step 4: Preview the Import
Before importing, the system displays a preview of the data.
For file imports, only the first 10 records are shown during the preview.
This makes it possible to verify:
Field mappings
Data formatting
Record accuracy
Note: Only the first 10 rows are displayed because the source file already contains all imported data.
Step 5: Complete the Import
Once the preview is confirmed, start the import.
After completion, the system displays an import summary, including:
Number of records added
Number of updated records
Any skipped or failed records
Import results can also be downloaded for auditing or troubleshooting.
Importing Different Account Types
The file import process is identical for all Account Map categories.
The only difference is where the import is initiated.
For example:
Importing from Target Accounts creates Target Account records.
Importing from Customers creates Customer records.
Importing from Competitors creates Competitor records.
Importing from Partners creates Partner records.
The selected section automatically determines the account type assigned to the imported records.
Method 2: Import from CRM
Instead of uploading spreadsheets, Event Intelligence can import account data directly from connected CRM platforms.
Currently supported integrations include:
Salesforce
OneFocus CRM
Additional CRM connectors may be supported in future releases.
Import Workflow
Importing from a CRM follows a workflow similar to that for file imports.
The process consists of:
Selecting import criteria
Configuring field mappings
Reviewing matching records
Previewing the data
Importing the selected records
Connection Status
For external CRM platforms (such as Salesforce), connector availability depends on its connection status.
Possible states include:
Connected – Ready for importing data.
Disconnected – The connector is available but must be connected before it can be used.
When a connector is disconnected, the interface displays a status indicator along with guidance prompting the connection to be established first.
The Account Type field is used only as a filtering criterion when retrieving records from Salesforce.
Enter the exact Account Type value that exists in the Salesforce instance.
For example, Salesforce may categorize accounts as:
Customer
Prospect
Partner
Enterprise
Custom account types defined by the organization
Event Intelligence uses this value only to retrieve matching records from Salesforce.
Instead, imported records are automatically assigned to the Account Map category from which the import was initiated (Target Accounts, Customers, Competitors, or Partners).
Authentication
If the Salesforce connection expires or becomes unavailable, the system prompts for re-authentication before continuing.
Once authentication is restored, the import process can continue normally.
Duplicate Handling
During the import, select how duplicate records should be processed.
Available options include:
Skip Duplicates – Import only new records and ignore existing matches.
Update Existing – Import new records and update matching existing records.
Duplicate matching can be performed using:
Company Website
Company Name
Regardless of the selected option, all new records are imported. The duplicate handling option only determines how existing matching records are treated.
OneFocus Import
Importing from OneFocus CRM follows the same workflow as Salesforce but uses native OneFocus data.
Available filters include:
Organization Type
Lifecycle Stage
Domain List
When multiple primary filters (such as Organization Type and Lifecycle Stage) are selected, records must match all selected criteria (AND logic).
The Domain List filter supports OR logic, allowing records that match the selected domain list to be included.
After applying the filters, review the matching records, verify the field mappings, configure duplicate handling, and start the import. The remaining steps are the same as the standard CRM import process.
Import Results
After an import is completed, the Results page provides a summary of the import process and access to the imported records.
The Results page displays counters for:
Records Added
Records Updated
Records Skipped
Failed Records
Selecting any counter opens the corresponding filtered data view, allowing only the records for that result type to be reviewed.
Data View
The Data tab displays all imported records.
If accessed from the Results page, the list is automatically filtered based on the selected result category (for example, Added or Skipped records).
Selected records can also be permanently deleted if necessary.
Import Logs
Every import creates a log entry that records the transaction history.
Logs include actions such as:
File Import
CRM Import
Record Deletion
For CRM imports, the log also identifies the source system (for example, Salesforce or OneFocus CRM).
Import Status
Imports progress through several statuses during processing, including:
Draft – The import has been created but not started.
Processing – Records are currently being imported.
Completed – The import has finished successfully.
If an import is left in the Draft state, it can be resumed later without starting over.
Exporting Results
Once an import is complete, the import results can be downloaded.
Depending on the selected result type, the exported file may contain:
Successfully imported records
Skipped records
Failed records
For skipped or failed records, the export also includes the reason each record was skipped or failed.
Reusable Import Experience
The import workflow is consistent throughout Event Intelligence.
Regardless of the data source, the same pattern is used:
Import data.
Review imported records.
Monitor the import log.
Export the results if needed.
The available import sources vary by feature. For example, the Account Map supports file and CRM imports, while other modules may support additional sources such as Captello Envoy.
Data Enrichment Settings
The Data Enrichment section allows the enrichment sources to be configured for use during campaign execution.
Rather than enriching records immediately, this page defines which sources the system should use and the order in which they are queried.
Supported Sources
Available enrichment sources depend on the integrations enabled for the account and may include:
My Captello (OneFocus)
Salesforce (Standard)
Connector Requirements
CRM import options are displayed based on the integrations available for the account.
Licensed Connectors
CRM connectors are licensed features.
A connector appears only if it has been purchased and enabled for the account.
OneFocus CRM
OneFocus behaves slightly differently because it is a native Captello product.
The connector is either:
Installed and available
Not installed
Unlike external CRM in
ort also includes the reason each record was skipped or failed.
Reusable Import Experience
The import workflow is consistent throughout Event Intelligence.
Regardless of the data source, the same pattern is used:
Import data.
Review imported records.
Monitor the import log.
Export the results if needed.
The available import sources vary by feature. For example, the Account Map supports file and CRM imports, while other modules may support additional sources such as Captello Envoy.
Data Enrichment Settings
The Data Enrichment section allows the enrichment sources to be configured for use during campaign execution.
Rather than enriching records immediately, this page defines which sources the system should use and the order in which they are queried.
Supported Sources
Available enrichment sources depend on the integrations enabled for the account and may include:
My Captello (OneFocus)
Salesforce (Standard)
Salesforce (Professional)
Hubspost
Captello Enrichment Network
Marketo
Additional supported CRM and enrichment providers
The available sources are displayed based on the account's licensed integrations.
Enrichment Order
Multiple enrichment sources can be configured.
The order is important because Event Intelligence processes each source sequentially during campaign execution.
Source 1 is queried first, followed by Source 2, and so on.
Source Configuration
Each enrichment source has its own configuration options.
For example:
My Captello allows data to be enriched from existing prospects.
Salesforce requires selecting the connected account, record type, and sorting options.
The available settings vary depending on the selected source.
Creating a Campaign
Campaigns in Event Intelligence are created using a builder designed to provide a seamless experience without isolating the configuration process from the rest of the application.
Unlike traditional wizards, the Campaign Builder keeps the main navigation available, allowing seamless movement between modules while configuring a campaign.
Basic Information
The first step is to enter the campaign's basic information.
Required fields include:
Campaign Name
Meeting Goal – The target number of meetings to generate from the event.
Lead Goal – The target number of leads to capture.
Event Name - The event name.
These goals are used as performance targets and will later be compared against actual campaign results.
Selecting or Creating an Event
The Event field supports both selecting an existing event and creating a new one.
Select an existing event from the list, or
Enter a new event name to create a new event automatically.
When creating a new event, also provide:
Event Type
Event Location
Event Date
The event is created automatically in the background and becomes available for future campaigns.
Builder Layout
The Campaign Builder is divided into multiple sections.
The navigation panel remains visible throughout the process.
Completed sections can be collapsed for easier navigation.
Required information is completed first, while optional fields can be added later.
This layout allows movement between sections without leaving the builder.
Data Hub
The Data Hub stores all participant data collected for an event.
Participants are organized into two entities:
Individuals
Companies
Each imported individual can also include information about their associated company.
Participant Types
By default, Event Intelligence recognizes four participant types:
Attendee
Speaker
Exhibitor
Sponsor
If imported data contains additional participant types (for example, Staff), Event Intelligence automatically creates the new type instead of rejecting the data.
The new participant type becomes available in the Data Hub after the import is complete.
Importing Participants
Participant imports follow the standard import workflow:
Upload the source file.
Configure field mappings.