Skip to content

Campaigns

Campaigns (/campaigns) is where posts are planned, approved, scheduled and followed until they go out. It is one page, built like Leads: what needs you, a few counts, your campaigns, then one board of every post.

Every card on the board is one post, never a whole campaign. How a post moves from idea to sent is explained in Drafts, approval and publishing.

The top of the page

  • Needs you now: each post that waits for you, one line each: Approve “…”, Write “…” (a post that is still only an idea), or "…" did not go out with the reason. Do it acts on it; Skip puts it off until your next visit. When nothing waits it says Nothing waits for you.
  • The counts: Running campaigns, Proposals waiting, Drafts to approve, Scheduled this week, Sent this week. A count PULSE could not read shows —, never 0.
  • Replies waiting for you: the replies Autopilot drafted to comments, mentions and messages. See Autopilot.
  • What your audit found: the campaigns PULSE proposes. See below.

Two buttons float at the bottom right: New Campaign, and Check a competitor’s content, which compares what a competitor publishes with yours.

The campaign strip

One row per campaign, newest first (archived ones and proposals you set aside are left out). Each row shows its state and its counts: N planned · N to approve · N scheduled · N sent. Why shows why PULSE proposed it.

  • Tap a campaign to narrow the board to its posts.
  • Open campaign opens its own page.
  • A campaign PULSE proposed and you have not accepted is read only, marked Proposed by PULSE, with Review and accept and Dismiss. While its plan is being prepared it says Preparing its plan, then Plan ready (or Plan failed).

The board

Four columns, in order:

ColumnWhat is in it
PlannedPosts a campaign’s plan holds that are not written yet. Create opens Studio to write one.
Drafts to approveWritten posts waiting for your OK. Each says when it is planned for, or Not scheduled, and its next step.
ScheduledApproved posts with a time to go out (Goes out …), or Approved: pick a time to send it. A post that did not go out stays here with its reason.
SentPosts that went out, with the day.

A card names its channel and where it came from: its campaign, From your check-up of …, Placed by Autopilot, or Not in a campaign. Open a card to read the post, its steps and its actions:

  • Draft opens it in Studio to write or change it.
  • Download saves it as files you can post yourself (approved, scheduled and sent posts). See Download.
  • Move moves it to another column (see the rules below).
  • Discard (drafts) rejects it. A rejected post leaves the board.
  • Reschedule and Remove (scheduled posts).
  • Automate opens its own automation. See Automate.

Approve and schedule

  • Move a draft to Scheduled to approve it and schedule it in one step: PULSE asks for the day and time.
  • Approve from Needs you now approves it without a time. With Autopilot on for that account, PULSE then queues it at the account’s best time. With Autopilot off, it goes out when you approve it, or at its planned time if it already has one that is still ahead.
  • Move a scheduled post to Scheduled again to pick a new time.

Some moves are refused, with the reason:

  • A post that is only an idea cannot be scheduled: Write it first.
  • Nothing moves to Sent by hand. A post reaches Sent only when it really went out.
  • A written post never goes back to Planned.

Approving does not by itself publish. Whether a post goes out is decided when it is due: its channel must be connected and Active, and your administrator must have publishing switched on. Otherwise the post stays in Scheduled marked held back (withheld) or failed, with the reason. A post whose time passed while it waited for approval is marked missed and is never sent late; reschedule it or remove it.

A campaign’s own page

Open campaign opens /campaigns/<id>. All campaigns takes you back.

At the top:

  • its state (Not started, Running, Paused, Finished, Archived), its dates, budget, spend and channels, with Edit Campaign and Start, Pause or Resume. A running campaign gets PULSE’s daily drafts; a paused one does not. Spend is shown only when an ad account reports it;
  • Why PULSE proposed it, for a campaign PULSE proposed;
  • its phases, one line each: name, weeks, and how many of its posts are made;
  • About this plan, for a campaign with a plan (see below);
  • its milestones, each with its done criteria and who approves it;
  • Results: the plan’s targets with what was measured against them. A result PULSE has not measured says so, never 0. Without a plan it says No targets yet.

