Data in Salesforce From Other Platforms
Data in Salesforce
Ambition interacts with data from third-party platforms in the same way we interact with standard Salesforce Objects and Fields!
The data Ambition queries is always completely dependent on the Organization's specific selection criteria and set up.
Ambition currently has customers who have successfully sent data from Salesforce to Ambition from the following platforms:
Update time in Ambition will be dependent on how the respective platform interacts with Salesforce. Ambition is integrated with Salesforce, so data points will have to first be in Salesforce before Ambition can begin querying data and making updates in Ambition.
Any helpful hints for when Salesforce is sending Outreach data to Ambition?
Outreach data is commonly represented in Salesforce as Task Records.
Task records generated by Outreach will have Subjects that begin with [Outreach].
The Type of Activity is also commonly present in the Subject. Examples [Outreach][Call] or [Outreach][Activity: Email].
↳ Example of filtering for Outreach generated Subjects in the Metric Builder.
Learn more about structuring Outreach data in Salesforce here.
Any helpful hints for when Salesforce is sending SalesLoft data to Ambition?
SalesLoft data can be represented in Salesforce as Account, Activity, and Opportunity records.
The data points that can be utilized in Ambition are entirely dependent on the fields that are mapped from SalesLoft to Salesforce.
It's important to note that while customizable, the default sync between SalesLoft and Salesforce is 10 minutes. Ambition can only be as real-time as the data in Salesforce, so it's important to be mindful of the SalesLoft <> Salesforce sync frequency.
Learn more about how Salesforce and SalesLoft can interact here.
Any helpful hints for when Salesforce is sending Gong data to Ambition?
Gong data is commonly represented in Salesforce as a custom Object, Gong Call Records.
Gong Trackers can be utilized in Ambition Metric Logic as filters.
While a Gong Call can be recognized as having specific Gong Trackers present, the number of times the Tracker is used in the call cannot be tracked at the current time.
Trackers are commonly sent to Ambition in JSON form in the
↳ Utilize a Metric Filter with the "Contains" operator in order to access Trackers within the JSON.
Any helpful hints for when Salesforce is sending DialSource data to Ambition?
DialSource data will most often be represented in Salesforce through several custom Objects, DialSource Sessions, DialSource Offer, and DialSource Actions.
Learn more about how DialSource works with Salesforce here.
Any helpful hints for when Salesforce is sending ringDNA data to Ambition?
RingDNA data is commonly represented in Salesforce as Task Records.
Task records created by ringDNA will commonly have a boolean field, Created By RingDNA, present.
↳ Example of filtering for ringDNA generated Tasks in the Metric Builder.
Data from Sources Outside of Salesforce
If the platform your Organization utilizes does not send data to Salesforce, an API, FTP, File Upload, or Manual Entry integration can be incorporated in order to deliver those data points to Ambition.
Reach out to firstname.lastname@example.org if you have any questions about setting up a new integration in Ambition.