Skip to main content

Backstory Salesforce Managed Package Overview

Information regarding the Backstory Managed Package with Salesforce

The latest version (4.16) of Backstory's managed package is available here.

Overview

The Backstory Managed Package includes custom fields, an apex trigger, Visualforce components, reports, and a permission set. Additionally, the managed package includes apex classes. These cover a variety of data points measured by Backstory and populated into Salesforce via REST and Bulk APIs. Details and descriptions for most of the metadata added by Backstory are included below.

Tip: It is always recommended that the managed package be installed in a sandbox before being installed on a production instance.

Contact your CSM or Backstory Support for the latest managed package version you should consider installing on your sandbox or production instance.

Backstory Custom Fields

The Backstory User permission set must be granted to your organization's integration user so that Backstory can view and push values to these fields.

Note: Backstory's custom fields introduced in version 2.9 are referred to as "summary fields".


After applying the permission set, please contact support@backstory.ai to enable summary field push for your organization.

Custom Fields on Activity [12]

API Name

Description

Available From

peopleai__ActivityType__c

The type of activity that is being synced will be classified as 'Received Email', 'Sent Email', 'Cold Email', ‘Blast Email', ‘In-Person’, or ‘Conference Call’.

1.6+

peopleai__Created_by_PeopleAI__c

Boolean marker for all Activities (Tasks and Events) created or updated by Backstory.

1.6+

peopleai__Direction__c

Defines whether the activity is "Inbound" or "Outbound" in Backstory. This is populated for Tasks created by Backstory.

1.6+

peopleai__ExternalId__c

Unique ID from Backstory that designates each activity.

1.6+

peopleai__From__c

The email of the originator of the activity.

1.6+

peopleai__To__c

The email of the recipient or list of recipients is delimited by commas. This is populated for Tasks created by Backstory.

1.6+

peopleai__Participants__c

The list of recipients for emails and attendees for meetings.

1.6+

peopleai__Timestamp__c

Timestamp of when the activity occurred.

1.6+

peopleai__OpportunityStage__c

The stage of the matched open opportunity at the time of activity sync. This is populated for Tasks & Events created by Backstory that match an Opportunity (WhatID = Opportunity)

2.8+

peopleai__MeetingStatus__c

Status of a scheduled meeting. Possible values are 'Scheduled', 'Rescheduled', 'Canceled', or 'Completed'. This is populated for Events created by Backstory.

1.8+

peopleai__MeetingChanged__c

The timestamp for when the event was last updated on Gmail or the O365 calendar. This is populated for Events created by Backstory.

1.8+

peopleai__ManualCallDurationInMinutes__c

Call duration in minutes converted from Salesforce standard field 'CallDurationInSeconds'
(This field is deprecated)

1.6+

Custom Fields on Account [11]

API Name

Description

Available From

peopleai__EngagementLevel__c

A numerical representation of sales engagement based on activities captured by Backstory.

3.11

peopleai__FirstTouch_c

The date/time of the first activity on the object (which was logged by Backstory).

2.9+

peopleai__LastTouch__c

The date/time of the last touch on the object (which was logged by Backstory)

1.8+

peopleai__LastEmailReceivedDate__c

The date/time of the last inbound email on the object (logged by Backstory).

2.9+

peopleai__LastEmailReceivedFrom__c

The email of the person who sent the last inbound email (which was logged by Backstory).

2.9+

peopleai__LastEmailSentDate__c

The date/time of the last outbound email on the object (logged by Backstory).

2.9+

peopleai__LastEmailSentFrom__c

The email of the person who sent the last outbound email (logged by Backstory).

2.9+

peopleai__LastMeetingDate__c

The date/time of the last meeting or call on the object.

2.9+

peopleai__NextMeetingDate__c

The date/time of the next meeting on the object (logged by Backstory).

2.9+

peopleai__TotalTimeSpent__c

This is a reserved field for future use. The total time spent on an Account (converted to a readable format from 'Time Spent in Seconds' via APEX trigger).

1.8+

peopleai__TimeSpent__c

This is a reserved field for future use. The total time spent (in seconds) on an Account.

1.8+

Custom Fields on Opportunity [12]

API Name

Description

Available From

peopleai__EngagementLevel__c

A numerical representation of sales engagement based on activities captured by Backstory.

3.11

peopleai__FirstTouch_c

The date/time of the first activity on the object (which was logged by Backstory).

2.9+

peopleai__LastTouched__c

The date/time of the last touch on the object (which was logged by Backstory)

2.10+

