Considerations for Setting up Revenue Insights

Requirements to Install Revenue Insights

• Enable data sync or direct data.
• Your org needs at least one record of each of these objects: Account, Opportunity, User, UserRole, Task, and Events.
• Role hierarchy must be set up with at least two layers. For example, you have one Sales Manager and one Sales Rep.
• Because Revenue Insights uses security predicates in its models, you must set it up from the Setup menu rather than Analytics Studio. This best practice ensures that all records in the dataset are used when training the models. Running setup from Analytics Studio can result in inaccurate or failed models

Note Even if you use Territory hierarchy, you must have set up a role hierarchy.

Requirements to Include Forecast Data

Forecast data comes from Salesforce Forecasting, a feature of Sales. When you set up forecasting, you create and activate a forecast type.

• You must have an active forecast type that matches one of these types:

  OBJECT	MEASURE*	DATA TYPE	HIERARCHY
  Opportunity	Currency	CloseDate (standard)	Role hierarchy
  Opportunity Splits	Currency	CloseDate (standard)	Role hierarchy
  Opportunity	Currency	CloseDate (standard)	Territory hierarchy

  

  Note *Revenue Insights supports the standard Amount field or a custom field of type Currency.
• For a role hierarchy-based forecast, go to Setup > Forecast Hierarchy and assign forecast managers to at least two layers.
• For a territory hierarchy-based forecast, go to Setup > Sales > Territories > Territory Models and assign forecast managers to at least two layers.
• Go to Forecasts > Quota and load at least one quota value for your forecast type.
• If your forecast type is based on the Opportunity Splits object, you must have at least one Opportunity Split record.
• The measure you use in your forecast type must have historical trending enabled on the opportunity object. If you use an opportunity split, ensure that the associated rollup field on the opportunity object is trended.

Requirements to Include Forecast and Quota Data

Quota data comes from Salesforce Forecasting, a feature of Sales. Or, you can upload quota data from a CSV file, which allows you to use quota data stored outside of Salesforce. If you use Salesforce Forecasting, see the notes in Requirements to Add Forecast Data. To use a CSV file: Create a CSV file with your quota data and save it. Then, navigate to the CRMA Analytics Studio > quota dataset. Edit the dataset by uploading your CSV file, which replaces the default quota dataset. To ensure the recipe runs again and pulls in your quota data, refresh the app.

Requirements and Considerations to use Forecast Insights Dashboards

Forecast Insights dashboards are populated from Salesforce Forecasting, a feature of Sales. Forecasts must be enabled and configured to use Forecast Insights. Territory forecasts aren’t supported. Opportunity split-based forecasts aren’t supported.

Requirements to Use a Standard Fiscal Year

If you use a standard fiscal year, enable the fiscal year configuration for CRMA recipes in the Data Prep settings. For details about how to configure fiscal year settings, For more information about Einstein Discovery specified limits, see Data Prep Configuration.

After Installing Revenue Insights

After installing Revenue Insights, navigate to App Launcher > Data Manager and follow steps to schedule data sync and recipes.

Note When you turn on CRM Analytics for your org, a default Analytics Integration User is created. This "user" accesses the data within Salesforce when the recipe is used to bring data in as datasets to CRM Analytics. It's important that this user has the proper level of permissions to access your data. For example, the integration user needs have object level access to all the objects from which data you want to pull, and field level access to the fields within those objects. If you have trouble in creating your app or can’t view data, you sometimes must modify either object or field permissions to allow the integration user to access them.