Legacy: What are the Differences between Salesforce Managed Package and Salesforce on Platform?

🔍 Please note: This article is for customers on Standard Bundle, Enrichment, or Clearbit Platform plans. If you signed up in 2024, you are on a Sales Intelligence for HubSpot plan: Free, Growth, or Business.

Last Updated: September 27, 2023

On February 15, 2022 Clearbit launched Salesforce on Platform. This article details the differences between Salesforce on Platform and the legacy Salesforce managed package.

Skip Ahead to

Before: Lightning Field Mapping After: Platform Field Mapping
Screen_Shot_2022-11-09_at_4.09.52_PM.png Screen Shot 2023-10-25 at 2.00.31 PM.png
Before: Salesforce Enrichment Logs After: Platform Enrichment Logs
Screen_Shot_2022-11-09_at_4.12.11_PM.png Screen_Shot_2022-11-09_at_4.12.58_PM.png

Benefits of Salesforce on Platform

  • Better implementation experience. Implement and manage your Salesforce configuration within the platform. No Salesforce packages to install.
  • Improved troubleshooting with detailed enrichment logs. Search, assess, and fix data sync and data-driven process problems with detailed enrichment logs that show statuses, errors, and field-level changes.
  • New attributes. Salesforce Enrichment now takes advantage of platform capabilities, like audience building and engagement data, to unlock new attributes. You can use these attributes to better prioritize your pipeline, profile companies, and people, and create custom true/false attributes.

Known Limitations of Salesforce on Platform

  • Does not support EU exclusion
  • Does not support Lightning components
    • Enrichment Widget (Enrichment, Activity, Details, Chatter, News)
    • Prospector Widget
  • Does not support Freemail Exclusion Settings
  • Does not support Custom Enrichment Schedules
  • Does not include a Health Check Report
  • Does not include pre-built reports (e.g. Clearbit Recent Inactives)

Feature Comparison

Feature Salesforce on Platform Salesforce Managed Package
Live Enrichment Included Included
Backfill Enrichment Included Included
Custom Enrichment Schedules Not Included Included
Enrichment Reporting Limited, Planned Included
Enrichment Logs Enhanced Included
Change History Logs Not Included Included
Clearbit Lightning Page Not Included Included
Clearbit Status Widget Not Included Included
Enrichment Field Mapping Included Included
Conditional Overwrite Included Included
Tech Tag Whitelisting Not Included Included
Freemail Exclusion Settings Not Included Included
Company Clearbit Traits Included Included
Company Engagement Metrics Included Not Included
Company Custom Audience Traits Included Not Included
Person Clearbit Traits Included Included
Person Engagement Metrics Included Not Included
Person Custom Audience Traits Included Not Included
System Traits Enhanced Limited

How Can I Control Clearbit’s Access to Private Records & Fields?

Clearbit recommends creating and using an Integration User when integrating with Salesforce. This allows you to apply granular User Permissions and Sharing Rules to define when Clearbit can or cannot read and write to Salesforce records.

Salesforce Enrichment requires both read and write access to successfully enrich records.

Required Read Access

We require read access to the email and/or domain fields on any record you would like to enrich. Like our APIs, these fields are the key we use to identify and find information on people and companies.

Lead Email
Contact Email
Account Website

Required Write Access

Clearbit requires write access to any record that you would like to enrich. Similarly, Clearbit requires both read and write access to any fields on those records that you hope to enrich. Read access surfaces the field for mapping, and write access allows us to update the field on that record.

Limiting Access to Records and Fields

You can apply User Permissions to restrict access to record types and fields. For example, if you would like to restrict access to all Account fields, you can do so by restricting Read/Write access for the Integration User.

For complex sharing rules (e.g. if an organization needs to restrict access to records or fields when certain conditions are met), Salesforce Admins can set up Sharing Rules to only grant read/write access on a conditional ruleset.

How Can I Test in a Sandbox Environment? How Can I Transition from Sandbox to Production?

If you need to test the integration in a Sandbox environment, we recommend that you create and use a separate Clearbit account for testing.

This will ensure that the Sandbox data ingested into your account does not pollute your production environment. This also makes it easy to transition, since Clearbit does not have a method of “flushing” that data once it is in your account.

Once you are satisfied with the outcome of the test, you can authenticate your production Salesforce account with your primary Clearbit account.