CRM campaign sync

Mobly can push the leads captured at an event into a campaign-style object in your CRM — a Salesforce Campaign, a HubSpot Marketing Event or Segment, or a Zoho Campaign. That's how event attribution shows up on the CRM side: a rep opens the campaign in Salesforce and sees every lead your team captured at the booth.

Mobly Labels ≠ CRM campaigns. These are two different features that are easy to confuse.

Mobly Labels are a Mobly-side grouping feature — you define a Label by qualifier value, events, activations, and a scan-count threshold, and it groups leads inside Mobly. See How to use Mobly Labels.

CRM campaigns are objects in your CRM that Mobly syncs event leads into. That's what this article covers.

Where campaign sync is configured

Per event, from the Sync Event bar on the event detail page — the bar above the tabs, not a tab itself. Each Mobly event connects to its own campaign.

Activations have a parallel Sync Activation bar, so a dinner or breakout can map to its own campaign separately from the parent event.

This is a change from how campaign sync worked on the legacy integration, where mappings lived in a per-integration tab. On the new integration platform, the mapping lives with the event it belongs to.

What each CRM receives

CRM

Object

Carries a per-member status?

Salesforce

Campaign

Yes — Campaign Member Status

HubSpot

Marketing Event

Yes — participation status

HubSpot

Segment

No — list membership only

Zoho

Campaign

Yes

Marketo

Program

Yes — Program Status (see the Marketing Automation write-up)

How a lead ends up in the campaign

When a lead is captured at an event that's connected to a campaign:

Mobly waits for enrichment to complete
Mobly pushes the lead to your CRM (creating or updating per the matching logic for your CRM)
Mobly adds the lead to the connected campaign
Mobly sets the member status based on your mapping

A single lead can land in multiple campaigns if it was captured at multiple Mobly events that each connect to a different one.

Member status mapping

When you connect a campaign, the last step of the wizard is Map Status — deciding what status a captured lead gets on the CRM side.

With Registration mappings configured, you get a row per Mobly registration state:

Mobly state

When a lead reaches it

Registered

Lead signed up before the event

Checked-in

Lead checked in at the door

Live Capture

Lead scanned on the floor

Each row pre-fills from your org-wide registration mappings, and you can override any of them for just this event. See the Salesforce or HubSpot setup guide for how the org-wide defaults are set.

Without Registration mappings, it's a single status that every lead captured at the event receives.

Creating the campaign from Mobly

You don't need the campaign to exist first. The wizard's Create new option builds it in your CRM and maps it in one step — name, dates (pre-filled from the Mobly event), and description at minimum.

Salesforce also exposes a Parent campaign picker (for nesting under a campaign hierarchy) and the standard Planning fields: Num Sent in Campaign, Expected Response (%), Budgeted Cost in Campaign, Actual Cost, and Expected Revenue in Campaign.

Best practices

One campaign per event, activations underneath. Connect the parent event to your main campaign, and let activations map to their own — that gives you booth-vs-dinner attribution without fragmenting the event's rollup.
Sync the parent event before its activations. Mobly warns you if you don't, because event-level attribution is missing until the parent is connected.
Watch archived campaigns. An archived campaign in your CRM won't accept new members, and those leads land in Reconciliation. If you archive on the CRM side, disconnect the Mobly mapping too.
Use Registration mappings if you run registration. Setting the three states once at the org level means every event picks up sensible defaults and you only override the exceptions.