Create Accountor Login
Docs

MountDev Ops Campaigns

How MountDev Ops Campaigns works, page by page. Updated October 14, 2026

MountDev Ops Campaigns documentation | Updated October 14, 2026

Our Commitment

MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.

Every update passes all 1,932 automated checks before it ships, plus screen tests on 9 screen sizes for everything it changes.

Tested Every Release

All 52 of Campaigns's own automated checks run on every update, plus 36 screen tests whenever Campaigns's screens change.

What they cover: Email | Records and fields | Contacts, leads, and deals | Import and export

What Campaigns Is

Campaigns sends email campaigns to the people in your CRM: write the email from simple blocks in your brand, choose who it goes to with a saved filter or a list, send yourself a test, then confirm and send it now or at a set time. It sends through the email sending service your company already uses, connected in API Connections, so the emails come from your own domain and your sending service's account.

Campaigns can be added without CRM, but it chooses its recipients from CRM's contacts and leads (or any module with an email field), so add CRM to send anything.

The Rules Every Campaign Follows

  • Consent first. Nobody is emailed without a consent record that says they agreed (Consent). People who unsubscribed, withdrew their consent, bounced, marked an email as spam, are on the suppression list, or have Email opt out turned on in CRM are always left out.
  • Do Not Contact, before every send. Your workspace's Do Not Contact list is checked when a campaign is confirmed and again right before every email, test email, and confirmation email. Anyone on it is left out, with the reason.
  • Every email in Arial, with its reason. Every email says why the person is getting it, shows your postal address, and has an unsubscribe link and the one-click unsubscribe header mail apps use.
  • UTM tags on every link. Campaigns adds utm_source=email, utm_medium=email, utm_campaign (from the campaign's name), and utm_content (where in the email the link was) to every web link, so visits from your campaigns show up in your website's analytics. Links that already have UTM tags keep them.
  • A confirmation before any real recipient. A campaign goes out only after an owner or admin confirms it, seeing exactly how many people it goes to and who is left out (Sending).
  • AI agents draft, people send. A connected AI agent can write and change drafts, saved filters, and lists, but it can never send, schedule, or test a campaign, and never records consent.
  • Tracking only where you allow it. Opens and clicks are counted only as your tracking setting allows (Campaigns Settings). It is off until you turn it on, and turning it on asks you to agree that your company keeps consent records for it.

Starting Modules

  • Consent Records: a copy of every consent and withdrawal: email, name, status (Pending, Active, or Withdrawn), how they agreed (double opt-in, single opt-in, or existing customer), where they agreed, what they agreed to (the words they saw), whether they also agreed to open and click tracking, IP address, browser, when they agreed, when they confirmed by email, and when they withdrew.
  • Suppressions: email, reason (Unsubscribed, Bounced, Complained, or Added by hand), source, since when, and a note.

Both are modules like any other: you can see, search, export, and import them, and add fields of your own. A consent record keeps what the person agreed to, so it never changes (except fields you added); withdrawing adds its own record (Consent). A suppression keeps why an address is never emailed, so only its note changes. Deleting a suppression record does not lift it: Campaigns keeps its own permanent copy of the suppression list.

Pages

  • Campaigns and the Editor: the campaigns list, writing an email from blocks, and the preview.
  • Saved Filters and Lists: choosing who campaigns go to.
  • Sending: test emails, the confirmation step, scheduling, and stopping.
  • Results: delivered, opened, clicked, unsubscribed, and bounced.
  • Consent: consent records, unsubscribes, and the suppression list.
  • Campaigns Settings: the sending service, From address, brand, postal address, tracking, and delivery reports.

Who Can Do What

  • Everyone in the workspace can see campaigns, their results, saved filters and lists, and look up whether an address can be emailed.
  • Write campaigns (owners, admins, and members): write and change drafts, keep saved filters and lists, and send test emails.
  • Send campaigns (owners and admins): confirm, schedule, unschedule, stop, and resume campaigns.
  • Manage Campaigns (owners and admins): Campaigns Settings, recording and withdrawing consent, the suppression list, and exporting everything Campaigns keeps.

Ask Us Anything

We’d love to hear from you!