When changing a Metric's logic you have the ability to determine if this change should apply retroactively or moving forward.
This allows your operations team to have maximum flexibility in keeping process changes in-sync with Ambition Metrics.
How is Existing Data Impacted?
If you need the changes applied retroactively you can select a specific date from which the changes should be in place. This will result in Ambition reprocessing your existing historical data back to the chosen date.
In the case where brand new User Fields, Date Fields, or Filters are added to Metric Logic and needed to be applied historically, all relevant data will need to be re-uploaded/re-imported into Ambition in order to accurately reprocess historical Metric values.
Ambition has not been sent records containing the the
Dispatcher User Field until July 10th.
The "Loads Booked" Metric is updated to utilize the
Dispatcher User Field and the Metric is opted to be reprocessed back to July 1st.
Records from July 1st - July 9th without the
Dispatcher User Field will not count towards the "Loads Booked" Metric until the records are updated and resent to Ambition.
Reprocess Historical Data Upon Editing a Metric
These steps begin after a Metric has been edited. If you have questions on accessing an integration's Metric Library navigate:
Here for Salesforce Integrations
Here for API Integrations
Here for FTP Integrations
Here for File Upload Integrations
1. After making the needed changes, click the green Confirm and Save Changes button.
2. A pop-up will appear asking at what point in time the changes just made need to go into effect.
If you do not wish to make changes, click the white Cancel button in the lower left hand corner.
3. Click on the Date dropdown to reveal a Calendar picker.
Select the Date from which you need the Metric changes to be applied.
The Calendar will default to Today's date.
If your Org need the changes put in place historically, select the appropriate day in the past.
If your Org need the changes put in place just from Today on, select Today's date.
↳ view example use case for opting out of historical data here.
Note: We do not support the ability to schedule changes into the future.
5. Verify that the Date selected from which you need the Metric changes to be applied is correct.
6. Click the green Apply Changes button.
How will I know a Metric is Locked?
If a member of your Admin team opted to utilize new Metric logic, subsequently "locking" a Metric, you will be able to view the Lock Date in two places.
Any Metric that have been "locked" will list the respective date, month, and year of the Lock Date.
Incoming records timestamped before the Lock Date will not be processed to preserve historical accuracy, based on the most recent change to metric's logic.
1. Upon accessing each respective Integration's Metric Library you will see a Lock Date column.
2. Within the Metric Builder.
Can a Lock Date be updated?
Once set, a Metric Lock Date cannot be altered by Ambition Users in order to preserve historical accuracy of your Organization's data.
Spot Checking with Lock Dates (Salesforce Integrations only)
If you are attempting to Spot Check a Date which is previous to the Lock Date found under the Metric name the Spot Check will not populate a daily value despite being records in Salesforce being present that would fit the new metric logic.
Lock Date 4/1/2020
Spot Check Date 3/20/2020
Example Use Case for Opting Out of Historical Reprocessing
You are a new company and you're currently using Salesforce and have built an Outbound Calls metric that looks at the Task Object using the logic below.
Subject CONTAINS Outbound Call
This is typically how organizations start out but realize over time it's imperfect, it would be more accurate to transition from the Subject Field looking for a phrase (assuming it was entered correctly) to a Type Field where you simply pick the correct option from a dropdown.
Type EQUALS Outbound Call
You can now transition your Ambition Metric from looking at the Subject Field to the Type Field and maintain historical accuracy by telling Ambition exactly when to take your change into effect. Since the Type field is a new field in your SFDC instance, there is no need to reprocess historical data because the field did not exist.