SMB Pulse

Run a campaign, then see if it moved anything

Send a campaign to the subscribers who have stopped ordering, with anyone who complained recently left out and named, have the owner approve it, and afterwards read what it changed against the fortnight before.

Pick a use case and follow its guide

Run a campaign, then see if it moved anything

0 of 6 steps done

Sign in to try the demo
  1. Step 1. Open Operations, then campaigns.start_from_sales. Type the campaign's discount code in discount_code (for example ETHIOPIA15) and its tracking tag in utm_tag, and press Call campaigns.start_from_sales. Under ANSWERED, campaign is the stored draft, with status draft, the products it pushes and bundles, and its campaign_id. Nothing is sent. Open campaigns.start_from_sales

  2. Step 2. Open Operations, then campaigns.define_audience. In campaign_id, type the id the previous step returned. In segments, type subscription-customers-no-order-60-days and press Enter, then press Call campaigns.define_audience. Under ANSWERED, the segment's count is the subscribers whose last successful charge is more than two months old; excluded names each one held back by a recent complaint, matched by customer or by email; and sendable_count is what is left. Nothing is sent and nothing is stored. Open campaigns.define_audience

  3. Step 3. Open Operations, then campaigns.stage. In campaign_id, type the campaign's id. Press Add drafts once for each post, email and design request, giving each its draft_id, kind, channel, scheduled_at, subject and text, with the email's audience_segment set to the segment of the previous step. In as_of, type the moment to stage from (for example 2026-09-14T09:00:00-07:00); left empty, it is the real clock, and any draft dated before it is refused as past. Press Call campaigns.stage. Under ANSWERED, staged lists each draft held for approval, an email with the recipient count the app computes from its segment. A draft scheduled at or before now, or with an image slot still missing, is listed under refusals with its reason. Nothing is approved or sent here. Open campaigns.stage

  4. Step 4. Signed in as the owner, open Workflows, then campaign-staging, and press New run. The run takes the oldest staged draft and stops at approve_draft. In the Runs tab, press Open decision. The draft's amount is its recipient count, computed by the app; a large send may be approved only by the owner. Check that approval_meta holds your user id, press Save under it, then Resume. The run turns SUCCEEDED, and approval_record records who approved, when, the recipient count and a sentence saying the send was simulated. Nothing is sent. A run with no staged draft ends without a pause. Open the campaign-staging workflow

  5. Step 5. When the campaign's window has passed, open Operations, then campaigns.results. In campaign_id, type the campaign's id and press Call campaigns.results. Under ANSWERED, redemptions counts the charges that carried the code, code_signups the subscriptions signed up with it, and products gives each pushed product's revenue in the window, the fortnight before and the same dates last year, with the change against each. Every product row carries the note that a change is inferred, not proved to be the campaign's, and there is no total across products. A campaign whose window has not started reads "no results yet". Open campaigns.results

  6. Step 6. Open Operations, then campaigns.explain_results. In campaign_id, type the campaign's id and press Run campaigns.explain_results. The run turns SUCCEEDED. The growth marketer writes one paragraph on what worked and what did not; every figure in it is filled in by the app from the results, an inferred figure is worded with a hedge, and any unsubscribes are mentioned. The wording differs from run to run. A paragraph that breaks those rules is held, with the reason, and carries no explanation. Open campaigns.explain_results

Did it fit your work?