Skip to main content

Validating Backstory Data

A crucial part of onboarding Backstory is data validation. Your Sales Process Analyst will need to validate, both in-app and in Salesforce, that Backstory has been properly configured to capture and sync all sales activity. Data validation will occur twice during onboarding–once in your Salesforce sandbox environment, and again after Backstory is connected to your production instance.

Backstory Functionality in Sandbox

The quality and accuracy of activity matching in your sandbox environment is directly related to the amount of time since your last Salesforce refresh. The more recent the refresh, the more realistic the results will be.

You can read more about what to expect when connecting Backstory to a Salesforce Sandbox environment here.

Verifying Backstory Data In-App

To aid validation efforts during onboarding, we’ve compiled a set of questions and steps to follow in the application that will ensure that Backstory is effectively processing your organization’s data.

Is Backstory ingesting my team’s email and calendar data?

  1. Open the Team Page.

  2. Click on any user to expand the activity feed.

  3. Compare activities to the user’s mailbox and calendar.

Has Backstory pulled all of my organization’s Salesforce data?

  1. Open the CRM Scan page.

  2. Compare the total number of Accounts listed to that of your Salesforce instance.

  3. Repeat on each respective page of the CRM Scan module.

Is Backstory accurately matching emails and meetings to objects in Salesforce?

  1. Open the Insights page.

  2. Click on the Meetings card to view meetings in the activity log.

  3. Confirm whether meetings are matched to the correct Salesforce object.

  4. Click on the Emails card to view emails in the activity log.

  5. Confirm whether emails are matched to the correct Salesforce object.

In the case that activities are matched to the incorrect object, you can re-match them to the correct one by clicking the three dots next to the activity.

To learn more about Sync Clouds, please click here.


Is Backstory pulling calls that are logged in Salesforce?

  1. Open the Team Page.

  2. Filter Activity Type for Calls only.

  3. Click on any user to expand the activity feed.

  4. Compare activities to the user’s logged calls in Salesforce.

To learn more about displaying calls in Backstory, click here.

Verifying Backstory Data in Salesforce

After enabling activity sync and record creation, you can run custom reports in Salesforce to answer the questions below and validate People Sync functionality.

  • Is Backstory automatically syncing external activities to Salesforce?

  • Is Backstory automatically creating new Contacts in Salesforce?

  • Is Backstory automatically creating new Contact Roles on Opportunities in Salesforce?

To learn more about building reports in Salesforce, click here.

Things to Consider During Validation

  • Backstory ingests internal and external activities, but only syncs external activities to Salesforce.

  • Backstory requires certain fields to be completed to pull calls from Salesforce.

  • Data ingestion and sync cycles may take up to a few hours to complete when there is a large volume of data.

  • Clicking any metrics card on the Insights page displays the Activity Log, showing external activities only.

The Backstory onboarding team will be available to answer questions and address unexpected behaviors observed during validation. Once your team’s questions are resolved, you will exit the validation phase and continue toward launch!

If you have any additional questions about data validation, please reach out to support@backstory.ai.

Did this answer your question?