Enable the sync of Account Spike data to your Salesforce
Keep in mind that integrating RollWorks with Salesforce will not automatically initiate the generation of Account Spike data. You must take additional steps to ensure that RollWorks starts detecting Account Spikes for your Salesforce accounts and to start syncing Account Spike data to your Salesforce instance.
To enable the sync of Account Spike data to your Salesforce instance you must complete the setup steps documented in this Sales Insights Initial Configuration Guide.
To learn more about the Sales Insights seat assignment conditions required for RollWorks to generate Account Spike data click here.
Account Spike Data available in Salesforce
When an account spike is detected by our Account Spike data science model we will generate different data attributes (Spike Level, Last Spike Date, Spike Raw Score, Spike Score Reason, and Matched Contacts). We refer to these different data attributes as Account Spike data.
Account Spike data is then synced to Salesforce daily so that your sales team always has a fresh view of their top spiking accounts. We will write account spike data in the 'RollWorks Account Data' custom object.
Keep in mind that the Account Spike data attributes below are calculated on business days only (Monday to Friday).
| Custom fields
✍️ 'Spike Level' is the primary data point that should be utilized by your Sales team to prioritize accounts spiking in engagement. We use machine learning to establish Account Spike thresholds as Low, Medium, or High. These Spike Levels are dynamic and responsive to the volume of organic site traffic for your site to ensure that when accounts are flagged as 🔥🔥🔥 High, 🔥🔥Medium, or🔥Low for spike activity, it is compared to your own organic website engagement.
|Last Spike Timestamp
✍️ You should always use 'Last Spike Timestamp' in combination with Spike Level to prioritize Accounts with recent spikes. Shows the last time an account spiked in engagement. Shows the last time an account spiked in engagement.
|Spike Had Matched Contacts
|This is a true/false boolean field that indicates if we were able to match the engagement Spike for this Account to any of your existing CRM contacts at the moment the Spike happened. Learn more about how matched contacts work here.
|Spike Raw Score
|The output of the data science model looks at various inputs of account engagement. This score is a number between 0-100 that is used to calculate Spike Level and is only visible to CRMAdmins.As a Sales Insights user, you will most likely not use this data, instead, you will use 'Spike Level'.
|Spike Score Reason
|This field refers to the engagement actions that occurred leading to the account spiking. For example # of ad clicks, # of unique visitors, # of conversion page views.
|Last Modified date
|Shows the last time Spike engagement data was pushed to your CRM.