Integrate, Automate, and Innovate With
DiGGrowth-Salesforce Connector

To sync DiGGrowth with Salesforce, important data fields include:

Account: Account Name, Owner, Industry, Revenue, Employees, Address.

Contact: Name, Title, Email, Phone, Account Name, Lead Source.

Lead: Name, Company, Title, Email, Status, Source, Industry.

Opportunity: Opportunity Name, Account Name, Close Date, Stage, Amount.

Case: Case Number, Contact Name, Status, Priority, Subject.

Campaign & Campaign Member: Campaign Type/Subtype, Member Status (e.g., registered, attended).

Yes, custom objects and fields in Salesforce require special handling during integration, particularly if they are needed for DiGGrowth reports. Custom fields added to standard objects (e.g., Account, Contact, Opportunity) or entirely custom objects with unique data are managed using DiGGrowth’s segment manager to build segments and apply them to dashboards.

Data between Salesforce and DiGGrowth should ideally be synced daily to keep reports and dashboards current. However, the optimal sync frequency may vary based on data volume and specific business requirements. For critical updates or time-sensitive data, more frequent syncing (e.g., real-time) might be necessary.

Yes, there are Salesforce limitations that could affect integration with DiGGrowth:

API Limits: Daily API call restrictions can impact frequent syncs.

Storage Limits: Data and file storage constraints may restrict large data transfers.

Batch Processing: Rate limits necessitate syncing large datasets in smaller batches.

Field and Object Limits: Restrictions on fields per object may limit available data for syncing.

Permissions: The integration user must have adequate permissions to access necessary fields and records.

Custom Code and Triggers: Custom workflows/triggers could delay or block syncing.

Field Types and Validation: Mismatched data types and validation rules may require data transformations.

Integrating Salesforce data into DiGGrowth enhances revenue and pipeline reporting by using key objects like Opportunities, Accounts, and Campaign Members as primary datasets. Accurate mapping of fields such as Opportunity Amount and Lead Stages ensures precise revenue tracking and funnel analysis. Configuring lookback windows supports historical insights, source attribution, and strategic, long-term trend analysis.

There are no specific security or compliance requirements outlined for the integration. However, to maintain best practices for data security and compliance, it's generally recommended that data be securely transferred, access controls are properly configured, and any relevant industry standards (such as GDPR or data protection policies) are adhered to.