Funnel Insights Prospects
This table has 1 row of per user-prospect interaction per UTC day per org id.
| Column | Type | Definition | Sample Value(s) | Sample Use |
|---|---|---|---|---|
| ACCOUNT_ID | Varchar | The associated account ID for the prospect ID that the activities with User ID Maps to the ACCOUNTS table. | ||
| ACTIVITY_DATE | Timestamp_NTZ | The UTC Day when the user performed any activities of tasks, mailing, meetings, or calls. | This is used in the filter to define a timeframe for a report | |
| BENTO | Varchar | A collection of machines that power the Outreach app. Orgs live inside these. | This may distinguish orgs that are in different data centers. | |
| IN_SEQUENCE | Boolean | Boolean value determining whether the prospect is contacted in any sequences thru mailing, tasks, meetings, or calls | Can be used to calculate total prospect contacted via sequence as count (distinct prospect_id) where in_sequence = true over a timeframe | |
| IS_ENGAGED | Boolean | Boolean value determining whether the prospect has responded/engaged | Can be used to calculate total prospect responded as count (distinct prospect_id) where is_engaged = true over a timeframe. Can also be used in conjunction with in_sequence = true to determine count of prospects who have responded in sequence | |
| IS_INVITED | Boolean | Boolean value determining whether the prospect has been invited | Can be used to calculate total prospect invited as count (distinct prospect_id) where is_engaged = true over a timeframe. Can also be used in conjunction with in_sequence = true to determine count of prospects invited in sequence | |
| O_ID | Varchar | Organization ID, also called instance ID. This is the ID for your unique Outreach account. | Most commonly used on joins alongside other primary keys. where a.o_id = b.o_id and a.id = b.a_id | |
| PERSONA_ID | Varchar | The associated persona ID for the prospect ID that the activities with User ID Maps to the PERSONA table. | ||
| PROSPECT_ID | Varchar | The associated prospect ID for the activities with User ID Maps to the PROSPECTS table. | Can be used to calculate total prospect contacted as count (distinct prospect_id) over a timeframe. | |
| USER_ID | Varchar | The associated user ID responsible for the activities. Maps to the USERS table. |