Salesforce Integration Glossary: Key Terms Every Marketer Should Know

If you've ever sat through a meeting where a developer said "we'll need to map the API endpoints for bidirectional sync" and wondered what planet they were speaking from, this glossary is for you. Understanding Salesforce integration glossary terms isn't just about keeping up with technical conversations (though that helps). It's about making better decisions when choosing marketing tools, avoiding expensive migration headaches, and actually getting your integrations to do what you need them to do.

This glossary focuses specifically on the terms that matter when connecting marketing platforms to Salesforce. We're not covering every Salesforce concept under the sun. Instead, we're zeroing in on the language you'll encounter when evaluating email marketing integrations, event management tools, or document platforms that sync with your CRM.

For more resources on Salesforce marketing integrations, explore our Beaufort 12 articles.

Core Integration Architecture Terms

API (Application Programming Interface) is the communication protocol that allows two platforms to exchange data. When Mailchimp for Salesforce syncs contact details or when Eventbrite sends registration data to your CRM, they're using APIs to speak the same language. Without APIs, platforms would be isolated islands.

REST API and SOAP API represent modern versus legacy Salesforce connection methods. REST is the current standard: faster, simpler, and what most integrations use today. SOAP is older technology you'll occasionally encounter in enterprise environments with legacy systems. If a vendor mentions only SOAP support, that's a red flag for outdated architecture.

OAuth2 authentication is the secure authorisation standard modern integrations use to connect platforms without sharing passwords. Instead of storing your email platform password inside Salesforce, OAuth2 generates temporary access tokens that can be revoked if needed. You authorise once during setup, and the integration handles the rest (including automatic token refresh to maintain connectivity).

Webhook refers to automated notifications sent from one platform to another when specific events occur. When a contact unsubscribes from your email list, a webhook can instantly notify Salesforce to update that contact's status. Webhooks enable real-time data updates rather than waiting for scheduled syncs.

Endpoint is the specific URL where an API receives or sends data. Think of it as a postal address for digital information. When Salesforce sends contact data to an email platform, it's addressing that data to the platform's endpoint.

Rate limiting describes restrictions on how frequently an integration can make API calls. Platforms impose these limits to protect their infrastructure. Understanding rate limits matters when you're syncing large contact databases or running frequent automated campaigns.

Data Synchronisation and Mapping Terms

Sync (synchronisation) is the process of keeping data consistent between Salesforce and external platforms. Update a contact's email address in Salesforce, and sync ensures that change appears in your email marketing platform as well.

Unidirectional sync versus bidirectional sync describes whether data flows one way or both ways. Unidirectional sync might push Salesforce contacts to an email platform but not pull campaign engagement data back. Bidirectional sync keeps both platforms updated with changes from either side. Most marketing integrations use bidirectional sync to capture campaign performance alongside contact management.

Field mapping matches data fields between platforms. When you map 'Email' in your email platform to 'Email' in Salesforce, you're telling the integration which pieces of information correspond. Custom fields in one platform may need mapping to custom fields in another. Good integrations make field mapping visual and straightforward.

Object is Salesforce's term for database tables. Contacts, Leads, Campaigns, Accounts, and Opportunities are all standard objects. Marketing integrations typically work with Contact and Lead objects, plus Campaign objects for tracking email performance.

Record refers to a single entry within an object. One contact record represents one person. One campaign record represents one marketing initiative. Understanding this distinction helps when reading integration documentation about "syncing contact records" versus "syncing to the Contact object".

Custom field represents marketer-defined data fields beyond Salesforce's standard fields. You might create custom fields for industry vertical, product interest, or event attendance history. Integration field mapping determines whether these custom fields sync to your email platform.

Delta sync versus full sync describes updating only changed records versus re-syncing everything. After initial setup, most integrations use delta sync to avoid redundant processing. Occasionally you might trigger a full sync to ensure complete data accuracy after making major configuration changes.

Salesforce Installation and Deployment Terms