Below, Board shows the same board narrowed to this campaign, and Timeline shows every recorded step of every post in date order. Steps with no recorded time are counted, not placed.

About this plan

One line sums up the campaign’s plan, for example About this plan: Plan accepted · tone: friendly, expert · 3 Story ideas · 1 check failed. Tap it to open the details:

  • Verdict: what the plan gate said, with its reason. Plan accepted; Plan not checked by the reviewer (the reviewer could not judge it, which is not an approval); Plan not reviewed (the reviewer is switched off on this server); or Plan withheld. A new plan the gate withholds is not saved: Plan your calendar shows why, and the plan you had stays.
  • Tone: how you sound to each persona, with an example line.
  • Story ideas: the Instagram Stories, under the phase their day falls in, each with its day, time, picture, text and sticker.
  • Checks: each of PULSE’s checks on the plan (your capacity, the selling ratio, each post’s details, the Story days, repeated topics, the three targets), passed or failed, a failure with what it found. A plan with no checks recorded says not checked, never “0 failed”.
  • Where PULSE won’t post: for each channel of the plan PULSE cannot post to today, PULSE won’t post on … because: …, read from the same rules that decide sending (for example no publisher for Facebook, the channel switched off, or publishing switched off for the server). A channel that can post gets no line. If PULSE could not check, it says so.
  • Notes: what PULSE could not do or measure when it made the plan.

Make its plan

A campaign without a plan offers Make its plan (Change the plan once it has one). Plan your calendar asks what you can manage:

  • the first and last day, and an event if there is one (its day and how many days it lasts);
  • how many posts a week you can manage per channel, and Instagram Stories a day during the event;
  • how often a post sells something (One post in every N sells something).

PULSE lays the posts out inside that. It places each post at your best time where it has measured one (otherwise at a starting time it labels as such), and writes a first idea for each post: topic, format, who it is for, first line and what readers should do, plus a tone for each persona and three results to aim for. Its checks test your capacity, the selling ratio, the dates and duplicates, and the plan gate reviews the plan against your check-up. Writing it can take a few minutes; you can leave the page.

PULSE needs to know who you talk to. If no check-up or lead tells it, the plan is refused with: PULSE does not know who you talk to yet: run a site audit (it asks who buys from you) or add leads, then plan again.

The plan’s posts appear in Planned. Studio writes them, and Autopilot never queues a post before its planned time.

The step trail

Open any card, or use Timeline, to see Its steps:

Planned → Drafted → Approved → Scheduled → Sent, or Withheld, Failed or Missed.

Each step says when it happened and what PULSE recorded: the phase and planned date, which skill wrote the draft and its check results, who approved it, when it was queued and for when, and where it went out or why it did not. Every step is read from what PULSE stored:

  • not yet: the step has not happened;
  • not recorded: it happened (a later step proves it) but PULSE kept no record of it, for example who approved a post approved before approvals were recorded.

A post sent through a channel you have not connected says to download it and post it yourself, rather than showing the platform’s raw error.

Campaigns PULSE proposes

From a check-up’s content gaps, PULSE may propose a campaign whose objective matches your goal. It waits under What your audit found and in the strip as Proposed by PULSE:

  • Review and accept shows the proposal; you can change its name, objective (required) and description, then accept it. Accepting prepares its content strategy and plan. Nothing is published.
  • Dismiss sets it aside. Set-aside proposals are kept, and you can open one again and accept it.

Automate

Every card (posts, leads, public tenders, partners) has Automate. It opens that item’s own automation over the page: a trigger, then steps. Tap a step to change it; add or remove steps. The assistant can propose steps; you approve them.

An automation is disarmed until you arm it: then it runs only as a Dry run, which shows what it would do. Once armed, it runs by itself when its trigger fires, and anything it sends still needs the server’s publishing switches. A step the server cannot carry out says so, and an automation that cannot run yet lists why.

Old addresses

/approval, /publishing, /strategy, /content-strategy, /content-gaps, /strategy-roadmap and /automations open this page; /approval and /publishing bring Drafts to approve into view.