> 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/campaigns/how-to-use-mobly-campaigns.md).

# How to use Mobly campaigns

## Overview

Mobly campaigns are designed to help you streamline your lead management process and enhance your CRM automation, saving you time and improving your follow-up strategies.

Assign Mobly campaigns to your leads on an event-by-event basis without doing repetitive CRM or MAP configuration for each event. You can even configure Mobly campaigns to be sensitive to specific qualifiers, allowing for personalized follow-ups based on industry, product, or lead score.

## Setup

In order to start using campaigns in Mobly, you'll first need to contact your CSM to get the feature enabled for your organization.

Once you're enabled, you can follow these steps:

1. Navigate to the "Campaigns" tab in the Hub. Click "New Campaign" in the top right corner.

   ![](//d33v4339jhl8k0.cloudfront.net/docs/assets/67f00b47b96c282fea91b6f6/images/6864360ab577ac399a510c43/file-bf3NAKSZgD.png)
2. Add a campaign name and the campaign ID from the CRM/MAP (e.g., Salesforce Campaign ID). Next, define the criteria for applying the campaign by including one or more of the following: the dates when the campaign mapping should be active, the qualifier values that should trigger the campaign, or the events that should activate the campaign.

   ![](//d33v4339jhl8k0.cloudfront.net/docs/assets/67f00b47b96c282fea91b6f6/images/686436a04b6745676163bf21/file-ByL0giTmy3.png)
3. Once you scan a lead that meets the criteria specified in the campaign configuration, you will see the campaign added to the "Activities" section of the lead. This can be found by clicking the "Info" icon in the mobile app or the "Activities" tab on a lead in the Hub. The lead will be sent to the CRM with the CRM ID you entered on the campaign.

![](//d33v4339jhl8k0.cloudfront.net/docs/assets/67f00b47b96c282fea91b6f6/images/686436d435edbc1e175da22c/file-66hQoOrYfn.png)

With the campaign ID on the lead object in the CRM, you can program any flows you'd like to trigger specific campaign actions.

***

## Event View

You can also view and edit your campaigns within your events. You can add new campaigns to this event, or edit existing campaigns.

![](//d33v4339jhl8k0.cloudfront.net/docs/assets/67f00b47b96c282fea91b6f6/images/69093420d45c6b72332505c5/file-gWYYrc0A3D.png)

It's helpful to know how many leads triggered the Mobly campaign and why they triggered it.

![](//d33v4339jhl8k0.cloudfront.net/docs/assets/67f00b47b96c282fea91b6f6/images/690934db6f84097ce8119f95/file-2qKC6IEraA.png)

For example this Mobly Campaign triggered on 483 leads because they had the "Hot" qualifier value applied. They only needed one scan to trigger the campaign sync.

## The campaign detail page

Click any campaign on the **Campaigns** list to open its detail page. Two tabs at the top.

### Info tab

The default landing tab. Shows the campaign's configuration:

* **Identity** — name, description, owner
* **Trigger** — what enrolls audiences (event attended, list joined, qualifier value applied, etc.)
* **Action** — what the campaign does (send email, sync to CRM, apply qualifier)
* **Audience size** — current count of leads matching the trigger
* **Status & schedule** — Active / Paused / Draft, with planned send windows if applicable

Use this tab to spot-check a campaign's setup before activating it.

### Leads tab

Every lead currently in the campaign's audience, with each lead's campaign-specific status (sent / opened / clicked / bounced / unsubscribed, where applicable). Click any lead to open the Lead Details drawer for the full profile.

Filter by campaign status and engagement to spot-check the audience before activating, or to see who actually opened the email after the fact.

## Editing a campaign

Click the pencil icon in the campaign detail page header. The edit drawer covers:

* Name, description
* Trigger configuration (which event, list, or qualifier value triggers enrollment)
* Audience filters (narrow to a subset of trigger matches)
* Action configuration (email template, CRM sync, etc.)
* Schedule

Save persists the campaign; reopening pre-fills the current state.

## Archive vs delete

Campaigns have a soft-archive flow:

* **Archive** — hides the campaign from default views and stops it from enrolling new leads. History (sends, audience snapshots) is preserved. Use this for seasonal campaigns you'll bring back annually.
* **Reactivate** — flips an archived campaign back to its previous status (typically Active). The history rolls forward.
* **Delete** — permanent. Confirms first. Only use when you're certain the campaign is genuinely obsolete.


---

# 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/campaigns/how-to-use-mobly-campaigns.md?ask=<question>&goal=<endgoal>
```

`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.
