What Should I Consider When Using Salesforce Related Fields?
Last updated: November 12, 2026
Metrics often use related field when they have a sophisticated configuration to pulls from multiple Objects, such as an Opportunity Object-based metric that also pulls fields from the Event and Account Objects. While Related Fields can help to source more data from your team, it's important to note that updating a Parent Object doesn't update the Child record, which can sometimes lead to stale or out-of-date data in Ambition.
Required permissions:
The Integrations: Edit permission is required to sync Related Fields.
Turn On Related Fields
Navigate to Admin --> Data --> Integrations.
Open the Enabled tab and click on the Salesforce integration.
Click on Data Configuration, then click on Edit next to the Object.
Turn on the Sync Related Fields toggle.
Click on Update Object.
Limitation of Using Related Fields
Ambition only receives an updated Salesforce record when the corresponding record on the main Object is updated.
For example, a metric may be built from the Opportunity Object, but pull Related Fields from the Account Object. Ambition will not receive an updated record if the corresponding Account record is changed. Instead, Ambition will only receive an updated record if the Object record changes.
Filters on a related record itself, such as an Opportunity's Campaign, stay in sync because changing that link updates the Opportunity.
If your metric uses Related Fields from multiple objects, you could also consider syncing a report to Ambition and building the metric from the report to circumvent the field update limitation.
Note:
It's best to use Related Fields only for those fields whose values rarely change. If you must use one that changes often, ask a Salesforce admin to add a trigger on the parent Object that updates the related child records.