CRM Enrichment

CRM Enrichment automatically populates Salesforce records with intelligence signals from Suger — engagement scores and marketplace metrics across AWS, Azure, and GCP — so your sales team gets actionable insights inside Salesforce without leaving the CRM.

Overview

With CRM Enrichment, you can:

• Automatically populate CRM fields with intelligence signals (engagement scores, marketplace metrics)
• Configure multiple record types (e.g., Opportunities, Accounts) with different enrichment rules
• Use SOQL queries to target specific records for enrichment
• Map intelligence fields to custom Salesforce fields

Prerequisites

Before configuring enrichment, ensure you have:

1. Custom fields created in Salesforce to store the intelligence data.
2. Integration User permissions on the permission set used by Suger:
   • Field-level read and edit access on every custom field you add for enrichment.
   • Modify All Records permission on each object you plan to enrich (e.g., Account, Opportunity). This is required because enrichment updates records that the Integration User did not create.

Creating Custom Fields in Salesforce

You need to create custom fields in Salesforce to store the intelligence signals. For each signal you want to sync:

1. Go to Setup → Object Manager → Select your object (e.g., Account, Opportunity)

   

2. Click Fields & Relationships → New

   

3. Choose the appropriate field type (e.g., Text for scores and general data)

   

4. Enter a Field Label (e.g., “Azure Engagement Score”)

   

5. Configure field-level security to allow the Integration User to read and write

6. Add the field to your page layouts as needed

Configuring Enrichment

1. Navigate to Suger Console → Settings → Integrations → Salesforce
2. Click Edit to open the integration settings
3. Go to the Enrichment tab
4. Click Add CRM Record to create a new enrichment rule

For each configuration, specify:

After entering your query, click Validate Query to verify it is valid and see how many records match. This helps ensure your enrichment rule targets the right set of records before saving.

Available Intelligence Fields

Intelligence signals are derived from multiple data sources:

• Cloud partner data — Engagement scores sourced directly from cloud partner programs (e.g., AWS Partner Network, Azure Partner Center, GCP Partner Advantage).
• Marketplace activity — Public marketplace metrics such as listing counts, review counts, and purchase history across AWS, Azure, and GCP marketplaces.

The following intelligence signals can be mapped to your CRM fields:

AWS Signals

• AWS Engagement Score
• AWS Marketplace Count
• AWS Marketplace Review Count
• AWS Marketplace Purchase Count

Azure Signals

• Azure Engagement Score
• Azure Event Score
• Azure Usage Score
• Azure Marketplace Count
• Azure Marketplace Review Count
• Azure Marketplace Purchase Count

GCP Signals

• GCP Engagement Score
• GCP Marketplace Count
• GCP Marketplace Review Count
• GCP Marketplace Purchase Count

Example Configuration

To enrich Opportunities in the Prospecting stage with AWS engagement data:

1. CRM Record Type: Opportunity
2. Field Mappings:
   • AWS Engagement Score → aws_engagement_score
3. SOQL Query: SELECT Id FROM Opportunity WHERE StageName = 'Prospecting'

How Enrichment Works

Sync Schedule

Suger runs a scheduled enrichment sync every 12 hours (at midnight and noon UTC). During each sync, Suger automatically processes all configured enrichment rules for your organization.

Enrichment Process

Each sync goes through the following steps:

1. Query your Salesforce org using the configured SOQL query to identify records that need enrichment.
2. Look up intelligence data for each matching record based on the company’s website domain.
3. Update the mapped fields in Salesforce with the latest intelligence values.

Update Mechanism

Suger uses a smart two-step approach to ensure efficient and complete data coverage:

• Step 1 — Enrich new records: Every sync prioritizes records that have not been enriched yet (where the mapped fields are still empty). This ensures newly added or previously missed records receive intelligence data first.
• Step 2 — Refresh existing records: Once all new records have been enriched, Suger begins a refresh cycle — rotating through previously enriched records in batches to keep data up to date. This rotation continues across multiple syncs until all records have been refreshed, then a new cycle begins.

The Refresh Existing setting controls how the refresh cycle behaves:

Records Per Sync

Each sync processes up to a configurable maximum number of records. For Salesforce, the default is 10,000 and can be increased up to 50,000. The minimum configurable value is 1,000.

If your query matches more records than the configured limit, the remaining records are handled automatically:

• New records (Step 1): Unenriched records will be picked up in the next sync since they still have empty fields — no progress tracking is needed.
• Refresh cycle (Step 2): Suger tracks its cursor position across syncs to rotate through all records. For example, with 100,000 records and a limit of 50,000 per sync, the refresh cycle completes in 2 runs. Once a full cycle finishes, the next one starts based on your Refresh Existing setting.

Tracking Enrichment Progress

To monitor the status of your enrichment sync:

1. Go to the enrichment configuration for your record type
2. Expand Advanced Configuration
3. Click Check Progress

The progress panel shows:

Disabling Enrichment

To stop enrichment for a specific record type, toggle it off in the enrichment configuration. This removes the enrichment rule, and no further syncs will process that record type.

To temporarily pause enrichment without removing the configuration, set Refresh Existing to Never — this will only enrich new records with empty fields and skip all previously enriched records.