How HubSpot and Salesforce Campaigns Work Together

Campaigns are one of the easiest places to get confused when you're using HubSpot and Salesforce together. Both platforms use the word "campaign," but they use it to track different parts of the go-to-market process. HubSpot campaigns organize marketing assets and their performance, while Salesforce campaigns track people, their responses, and the pipeline or revenue connected to those responses.

Once you separate those jobs, the setup becomes much easier to design. You can let each system answer the questions it's built to answer, then connect the two through clear workflow logic.

‍

How do HubSpot campaigns and Salesforce campaigns differ?

A HubSpot campaign is built around marketing assets. Think of it as the container for the emails, landing pages, forms, ads, social posts, CTAs, and tracking URLs that belong to a specific marketing initiative. HubSpot then reports on how those assets performed through metrics such as sessions, new contacts, influenced contacts, clicks, submissions, and attribution touchpoints.

That makes HubSpot useful when Marketing wants to understand what generated interest. If you're running a webinar campaign, for example, you can group the promotional email, registration page, form, paid ads, and follow-up content so you can look at the initiative as a whole instead of checking each asset separately.

Salesforce campaigns are built around people. Leads and Contacts become Campaign Members, and the Campaign Member Status shows what happened with each person. Depending on the campaign, statuses might represent actions such as Sent, Registered, Responded, or Attended. Salesforce can then connect those people to Opportunities and revenue through its campaign reporting and influence model.

Salesforce also supports campaign hierarchies, which are useful when you want detailed campaigns to roll up into a broader initiative. A "2026 Roadshow" parent campaign, for example, could have a separate child campaign for each city. Sales and RevOps can report on the individual event while still looking at the roadshow as one larger program.

This difference between assets and people should drive the rest of the architecture. HubSpot helps Marketing understand how the content and channels performed. Salesforce helps the revenue team understand who engaged and what happened after that engagement.

Why don't HubSpot campaigns and Salesforce campaigns sync?

The two campaign objects don't sync because they represent different things. HubSpot campaigns group marketing assets. Salesforce campaigns group Campaign Members and their responses. A one-to-one sync between the objects would have to translate two different data models into each other.

With the native integration, HubSpot campaigns don't become Salesforce campaigns, and Salesforce Campaign Members don't become members of a HubSpot campaign. HubSpot also doesn't have an equivalent Campaign Member object where Salesforce member statuses could live.

The native connection you can use is the Salesforce Campaign ID written to the HubSpot contact when that Salesforce lead or contact is associated with a Salesforce campaign. That gives you something to reference in HubSpot for segmentation and automation, but the two campaign objects remain separate.

Most of the practical connection therefore happens through automation. Understanding your HubSpot-Salesforce sync triggers matters here because a form submission, property update, or other engagement can become the event that adds someone to the right Salesforce campaign.

Trying to make both campaign objects contain the same data usually adds work without improving the reporting. Decide which system owns each part of the campaign, then move the information that actually needs to cross the boundary.

When should you use HubSpot campaigns, Salesforce campaigns, or both?

Use HubSpot when you're primarily measuring marketing execution and engagement. If Marketing needs to know whether a landing page converted, which email drove clicks, how many new contacts came from the initiative, or which assets influenced existing contacts, HubSpot is the natural place to manage that campaign.

Use Salesforce when the reporting depends on individual people and what happened after they engaged. Events are a good example. Salesforce can tell you which Leads and Contacts were invited, who registered, who attended, which attendees became Opportunities, and how much pipeline or revenue became associated with the campaign.

For campaigns that start in Marketing and later involve Sales, you'll usually use both. HubSpot carries the marketing side of the story, and Salesforce carries the person and revenue side. That handoff works well when the campaign structure has been planned before launch.