peopleai__LastEmailReceivedDate__c

The date/time of the last inbound email on the object (logged by Backstory).

2.9+

peopleai__LastEmailReceivedFrom__c

The email of the person who sent the last inbound email (which was logged by Backstory).

2.9+

peopleai__LastEmailSentDate__c

The date/time of the last outbound email on the object (logged by Backstory).

2.9+

peopleai__LastEmailSentFrom__c

The email of the person who sent the last outbound email (logged by Backstory).

2.9+

peopleai__LastMeetingDate__c

The date/time of the last meeting or call on the object.

2.9+

peopleai__NextMeetingDate__c

The date/time of the next meeting on the object (logged by Backstory).

2.9+

peopleai__TotalTimeSpent__c

This is a reserved field for future use. The total time spent on an Opportunity (converted to a readable format from 'Time Spent in Seconds' via APEX trigger).

1.8+

peopleai__TimeSpent__c

This is a reserved field for future use. The total time spent (in seconds) on an Opportunity.

1.8+

peopleai__LastTouch__c

The date of the last touch on the object (logged by Backstory
(This field is deprecated.)

1.8 - 2.9

Custom Fields on Opportunity Contact Role [1]

API Name

Description

Available From

peopleai__Created_by_PeopleAI__c

A Backstory-generated Boolean marker that shows that Backstory created the record.

3.11

Custom Fields on Contact [19]

API Name

Description

Available From

peopleai__EngagementLevel__c

A numerical representation of sales engagement based on activities captured by Backstory.

3.11

peopleai__FirstTouch__c

The date/time of the first activity on the object (which was logged by Backstory).

2.9+

peopleai__LastTouch__c

The date/time of the last touch on the object (which was logged by Backstory)

2.9+

peopleai__LastEmailReceivedDate__c

The date/time of the last inbound email on the object (logged by Backstory).

2.9+

peopleai__LastEmailReceivedFrom__c

The email of the person who sent the last inbound email (which was logged by Backstory).

2.9+

peopleai__LastEmailSentDate__c

The date/time of the last outbound email on the object (logged by Backstory).

2.9+

peopleai__LastEmailSentFrom__c

The email of the person who sent the last outbound email (logged by Backstory).

2.9+

peopleai__LastMeetingDate__c

The date/time of the last meeting or call on the object.

2.9+

peopleai__NextMeetingDate__c

The date/time of the next meeting on the object (logged by Backstory).

2.9+

peopleai__Created_by_PeopleAI__c

Boolean marker for all Contacts created or updated by Backstory.

1.6+

peopleai__ExternalId__c

Unique ID from Backstory that designates each person.

1.8+

peopleai__Seniority__c

The Backstory-classified seniority of the contact’s job title

3.10

peopleai__Department__c

The Backstory-classified department of the contact’s job title

3.10

peopleai__Persona__c

The Backstory-classified persona (seniority and department) of the contact’s job title

3.10

peopleai__NumInboundEmails__c

The total number of emails sent by the contact, as captured by Backstory.

3.10

peopleai__NumOutboundEmails__c

The total number of emails sent to the contact from your organization,n as captured by Backstory

3.10

peopleai__NumMeetings__c

The total number of meetings with the contact as captured by Backstory.

3.10

peopleai__TotalTimeSpentInSeconds__c

The total time spent with the contact (in seconds) as classified by Backstory.

3.10

peopleai__LastUpdated__c

The time the contact was last updated by Backstory in Salesforce.

3.10

Custom Fields on Lead [11]

API Name

Description

Available From

peopleai__EngagementLevel__c

A numerical representation of sales engagement that is based on activities captured by Backstory.

3.11

peopleai__FirstTouch__c

The date/time of the first activity on the object (which was logged by Backstory).

2.9+

peopleai__LastTouch__c

The date/time of the last touch on the object (which was logged by Backstory)

2.9+

peopleai__LastEmailReceivedDate__c

The date/time of the last inbound email on the object (which was logged by Backstory).

2.9+

peopleai__LastEmailReceivedFrom__c

The email of the person who sent the last inbound email (which was logged by Backstory).

2.9+

peopleai__LastEmailSentDate__c

The date/time of the last outbound email on the object (which was logged by Backstory).

2.9+

peopleai__LastEmailSentFrom__c

The email of the person who sent the last outbound email (which was logged by Backstory).

2.9+

peopleai__LastMeetingDate__c

The date/time of the last meeting or call on the object.

2.9+

peopleai__NextMeetingDate__c

The date/time of the next meeting on the object (which was logged by Backstory).

2.9+

peopleai__ExternalId__c

Unique ID from Backstory that designates each person.
(This field is deprecated.)

1.8+

peopleai__Created_by_PeopleAI__c

This is a reserved field for future use. Boolean marker for all Leads created or updated by Backstory.
(This field is deprecated)

1.6+

Backstory Custom Objects [1]

API Name

Description

Available From

peopleai__Email_Status__c

Used to identify invalid email addresses of contacts who have left a company.

3.7+

Backstory Apex Triggers [1]

Name

Parent Object

Available From

UpdateCallDurationFieldTrigger

Task

1.6+

Backstory Permission Set [1]

If your organization chooses not to grant the View All Data permission to your integration user, the permission set below must be applied.
If View All Data is granted to the integration user, please disregard this section.

Name

Description

Available From

People_ai_User

This permission set should be assigned to the Backstory Integration User to allow Backstory access to custom fields introduced as part of our managed package.

3.1+

Backstory Report Folder [1] + Reports [3]

Name

Description

Available From

Backstory Reports

Report folder created by the Backstory managed package to hold all reports added by our managed package

3.1+

Backstory Activity (Today)

Activities (Tasks and Events) logged by Backstory today

3.1+

Backstory Contact Created (Last 30 Day)

Contact created by Backstory in the last 30 days

3.1+

Backstory Contact Roles Added

Contact Roles added by Backstory on Open Opportunities

3.1+

Note: The Backstory Report Folder is only visible to System Administrators by default. Please get in touch with your Salesforce Admin to update folder viewing permission if it is not visible in Reports.

Backstory Visualforce Pages [4]

Name

Description

Available From

AccountSection

A Visualforce page that aggregates the Backstory summary fields at the Account Object. This VF is Lightning Ready. Administrators should add the AccountSection VF page to the corresponding Account page layouts, as required.

2.12+

OpportunitySection

A Visualforce page that aggregates the Backstory summary fields at the Opportunity Object. This VF is Lightning Ready. Administrators should add the OpportunitySection VF page to the corresponding Opportunity page layouts, as required.

2.12+

ContactSection

A Visualforce page that aggregates the Backstory summary fields at the Contact Object. This VF is Lightning Ready. Administrators should add the ContactSection VF page to the corresponding Contact page layouts, as required.

2.12+

LeadSection

A Visualforce page that aggregates the Backstory summary fields at the Lead Object. This VF is Lightning Ready. Administrators should add the LeadSection VF page to the corresponding Lead page layouts, as required.

2.12+

Lighting Components

  • WPaiCanvasFullApp

  • WPaiCanvasAccount360 (Backstory: Account 360)

  • WPaiCanvasOppty360 (Backstory: Opportunity 360)

  • WPaiCanvasDealRoom (Backstory: Deal Room)

  • WPaiCanvasPerfMy (Backstory: My Performance)

  • WPaiCanvasPerfTeam (Backstory: Team Performance)

Lightning Tabs

  • PeopleAiAppTab

Connected App

  • PeopleAiCanvasApp (Backstory: Canvas App)

APEX Classes

  • CanvasHandler.cls

  • CanvasHandlerTest.cls

Granting Login Access to Backstory

During onboarding, Backstory may request access to your Salesforce instance for support and debugging purposes. With our Managed Package, you can Grant Account Login Access directly from your Salesforce settings.

You can read more in Salesforce: How to Grant Login Access

Post Installation Steps & Considerations

  1. Grant Permission Set to Backstory Integration User (Required)
    ​The managed package includes a predefined permission set called People_ai_User. This permission set should be assigned to the Backstory integration user so that Backstory can access custom fields included in the managed package. Assign this permission set immediately after installing the package to enable the CRM sync to function correctly.

  2. Check additional permissions required for Backstory Integration User (Required)
    If you have APEX Triggers, Workflows, or Process Builder Workflows on any objects that Backstory creates or updates, you may need to grant the Backstory integration user additional permissions.

  3. Add Visualforce pages to respective page layouts (Optional)
    Backstory Visualforce pages enable organizations with valuable activity data and insights. Considering your organization may have custom page layouts for specific profiles, please feel free to add these Visualforce pages to page layouts at your own discretion.

  4. Add Backstory fields to Activity History Related List (Optional)

    We would recommend that you make the following fields visible in all tables so that your team knows which activities were automatically synced by Backstory.

    • peopleai__Created_By_People_ai__c

    • peopleai__Direction__c

    • peopleai__Timestamp__c

Did this answer your question?