Passing campaign membership and statuses into Salesforce

Pass campaign membership as a relationship between a person and a specific CRM campaign, with a status for that campaign. In Salesforce, that relationship is a campaign member: a lead, contact, account or person account added to a campaign. A general contact field holding a campaign name does not establish membership by itself, nor distinguish several campaigns.

Define the membership change

Choose which marketing event adds a member and which changes an existing member's status. Registration, attendance and withdrawal may mean different things, so agree the event and status mapping for each campaign.

Resolve the person to the intended Salesforce lead or contact and identify the destination campaign before writing membership. Members can also be added by hand from a record's detail page, a list view, report results or the Data Import Wizard, so check for existing members first.

Each Salesforce campaign has its own Campaign Member Statuses related list. To add a status, click New in that list on the campaign record's Related tab, enter a name and save it.

Use one set of statuses for each campaign type so reporting stays meaningful. Salesforce's examples are Sent, Responded, Purchased and Did Not Purchase for email campaigns, and Invited, Accepted, Declined and Attended for product demos. Tick the Responded box next to each status that should count as a response, rather than assuming a label such as “Registered” does.

Connect HubSpot and map the person, campaign and status

Before the first write, connect HubSpot and Salesforce. The person connecting must be a Salesforce system administrator with API Enabled, View Setup and Configuration, and Modify All on the objects to sync, such as campaigns, contacts and leads.

Then build a contact-based HubSpot workflow whose enrolment trigger is the marketing event, such as a webinar registration form, and add the Set Salesforce campaign action. It sets a Salesforce campaign for the enrolled contact and is only available in contact-based workflows.

For a product demo campaign, for example, a registration could set the member to Accepted and confirmed attendance to Attended, with only Attended counted as a response. A cancellation would set Declined rather than removing the member, so the history stays visible.

Keep the person and campaign references in the integration record, and limit personal details in routine alerts. Hold an uncertain match for review. Creating another person merely to make a membership write succeed can leave the CRM with duplicate people.

Steps to Pass Campaign Membership into Salesforce

Verify the result in Salesforce

Check a controlled case for a person new to the campaign, one already a member, and one whose HubSpot record cannot be matched. Open the campaign's Campaign Members related list and confirm the campaign, member status and response setting. Repeat the same event: the expected result is one unchanged membership, not a second member or a changed status.

For a wider check, run Salesforce's built-in Campaigns with Campaign Members report, found under the Reports tab with New Report. It shows how many members have responded to each campaign, so a status mapped to the wrong response setting shows up quickly.

Confirm the resulting Salesforce state rather than treating a completed workflow action as proof of the intended membership. If a contact did not sync or the member status differs from the agreed mapping, correct the status list or the workflow before the campaign goes live.