Most campaign problems we see come from the structure around that handoff. Assets get created in HubSpot but never associated with the campaign. The Salesforce campaign exists, but nobody defines useful member statuses. A workflow sends Contacts into the wrong campaign, or reps don't update statuses after an event. Naming gets inconsistent and teams end up with duplicate records across HubSpot and Salesforce. Reusing the same form across unrelated initiatives can make attribution harder to interpret as well.

Those issues are easier to prevent during campaign design than to reconstruct after the campaign has already generated pipeline.

How should you set up campaigns across HubSpot and Salesforce?

Start by defining ownership.

HubSpot should own the marketing assets and the engagement data tied to those assets. Marketing builds the emails and landing pages there, associates the appropriate forms and CTAs, and uses HubSpot campaign reporting to understand traffic, conversions, new contacts, and influenced contacts.

Salesforce should own the Campaign Members, member statuses, Opportunities, and revenue reporting. Once an engagement becomes something Sales needs to act on or something you want represented in revenue reporting, the Salesforce campaign becomes part of the process.

Your workflows connect those two layers. They take a HubSpot engagement event and translate it into the appropriate Salesforce action. A form submission might add the Contact to the matching Salesforce campaign. A later action might update the Salesforce Campaign Member Status from HubSpot. The workflow may also stamp source fields or update lifecycle information when the process calls for it.

Any fields involved in that handoff should follow the ownership rules in your HubSpot-Salesforce field mapping. If both systems can write to the same campaign-related property without a clear rule, debugging the workflow later gets much harder.

Before a campaign goes live, check the setup once from end to end:

1. The HubSpot campaign exists and the correct marketing assets are associated with it.
2. The matching Salesforce campaign exists and its Campaign Member Statuses are finalized.
3. Workflow enrollment criteria match the actual engagement that should create or update campaign membership.
4. Re-enrollment behavior is intentional and won't create unexpected campaign updates.
5. Suppression criteria exclude the people who shouldn't enter the workflow.
6. Campaign naming follows the same convention in both systems.

Once those basics are in place, there are a few ways to structure the automation.

One workflow per campaign

This is usually the easiest pattern to understand. A webinar, launch, event, or other defined initiative gets its own workflow, and that workflow manages the corresponding Salesforce campaign actions.

It works well when campaigns have a clear start and finish because someone can open the workflow and immediately see the logic for that campaign. The tradeoff is maintenance. If you run a large number of campaigns, you can end up managing a large number of similar workflows.

One workflow per lead source

This works when several campaigns use the same type of acquisition path and follow similar Salesforce logic. Instead of creating a new workflow for every campaign, you organize automation around a source or recurring campaign type.

The pattern can reduce duplicated workflow logic, but your criteria need to be specific enough to send each Contact to the correct Salesforce campaign. If different initiatives start sharing the same forms or source values, the workflow can become harder to read.

One global workflow with branching

Higher-volume teams sometimes use a central workflow and branch based on campaign, form, source, or another field. This gives RevOps one place to govern the campaign handoff.

The advantage is central control. The risk is that the workflow can become difficult to maintain if every new campaign adds another set of branches and exceptions. Use this pattern when your naming and campaign taxonomy are mature enough to support it.

Enterprise custom objects

For Enterprise setups that need deeper cross-platform reporting, another option is to represent Salesforce campaign information inside HubSpot through custom objects. Salesforce campaigns and Campaign Members can be mirrored as custom objects, with the required fields and associations mapped into HubSpot.

This gives you more flexibility for reporting inside HubSpot, but it also creates a larger data model to maintain. Field mappings and duplicate handling need to be planned carefully. We'd usually consider this after the standard workflow patterns, when there's a specific reporting requirement that the simpler setup can't meet.

A clean example of proper HubSpot-Salesforce mapping:

What can you associate with a HubSpot campaign?

HubSpot campaigns work best when the assets associated with them genuinely belong to the same initiative. Emails, forms, landing pages, CTAs, ads, social posts, marketing events, and tracking URLs can all contribute to campaign reporting when they're associated correctly.

