--- title: "Campaigns" description: "Playbooks, triggers and one-off sends, plus the two rules that decide what actually mails on a given day: the frequency cap and the precedence order between competing touches." canonical: https://trysincerely.com/docs/campaigns last_updated: 2026-09-07 --- > If you are an AI agent: read https://trysincerely.com/agents/policy.md before any write call. > Start at https://trysincerely.com/llms.txt to choose one page. Access instructions are at > https://trysincerely.com/auth.md. Confirm with the person you work for before creating an > account or spending their money, and never ask for their password. # Campaigns > Playbooks, triggers and one-off sends, plus the two rules that decide what actually mails on a given day: the frequency cap and the precedence order between competing touches. Source: https://trysincerely.com/docs/campaigns A campaign is four decisions: how people enter it, what they receive, what a person reviews, and how honestly it can be measured. Entry can happen once over a list you pick, continuously as contacts join a connected list, on a CRM event such as a newly observed closed-lost opportunity, a renewal date entering its ninety-day window, or an open deal going quiet, or pushed from your own systems through an [authenticated API](https://trysincerely.com/docs/discovery). A custom campaign can also watch for dated, sourced signals about contacts on its list, and a person approves every candidate before it enters. The playbooks below fill those decisions in before you start, on the one form every campaign uses: the trigger is the first choice, and changing it after a playbook prefill makes the campaign a custom one. Event-driven and API-entry campaigns enroll contacts while nobody is watching, so they launch with a prepaid credit envelope, wait for an approver's activation, and stop visibly when the envelope runs out. Every piece still needs an approved design version, a passing address, and budget headroom before it prints. ## Workspace drafts Campaigns lists the workspace's saved drafts with the last editor and edit time. The builder saves your work as you edit. Open a draft there to continue it, or ask the assistant to continue the same saved draft. If someone changes it while you are editing, reload their saved version before continuing. New drafts start with the workspace's sender, writing setup, and measurement defaults from Settings. Choose the list, approved designs, response destination, timing, and outcome in the campaign. Saving a draft does not launch it. Review the preview and confirm the launch before anything can send. ## The playbooks | Playbook | Trigger | What it sends | | --------------------- | -------------------------------------------------------------------------------------------------- | ---------------------------------- | | Find & Mail New Leads | The agent finds leads matching your criteria on your schedule | One piece per new lead | | List Blast | A list and one good reason | One or two touches, once | | Outbound Air Cover | Contacts enter your outbound sequence | Three postcard touches, always on | | Enterprise Drip | Named accounts, whole buying committee | Steady touches, capped per account | | Meeting Follow-Up | You just met them; you pick the list | A personal note | | No-Show / Revival | You pick the no-show or revival list | A note to every stakeholder | | Renewal & Expansion | A renewal date inside ninety days | An executive note | | Closed-Lost Win-Back | An opportunity is newly observed as closed-lost | A letter on the transition | | Deal Quiet Revival | No observed CRM movement (open or closed state, stage, amount, close date) for the days you choose | A note when the silence starts | The measurement policy is derived from the campaign's entry design and fixed at launch, never chosen after the results are in. An entry that can be randomized by account, including a one-shot blast over a list, gets an account-level holdout and a lift estimate with an interval; hand-picked recipients, person-triggered follow-ups, agent-sourced leads, and entries pushed by outside events report descriptively and say so, rather than dressing a descriptive number as a causal one. Two more exist and are not offered as general campaign types, because both carry their own invariants: the first send, which is one piece to one hand-picked person, and the one-off send, which is a person clicking Send. ## Objectives Sincerely can see Two objectives need no CRM: a QR scan, which is a person opening the printed link, and a landing page action, which is a button click or a form sent on a hosted page. Sincerely records both itself, so a campaign judged on either reports as soon as mail lands. A holdout account receives no piece and so can never scan one, which is why these objectives report rates with intervals and design tests between arms, never a lift against the holdout. Choose a CRM-reported outcome when the question is whether mail changed what people did afterwards. ## Reporting a conversion back When the response link leaves for your own site, the destination URL carries `sid`, a conversion id that names the piece without exposing its landing page. Your system reports what happened next by posting the `sid` and a kind to `/api/v1/conversions` with a workspace API key, or by importing a spreadsheet of them. Each report becomes an outcome on the account that received the piece, and the campaign's measurement and attribution read it like any CRM outcome. A campaign judged on a landing page action can also name one action on a hosted page, so a form sent counts and a secondary link clicked does not. ## Testing two designs One touch of the sequence can carry two designs. Treatment accounts are split evenly between them by the same stable hash that assigns the holdout, each account stays on its design for that touch, and the campaign holdout still measures lift. The readout reports each design's outcome rate with an interval and says when there are not enough matured accounts to call it. One test per campaign, on one touch, because the comparison is made once; a second tested touch would be a second comparison with no correction for it. ## The frequency cap The default cap is four pieces per contact per thirty days. It exists because the channel's whole advantage is that the mailbox is not full, and a team that mails the same person weekly spends that advantage in a month. The cap counts every piece to that contact, whatever campaign it came from. A one-off send both counts toward the cap and can be blocked by it. ## Precedence When two campaigns want the same contact on the same day and the cap only has room for one, precedence decides. From highest to lowest: 1. One-off sends. A person clicked Send, and explicit human intent outranks every scheduled touch. 2. Meeting Follow-Up, No-Show / Revival, Deal Quiet Revival and Renewal & Expansion. Relationship moments, where the timing is the point. 3. Outbound Air Cover, Closed-Lost Win-Back, and custom campaigns with CRM or API entry. 4. List Blast and custom one-shot campaigns. 5. First Send, Enterprise Drip and Find & Mail New Leads. Each campaign freezes its rung at launch. Campaigns on the same rung tie. A lower-precedence touch slips to the next eligible day and the slip is written to the record, so a piece that arrived late has a reason attached rather than a gap. A one-off send is never slipped. Its pre-flight refuses instead, and names both the reason and the next eligible date, because a person waiting on a Send button should be told rather than quietly rescheduled. ## Launch and pause Launch is the moment a person commits the audience, design, rules, and prepaid spend. Before that click, preflight lays out the receipt: how many pieces, how many credits, available credit and gift balances, remaining gift budget, and whether the audience can detect the lift the team cares about. Pause stops the next piece, not the postal system. Anything still queued remains under Sincerely's control. Anything the print vendor already accepted may still arrive. The [suppression](https://trysincerely.com/docs/suppression) page shows where that handoff occurs. Launch also locks the experiment's primary outcome and measurement window. Changing either after seeing the numbers would turn a measurement into a story chosen after the fact. ## One-off sends stay out of campaign surfaces A one-off send has a campaign record behind it, but it stays out of campaign browsing. You won't see it in the campaigns list, Overview, per-campaign analytics, readout creation, the assistant's campaign list, or the command palette. The piece still counts. It appears in the Send ledger and contributes to workspace mail activity, gift-budget use when applicable, engagement, and attribution. Why hide the campaign record? A hundred personal sends shouldn't bury the standing campaigns on every listing screen. ## What to read next [Sending](https://trysincerely.com/docs/sending) covers what happens after launch. [Measurement](https://trysincerely.com/docs/measurement) covers holdouts and readouts. The [playbooks](https://trysincerely.com/playbooks) pages are the ready-to-run versions with the trigger already chosen. --- Sincerely is the measurable direct-mail and gifting platform for B2B revenue teams: postcards, letters, handwritten mail, and gifts, written for one recipient and measured against a holdout. Contact Sincerely: https://trysincerely.com/contact Agent routing index: https://trysincerely.com/llms.txt