Adobe Campaign Salesforce Integration: Connector, Setup and Pitfalls (2026)

What an Adobe Campaign Salesforce integration should do

The usual setup: sales and service teams keep customers in Salesforce, and the marketing team sends email, SMS and push at scale from Adobe Campaign. Without a link, marketing segments on a stale export, and reps call people who unsubscribed last week.

A useful integration does four jobs:

• Fresh audiences. Contacts and leads, with the account and owner fields marketing segments on, reach Campaign on a schedule.
• One consent record. An unsubscribe in either system reaches the other before the next send or the next call.
• Responses for sales. Who opened, clicked or replied lands in Salesforce, so reps see engagement and campaign reports work.
• Clean deletes. Records deleted or merged in Salesforce stop receiving messages from Campaign.

It is not a copy of the whole CRM. Campaign tables built for millions of profiles and Salesforce API allocations both punish “sync everything”. Start with the fields a segment or a report actually uses.

Which Adobe Campaign version you have decides the route

“Adobe Campaign” covers three products with different integration options. According to Adobe’s Experience League documentation, as of October 2026:

Adobe’s compatibility matrices for both v8 and Classic v7 list the Salesforce connector against Salesforce API version 49. That is the API version you pick in the external account.

How the Campaign CRM connector works

The connector ships in a dedicated CRM connectors package, and Adobe notes it only works over a secure (https) URL. There are three parts.

1. The Salesforce external account

In the Campaign Client Console, under Administration, Platform, External accounts, you create an account of type Salesforce.com with a Salesforce login, password, security token and API version. Adobe’s guide says the client identifier can be left empty, and that you log off and back on to finish the setup.

2. The configuration wizard

The Salesforce CRM configuration wizard lets you pick the Salesforce tables to synchronize. Campaign then generates a data schema for each, which you can check under Administration, Configuration, Data schemas. A second assistant synchronizes enumerations: it copies Salesforce picklist values into Campaign enumerations, optionally replacing the existing values.

3. The CRM Connector workflow activity

Data moves only when a workflow runs. The activity has four operations:

• Import from the CRM. Pick the remote object and fields. The Salesforce record ID is added automatically and links the records. With Automatic index on, each run imports only records changed since the last run, using LastModifiedDate or SystemModstamp.
• Export to the CRM. Copies a Campaign table to Salesforce. If you set the Salesforce primary key, records are updated; without it, they are inserted. An Export in batches option speeds up large exports.
• Import objects deleted in the CRM. You give a date range. Adobe warns that for Salesforce, records deleted more than 30 days ago can’t be recovered, so the job must run well within that window.
• Delete objects in the CRM. Deletes Salesforce records by primary key. Use it rarely, if ever.

The Behavior tab can keep rejects in a file and add a reject transition. For Salesforce, each reject carries an error symbol and message, so you can log failures and retry them from the same workflow.

Your options compared

The connector is the default for v8 and Classic. The other routes fit specific situations:

The Experience Platform route. Adobe documents a Salesforce source for Experience Platform that ingests contacts, leads, accounts, opportunities, opportunity contact roles, campaigns, campaign members and account contact relations. Adobe’s documentation says Basic authentication for this source is deprecated and OAuth 2 Client Credential authentication is required. It also says only soft-deleted Salesforce records are detected, not hard deletes.

Experience Platform then sends audiences to Campaign v8 through the Adobe Campaign Managed Cloud Services destination, and a matching source returns Campaign delivery and tracking logs to Platform. It is a strong route if you already run AEP, and an expensive one to buy just for this.

Marketo Engage. If you are still picking a platform and the job is B2B lead scoring and handoff to sales, Marketo’s native sync is a closer fit. Our Marketo Salesforce integration guide covers it.

For smaller teams, the Mailchimp Salesforce integration guide shows the lighter end of the market.

Which option fits you?

Your Campaign version and whether you already run Experience Platform narrow this down fast. Five questions, including what must flow back to Salesforce, give you a route.

How the data flows

Split ownership cleanly: Salesforce is the system of record for people and accounts. Campaign is the system of record for deliveries and tracking. Consent is the one field both sides can change, so it needs an explicit rule.

Object and field mapping: what goes where

This is the minimum set for a working sync. Every extra field should be one that a named segment or report actually uses.

Two habits keep the mirror clean. First, key everything on the Salesforce record ID, not on email: contacts and leads share addresses, and a person can exist as both.