AppExchange is Salesforce's official marketplace for third-party applications and integrations. All legitimate Salesforce integrations are distributed through AppExchange, which provides security reviews and customer ratings.

Managed package describes a self-contained application installed directly into Salesforce orgs. These packages don't impact standard Salesforce objects. They receive automatic updates from the vendor and can be uninstalled cleanly without leaving orphaned data.

Unmanaged package contains custom code that becomes part of your Salesforce org and can be modified. Unlike managed packages, unmanaged packages give you full access to customise the code, but you lose automatic vendor updates. Marketing teams rarely encounter unmanaged packages unless working with custom-built integrations.

Namespace is a unique identifier that prevents naming conflicts between packages. When you install multiple integrations, namespaces ensure each package's objects and fields remain distinct. You'll see namespaces as prefixes in field names (like 'mc4sf__Email_Activity__c' where 'mc4sf' is the namespace).

Production org versus Sandbox distinguishes your live Salesforce environment from testing environments. Production contains real customer data and active campaigns. Sandbox environments are recommended for testing integrations, and Salesforce offers sandbox refresh functionality that copies installed applications from production. Always test major integration changes in a sandbox before deploying to production.

Sandbox refresh means copying production configuration and data into a sandbox for testing. This gives you a safe environment to experiment with new integration settings or test how campaigns will behave before going live.

Custom domain is an organisation-specific Salesforce URL required for Lightning Components. Salesforce requires a custom domain to be set up in order to use Lightning Components, which are used in modern AppExchange applications. If you see errors about missing domains during integration setup, this is why.

User Access and Permission Terms

Permission set is a collection of settings that determines what users can do with an integration. After installing an email marketing integration, your administrator assigns permission sets to control who can configure sync settings, view campaign data, or push contacts to external platforms.

Profile refers to broader Salesforce roles that determine platform access. Profiles control object-level access, while permission sets add specific capabilities. Most integrations use permission sets layered on top of existing profiles rather than creating entirely new profiles.

System administrator is a Salesforce user role with full platform access, typically responsible for installing integrations. System administrators can see all data, modify all settings, and assign permissions to other users. Most integration documentation assumes a system administrator is performing the setup.

Connected app describes an authorised external application that can access Salesforce data via API. When you connect an email platform or event tool to Salesforce, you're creating a connected app that has permission to read and write specific data types.

Integration user is a dedicated Salesforce user account created specifically to run integration processes. Some organisations create integration users to track which changes came from automated syncs versus manual user updates. This isn't required for most marketing integrations but can help with auditing.

Performance and Technical Limitation Terms

Governor limits are Salesforce's resource usage restrictions that prevent any single process from monopolising shared infrastructure. Because Salesforce is a multi-tenant platform, governor limits ensure fair resource distribution. These limits affect API calls, data storage, and processing time.

API call limit is the maximum number of API requests allowed per 24-hour period, varying by Salesforce edition. Professional Edition orgs get 1,000 API calls per user per day, while Enterprise gets 5,000. Marketing integrations consume API calls when syncing data, so understanding your limits matters when running large campaigns.

Batch processing handles large data volumes by processing records in groups rather than individually. When syncing 50,000 contacts to an email platform, batch processing divides that into smaller chunks to avoid hitting governor limits. Modern integrations handle batch processing automatically.

Callout occurs when Salesforce makes an API request to an external system. All syncing operations to and from external platforms use outbound callouts from Salesforce, which don't count against standard API limits. This architectural detail means marketing integrations typically don't consume your precious API call allowance.

Apex is Salesforce's proprietary programming language used in custom integrations. Marketing teams don't need to learn Apex, but you might encounter it in integration documentation when describing how data transformations or custom workflows function behind the scenes.

Workflow versus Process Builder versus Flow represent three generations of Salesforce automation tools. Flows are the modern standard for building automation. Process Builder is being phased out. Workflows are legacy technology still supported but deprecated. When evaluating integrations, check whether they support Flow invocable actions for modern automation capabilities.

Marketing-Specific Integration Terms

