Campaign Status TemplatesCampaign Status Templates for Salesforce
Define your Campaign Member Status values once. Every new campaign gets the right statuses automatically, and existing campaigns move to the standard with a preview, mappings for old statuses and no lost members.
The problem
Salesforce stores member statuses per campaign. Every new campaign starts with "Sent" and "Responded", so marketing operations teams set up the same statuses by hand, campaign by campaign. The result is inconsistent statuses and reports that do not add up. The idea to make the values reusable has been on the Salesforce IdeaExchange since 2007 with almost 3,000 votes, and it is archived.
What the app does
- Reusable templates. A template is a named set of statuses with label, responded flag, default flag and sort order. Templates are custom metadata, so you can move them between sandboxes and production with change sets or packages.
- Automatic on new campaigns. Choose the Campaign Types for each template, plus one org default. A new campaign gets its template in the same transaction, also for imports of hundreds of campaigns.
- Rollout to existing campaigns. Select campaigns, preview every change, map old statuses to new ones, and apply. Members move to the mapped status before an old status is removed.
- Conflicts made visible. A status with members and no mapping is a conflict. Per template you choose: keep it, move its members to the default status, or skip the campaign. You can add one-time mappings in the preview.
- Governance. Two permission sets (Admin and User), edit access checks per campaign, an audit log of every change, a pause switch for data loads, and an option to reject a campaign save when its template cannot be applied.
- Flow action. "Apply Campaign Status Template" for your own automation.
How it compares
| Native Salesforce | Type-based default apps | Campaign Status Templates | |
|---|---|---|---|
| Statuses for new campaigns | Manual per campaign | Automatic by Type | Automatic by Type, plus an org default |
| Change existing campaigns | Manual per campaign | No | Bulk, up to 2,000 campaigns per run |
| Preview before changes | No | No | Yes, per campaign and status |
| Move members from old statuses | Manual | No | Mappings in the template and per run |
| Audit log | No | No | Yes |
Built for safe changes
- Every change runs in one transaction per campaign: if one campaign fails, it is rolled back and the others continue.
- The app follows the platform rules for member statuses: one default, at least one responded status, unique labels, and no deletion of statuses that members use.
- No data leaves your org. The app has no external callouts.
Get started
Read the setup guide and FAQ. Questions: help@elektraset.com.