Second, summarize engagement before export. Writing every open and click to Salesforce as its own record burns API calls and storage; a status per campaign member plus a few “last engaged” fields is what reps actually read.

How to set it up, step by step

With the CRM connector, the data contract comes before the external account, and deletions get their own workflow before the first export. Screens differ between Campaign builds, so keep Adobe’s Experience League guides open for yours.

1. Confirm your version and packageCampaign v8 or Classic v7, with the CRM connectors package installed. On Campaign Standard, stop here and decide between a custom flow and the move to v8.
2. Write the data contractWhich Salesforce objects and fields marketing segments on, which consent field wins in which case, and what goes back to Salesforce. One page, signed off by marketing ops and the Salesforce admin.
3. Create a dedicated Salesforce integration userGive it API access and read access only to the objects and fields in the contract. Add edit rights on the few fields Campaign writes. Supported editions come with a limited number of Salesforce Integration user licenses for this purpose. Generate its security token.
4. Connect a sandbox firstIn the Campaign Client Console, add a Salesforce.com external account pointing to a Salesforce sandbox. Enter the login, password, security token and the API version from Adobe’s compatibility matrix. Enable it, then log off and on.
5. Run the configuration wizardSelect only the tables in your contract. Check the generated schemas, then run the enumeration assistant for the picklists you segment on.
6. Build the import workflowScheduler, CRM Connector (import), then dedup and update of Campaign profiles. Create the text option for Automatic index by hand under Administration, Platform, Options, and filter out records you must not message.
7. Build the deletions workflowA daily CRM Connector import of deleted objects for the last few days, which flags or removes matching profiles. Daily runs keep you far inside the 30-day window.
8. Build the export workflowCollect opt-outs and summarized responses, then CRM Connector (export) with the Salesforce ID as primary key so records update instead of duplicating. Turn on Export in batches and reject handling.
9. Test real scenariosTry a new lead, a converted lead, a merged contact and a deleted record. Add an unsubscribe in each system, a picklist value Campaign doesn’t know, and a bulk update of 50,000 records.
10. Switch to productionRepeat the external account against production, run the first full import outside business hours, then turn on the schedules and watch rejects for two weeks.

Built by Gilzor

Results we’ve shipped

70+products launched

98%delivered on time

85%clients come back

Aviation33%faster baggage weigh-inWeb and Mobile application for Airlines→Healthcare+30%lab test ordersMedical Lab Web and Native Mobile Applications→Retail · Startup700+stores aggregatedMobile application for Grocery shops→

Talk to the people who build it. Tell us about your project and get a free estimate of scope, timeline and cost.

See how we’d approach yours →

Pitfalls and how to fix them

When to go beyond the connector

The connector is a scheduled batch tool, and that is fine for most audience syncs. Custom work, or an iPaaS such as MuleSoft, Workato or Boomi, starts to pay off when:

• You run Campaign Standard and are not moving to v8 yet.
• A Salesforce event must trigger a message within minutes, for example a closed-won deal starting an onboarding series.
• Records need filtering, enrichment or approval in transit, under rules you can audit.
• Several Salesforce orgs feed one Campaign instance.

A typical custom build listens to Salesforce Change Data Capture or Platform Events, queues the changes and writes to Campaign through its SOAP APIs. A nightly reconciliation job acts as a safety net.

Adobe documents Campaign REST APIs as well, but only on demand for FDA environments and not for Enterprise (FFDA) deployments, so check your deployment with Adobe first. If MuleSoft is already your integration layer, see our Salesforce MuleSoft integration guide.

These build figures, drawn from our API integration cost guide, leave out Adobe and Salesforce licenses. For every other system you might connect to Salesforce, start with the Salesforce integration guide.

Go-live checklist

A wrong consent value here means a message to someone who opted out, so go through this list before the first production send. Check off what is done.

FAQ

Where Gilzor fits

With Adobe Campaign, most of the risk sits in the consent rule and the deletions workflow, not in the connector settings. Gilzor, whose software developers work from Poland and Cyprus, builds and maintains Salesforce integrations. With Campaign, we start by mapping the data flow and consent rules with your marketing and Salesforce teams.

We then build the Campaign connector workflows or a custom integration on the Salesforce and Adobe Campaign APIs, and support it after launch. See the Salesforce integration services page for how we scope that work.