Campaign sync connects Salesforce Campaigns with email marketing campaigns to track engagement. When you send an email campaign, campaign sync creates or updates the corresponding Salesforce Campaign with metrics like sends, opens, and clicks.

Campaign member is a Salesforce object that links contacts or leads to specific campaigns. When someone attends your webinar or receives your newsletter, they become a campaign member with a status indicating their level of engagement (registered, attended, responded).

Engagement data encompasses metrics like opens, clicks, and unsubscribes synced from marketing platforms. Storing engagement data in Salesforce lets sales teams see which prospects opened pricing emails or clicked product links, enabling better conversation timing.

List segmentation filters contacts based on Salesforce data for targeted campaigns. You might segment contacts by industry, purchase history, or engagement score to send personalised email content. Strong integrations let you build segments in Salesforce and sync them directly to your email platform as lists.

Lead source tracking attributes new leads to specific marketing activities. When someone downloads a whitepaper or registers for a webinar, lead source tracking records which campaign generated that lead. This visibility helps calculate marketing ROI and optimise campaign budgets.

Suppression list contains contacts excluded from marketing communications, synced from unsubscribes or opt-outs. Compliance regulations require honouring unsubscribe requests across all channels. Integrations that sync suppression lists automatically prevent sending to opted-out contacts even if someone manually adds them to a campaign.

Common Integration Patterns and Workflows

Real-time sync versus scheduled sync distinguishes immediate data updates from periodic batch updates. Real-time sync using webhooks updates Salesforce the moment someone unsubscribes. Scheduled sync runs hourly or daily to batch process changes. Most marketing integrations use scheduled sync for contact updates and real-time sync for critical events like unsubscribes.

Event-driven integration uses webhooks to trigger actions when specific events occur. When a high-value prospect opens your pricing email three times in one day, an event-driven integration can notify sales immediately rather than waiting for the next scheduled sync.

Middleware refers to third-party platforms that connect multiple systems (iPaaS solutions). Tools like Zapier or Workato sit between Salesforce and other applications, routing data and transforming formats. Middleware adds flexibility but introduces another vendor dependency and potential failure point.

Native integration versus third-party connector distinguishes whether the platform vendor built the integration or an integration specialist did. Native integrations typically receive better support and earlier access to new features because the vendor controls both ends of the connection.

Deprecation happens when a vendor discontinues support for a legacy integration. Dropbox transitioned away from their legacy Salesforce integration, prompting organisations to migrate to modern alternatives. Understanding deprecation timelines helps avoid sudden disruption.

Migration is the process of moving from one integration solution to another. Whether you're replacing a deprecated integration or upgrading to a more capable solution, migration involves mapping configurations, transferring historical data, and testing workflows before switching over completely.

How to Use This Glossary When Evaluating Integrations

Armed with this terminology, you can ask vendors better questions. Does the integration support bidirectional sync? Is it delivered as a managed package? What are the API call requirements? Does it use OAuth2 for authentication? Can you map custom fields?

Watch for red flags in integration documentation. Vague authentication methods suggest security shortcuts. No mention of governor limits indicates the vendor doesn't understand Salesforce architecture. Unclear sync frequency means you might be stuck with daily updates when you need real-time visibility.

Understanding these terms helps you avoid migration pain later. An integration that seemed simple during the demo might reveal limitations once you understand that it only supports unidirectional sync or doesn't handle custom fields. Better to ask informed questions upfront than discover constraints after you've invested months in setup.

Good vendors explain features using this terminology while also showing practical examples. If documentation reads like it was written by developers for developers, expect a steeper learning curve and more reliance on technical support.

Built for Marketers Who Need Integrations That Just Work

Beaufort 12 builds official Salesforce integrations for Mailchimp, Campaign Monitor, Emma, Eventbrite, and Dropbox using the terminology and best practices defined in this glossary. Every integration is a managed package installed from AppExchange, with OAuth2 authentication and field mapping you can configure yourself. Explore solutions built with marketing teams in mind at beaufort12.com.