How Talent CRM Campaign Statistics Work
ALL CALCULATIONS USE UTC TIME TO AVOID TIMEZONE CONFLICTS ACROSS AN ORGANIZATION'S USERS.
- Reach Outs: Sometimes called Email Threads, Reach Outs are the count of the net new attempts to communicate with a prospect via a campaign. For a date range, a Reach Out is counted if the Reach Out was created within that date range. It may not always be the case the email message is sent on that date due to your own throttle settings and mail provider limits.
- In Progress: the count of Reach Outs that haven't been responded to, canceled, or hard bounced within a given reporting date range.
- Opens: the count of Reach Outs created in the reporting range where a prospect has opened at least one of the messages from the campaign. Please note, if two or more messages sent within the reporting period to a prospect and multiple are opened, aggregate reports will only show 1 opening.
- Opens are always equal or less than total reach outs
- Responses: the count of Reach Outs that the prospect has opened and responded to
- For the set of Reach Outs counted in a date range (see logic above), if any Reach Out has a response (Response Via is not blank AND/OR Reach Out state is set to responded (2)), count it here
- Responses are always equal or less than total Reach Outs
- Interested: the count of Responses that are marked with Response Type of Interested (👍). This total is again based off the creation date of the Reach Out.
- Interested count is are always equal or less than total reach outs and responses.
States of Reach Outs (Email Threads)
Reach Outs, once created, can exist in nine different states. Below is a simple explanation of those states and how they occur. Please note, this is not a complete explanation as there are many edge cases based on your email provider, account type, prospect email provider etc.
- In Progress (0) - As stated, this is an in progress Reach Out that has messages scheduled for sending.
- Hard Bounced (1) - A Reach Out with a message that was sent and received back a hard bounce or mailbox rejection. These Reach Outs are considered stopped from further sending.
- Responded (2) - ****Responded Reach Outs are marked this way either manually or automatically when you receive a reply from your prospect. If this state is reached, all future messages within the Email Thread will be set to “Prevented” (see below).
- Completed (3) - Reach Outs that send out all the messages of the campaign with no reply or other event such as a Hard Bounce, are set to Completed. This implies no more messages are left in the Email Thread.
- Paused (4) - Email Threads can be paused for several reasons. The most common is in the event of an automated response from the prospect such as an Out of Office reply. To avoid spamming someones inbox when its set as inactive (OOO), we choose to pause your Reach Out. These paused Reach Outs will appear at the top of your dashboard periodically and can be forced to re-send at your discretion.
- Canceled (5) - Reach Outs are only considered Canceled when a user explicitly requests to cancel from the Reach Outs table on the Dashboard or Campaign. Reach Outs from a batch will be marked canceled if the batch has been canceled. All future messages are stopped.
- Undone (6) - Reach Outs that were formerly In Progress, and are stopped manually before any message is sent out are marked Undone. Undone Reach Outs can be rescheduled.
- Paused By Auth Loss (7) - Similar to a Paused state, Paused by Auth Loss will freeze future messages of the Reach Out from being sent. This state occurs when we lose connectivity to your inbox. When a Reach Out is in this state it will appear on your dashboard in the paused reach out table. If you are unable to reconnect in order to reschedule the Reach Out, please contact email@example.com
- Prevented (8) - Prevent state occurs when you receive or mark a Reach Out message as responded to. Future messages within the Email Thread are set to Prevented.
- Pending (9) - Pending is a brief state that typically implies the Reach Out is in the process of being scheduled or modified. Users will not typically see this state in the platform.