> For the complete documentation index, see [llms.txt](https://help.getmobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getmobly.com/help-center/integrations/crm/campaign-mapping.md). # Mapping campaign fields Mobly's per-event campaign sync lets you push leads into specific CRM campaigns based on which event they were captured at. Configure it on the **Campaigns** tab inside any connected CRM integration (**Integrations → \[your CRM] → Campaigns**). > Mobly Campaigns ≠ CRM Campaigns. **Mobly Campaigns** are a Mobly-side feature for grouping/automation logic; **CRM Campaigns** are HubSpot/Salesforce campaign objects you can sync your event leads into. This article is about syncing event leads into CRM Campaign objects. For Mobly Campaigns, see [Mobly Campaigns](/help-center/campaigns/campaigns.md). For Marketo Programs (the Marketing Automation equivalent), see [Mapping program fields](/help-center/integrations/marketing-automation/campaign-mapping.md). ## What's on the Campaigns tab A list of every CRM campaign Mobly is currently configured to sync to, with: * **Name** — the CRM campaign's display name * **CRM ID** — the CRM-side identifier * **Is Archived** — whether the campaign is archived in your CRM (archived campaigns won't accept new members) * **Qualifier Option** — which Mobly qualifier (if any) drives status changes for members of this campaign * **Lead Scan Threshold** — minimum scans required for a lead to be added (0 = every captured lead) * **Leads** — current count of leads attached * **Events** — the Mobly events that feed into this campaign * **Activator** — which person or process triggers the sync Plus a **+ New Campaign** button to add a new mapping and an **Export CSV** option for offline review. ## How campaigns sync When a lead is captured at an event mapped to a CRM campaign: 1. Mobly waits for [enrichment](/help-center/integrations/crm/how-data-flows.md) to complete 2. Mobly pushes the lead to the CRM (creating or updating per the matching logic for your CRM) 3. Mobly adds the lead as a member of the linked campaign(s) in your CRM 4. If your **Qualifier Option** mapping is configured, Mobly sets the campaign member's status based on the qualifier value the rep applied A single lead can be added to multiple CRM campaigns if it was captured at multiple Mobly events that each map to a different campaign. ## Campaign member status from qualifiers If a CRM campaign has member statuses (e.g., Salesforce Campaign Member Status: "Sent," "Responded," "Attended"), you can drive those statuses from a Mobly qualifier. Example: a qualifier called **Follow up** with values **Yes** / **No** / **Already a customer**. Map: * Yes → "Responded" * No → "Sent" * Already a customer → "Attended" Now when a rep picks a qualifier value on a lead, the corresponding CRM Campaign Member Status is set automatically. ## Lead Scan Threshold This sets a minimum number of badge scans before a lead syncs to the campaign. Most teams keep this at **0** (every captured lead syncs). Use a higher threshold when: * A booth attendant scans by accident (raise to 1+ to filter out single-scan accidents) * You want to flag highly-engaged leads who hit your booth multiple times ## Adding a new campaign sync 1. Go to **Integrations → \[your CRM] → Campaigns** 2. Click **+ New Campaign** 3. Pick the CRM campaign from the dropdown (Mobly pulls the list from your CRM live — make sure the campaign exists in your CRM first) 4. Pick which Mobly events feed into it (you can pick multiple) 5. Optionally set **Qualifier Option** (the qualifier that drives member status) 6. Optionally set **Lead Scan Threshold** 7. Save The mapping takes effect for new captures going forward. Leads already captured at the linked events don't retroactively sync to the campaign — for those, retry from [Reconciliation](/help-center/integrations/crm/reconciliation.md). ## Editing or removing a campaign sync The three-dot menu at the right of each row has: * **Edit** — change linked events, qualifier option, threshold, etc. * **Remove** — stops new syncs to this campaign. Existing campaign members in your CRM are not removed. ## Best practices * **One CRM campaign per event series, not per event.** Most teams find it cleaner to have a "SaaStr 2026" campaign than 17 sub-campaigns for each booth/dinner/activation. Use Mobly's [Activations](/help-center/the-hub/managing-events/tracking-activations.md) for sub-event tracking instead. * **Use Qualifier Option for high-signal status.** "Did they convert?" "Did they attend the demo?" These are the highest-value status drivers. Skip qualifiers where the value is just metadata. * **Match CRM campaign archived state.** If you archive a CRM campaign in HubSpot/Salesforce, archive or remove the Mobly mapping too — Mobly will fail to add new members to an archived campaign and those leads will land in [Reconciliation](/help-center/integrations/crm/reconciliation.md). * **Review the Activator column quarterly.** Old campaigns whose Activator is no longer with the team should be reassigned or archived. ## Vendor-specific notes Campaign-as-an-object exists in different forms across CRMs. Setup differs slightly per CRM — each per-vendor folder has the specific connect article: * [Connecting HubSpot Marketing Events to Mobly Events](/help-center/integrations/crm/hubspot/connecting-marketing-events.md) * [Connecting Salesforce Campaigns to Mobly Events](/help-center/integrations/crm/salesforce/connecting-campaigns.md) For Marketo Programs (Marketing Automation), see [Connecting Marketo Programs to Mobly Events](/help-center/integrations/marketing-automation/marketo/connecting-programs.md). ## Related articles * [Field mapping](/help-center/integrations/crm/field-mapping.md) * [Qualifiers](/help-center/integrations/crm/qualifiers.md) * [How data flows from Mobly to your CRM](/help-center/integrations/crm/how-data-flows.md) * [Reconciliation](/help-center/integrations/crm/reconciliation.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.getmobly.com/help-center/integrations/crm/campaign-mapping.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.