There's an important constraint to account for during planning: a HubSpot marketing asset can belong to only one campaign at a time. If you need the same asset represented in separate campaigns, you'll need to clone it and associate the copies with the appropriate campaigns.

That becomes relevant with evergreen forms and assets that teams like to reuse. A single generic demo form might appear on several landing pages, but using that same form across multiple campaign concepts can limit how cleanly you can attribute its performance at the campaign level. When campaign-level reporting matters, dedicated assets usually give you clearer reporting.

Lists and workflows are useful when you need logic that spans campaigns because they don't have to play the same role as a campaign-owned marketing asset. HubSpot can also associate certain sales activities with campaigns, which can add context around campaign performance.

The campaign structure should be decided before Marketing starts building. If you wait until everything is live to work out which campaign owns each asset, you'll spend time rebuilding associations or cloning assets after the fact.

Which campaign KPIs belong in HubSpot vs Salesforce?

‍

You'll get cleaner cross-platform reporting if you decide which system owns each top-level number before the campaign starts. The three most useful campaign outcomes to separate are lead generation, pipeline, and revenue.

• Lead generation: HubSpot is where you'll usually look at new Contacts, influenced Contacts, asset engagement, and contact creation attribution. Salesforce can show the Leads or Contacts Sales needs to act on once they enter the Salesforce process. HubSpot gives you the better view of what generated the engagement.
• Pipeline: Salesforce should own the pipeline number through Opportunities associated with the sales process and campaign influence. HubSpot can provide supporting marketing context, particularly for teams with higher-tier attribution features, but Salesforce should remain the reference point for the Opportunity value. If your pipeline model itself needs work, start with how you define Opportunities in Salesforce and your broader sales pipeline generation process.
• Revenue: Salesforce owns closed-won revenue and the Salesforce campaign influence reporting tied to those Opportunities. HubSpot can add attribution context about the marketing interactions that contributed along the way. Salesforce gives you the revenue outcome, while HubSpot helps explain which marketing activity contributed to it.

Problems start when teams expect the two platforms to produce an identical campaign number from different data structures. Define the reporting question first, then use the platform that actually owns the data required to answer it.

What should you decide before creating a campaign?

Campaign reporting can only use the structure you put in place before and during the campaign. A few decisions made up front can save a lot of cleanup later.

• How will people enter your CRM from this campaign?
• Which HubSpot assets belong specifically to this initiative?
• When should engagement create or update a Salesforce Campaign Member?
• Which Campaign Member Statuses will represent meaningful actions?
• Where will pipeline and campaign ROI be reported?
• How will Opportunities be created and connected to the campaign process?
• Does the campaign need its own forms or CTAs because of HubSpot's one-campaign-per-asset rule?
• Who will use the campaign dashboards, and what decisions are they expected to make from them?
• Does qualification need to happen before Sales follows up, and how does that connect to your RevOps lead scoring model?

You don't need a complicated campaign architecture for every initiative. You do need agreement on how engagement becomes campaign membership, how membership becomes pipeline, and where each result will be reported.

That's what keeps Marketing and Sales from building separate versions of the same campaign after launch.

What should you do next?

Start with one real campaign and trace it through both systems. Look at the HubSpot assets, the engagement that should matter, the workflow that connects that behavior to Salesforce, the Campaign Member Statuses, and the Opportunities that follow.

If the process requires manual corrections every time a campaign launches, the problem is usually in the operating model around the campaigns. Standardize the campaign naming, asset rules, workflow pattern, and Salesforce statuses before scaling the number of campaigns.

From there, you can add more mature lead qualification, attribution reporting, and shared dashboards without rebuilding the campaign model every quarter.

The distinction to keep is simple: HubSpot campaigns tell you what content worked. Salesforce campaigns tell you who responded and how much revenue they generated.

If you want help designing or fixing the campaign architecture between the two platforms, book a call with RevBlack.

‍