With so many moving parts in an organization the occasional data inconsistency can appear, reflecting a needed update internally or a missed step in the data collection process. This is especially true for email data as teams grow, campaigns change, and priorities shift.
This article will first explain how Atrium aggregates email data, and what is needed to remedy such inconsistency.
Where is Atrium Pulling Email Data?
Atrium can pull email data from one of these three sources:
- Gmail
- Outlook
- Salesforce
- Blurb about Yesware, Salesloft, Outreach
To check where email data is coming from, try the following:
- Chat
- Email support
To delete/rework:
When an organization is onboarded, Atrium goes through the necessary process of pulling in relevant data from both Salesforce and G Suite or Microsoft, dependent on which platform the organization uses. In most cases, Atrium pulls email data from the preferred email platform, but in cases where multiple email accounts are being used or emails are not being sent directly through the preferred email platform, then email data can be pulled from Salesforce. A quick way to verify where we are pulling this data for your organization is to send our Support team an email at Support@atriumhq.com, or even better, hop on chat in the top right corner during business hours!
It's important to note here that Atrium does not adjust or alter any data in any way, we simply mirror what is taking place within Salesforce and G Suite or Microsoft based on the fields mapped in Atrium.
Many Atrium clients have a third-party integration working seamlessly with Salesforce and their preferred email platform and Atrium works alongside to collect that data. Here are a few examples -
While Atrium works alongside any third-party integration setup for your organization, we do not pull data directly from any third-party integrations at this time.
Why is Email Data Incorrect in Atrium?
Scenario 1:
Scenario 2:
If there is a clear data inconsistency, the first step is to pull a report from Atrium that can be used to compare to either Salesforce or email platform data. It's recommended to work with a small subset of data in order to identify a clear pattern, such as highlighting one rep and one week. Here's a video recording of the process to pull an email report for one rep for one week -
{INSERT VIDEO}
From here, it is recommended to use this report as a comparison to either the email platform or Salesforce, wherever email data is being pulled.
Based on the comparable reports, are any patterns emerging? Here are three very common examples of inconsistency highlighted by the method above -
- A new rep has been added to the team, however their email data sync preferences were not set up in Outreach
- The settings for a new email outreach campaign were not set to send copies of outgoing emails to Microsoft
- A new email domain being used for outreach in Yesware was not set up to create email tasks in Salesforce
All of these examples will cause a data discrepancy in the respective platform email data is being pulled, and all were solved quickly as Atrium is able to mirror that data easily.
If, however the above steps do not lay out a clear path for resolution or there are other email data discrepancies taking place then it is best to alert Atrium Support of the matter.
Scenario: When all the above does not apply, Atrium Support will help resolve the inconsistencies.
Please send the following information to Atrium Support via email support@atriumhq.com
- The URL to the Atrium email card
- [[screenshot annotated showing what that is]]
- A screenshot of an example of an email that is not being logged in Atrium, including the subject line, recipients, and date + time sent
- Google example screenshot
- Microsoft example screenshot
- Salesforce Task including the URL visibility and task ID
- example screenshot
- Any details on what was expected in Atrium vs. what it's showing in reality
- Example: "I expected that Atrium would show more than 0 emails sent by Rep A this week, as I know they've been sending outbound emails."
- Example: "