What a Campaign Actually Is

Lesson 1: The Definition

A Bolta Campaign is a themed, time-boxed body of content with exactly one editorial angle.

Four words in that sentence are load-bearing:

• Themed — it is about something specific. "Spring launch." "The new dashboard." Not "our social media."
• Time-boxed — it starts on a date and runs for one to four weeks. It has an ending, and the ending is the point at which you can say whether it worked.
• Body of content — it plans a countable number of pieces, in named formats, on named accounts.
• One angle — exactly one editorial stance, chosen from six. Not two, not a blend. A campaign that takes two positions is two campaigns.

Everything else about the feature follows from those four. The four-week ceiling is there because a campaign is a push, not a permanent arrangement. The single angle is there because a writer given two stances produces content that reads like neither.

Lesson 2: A Push, Not an Arrangement

The distinction people get wrong most often is between a campaign and a Routine — a standing arrangement that runs indefinitely, doing the same kind of work forever until you turn it off. A routine has no ending and no subject. It is your baseline presence.

A campaign is the opposite shape: a finite push with a subject. It starts, it runs for a set number of weeks, and it finishes. Then you read the result.

The practical rule: if you cannot name what the content is about and when it ends, you want a Routine. Module 3 covers routines properly, including the three questions that settle it.

Under the hood a campaign is an envelope over the same machinery routines use. Its runs are the same run records, dispatched through the same single entry point. That is deliberate: a second execution path would mean two different answers to "did this run?", and there is only ever one.

That shared spine is also why the two objects behave alike in ways that surprise people — both derive their run status rather than storing it, both treat archiving as terminal, and both are restored by cloning rather than re-arming.

Lesson 3: Where a Campaign Sits

Bolta has four objects that produce or organise content, and they are constantly mistaken for one another. Here is the whole map in one table; three of them get a module of their own next.

Object	What it is	Has an ending	Can publish without you
Agent	A worker you hire, with a persona and an autonomy level	No	Yes, if set to auto
Routine	A standing arrangement — this work, on this trigger, forever	No	Yes, if your policy allows
Campaign	A brief: one subject, one angle, a finite window	Yes, 1–4 weeks	Never
Calendar	A view of everything you publish, from every source	n/a	It publishes nothing

The shortest way to hold it:

• An agent is who does the work.
• A routine is when work keeps happening.
• A campaign is what a body of work is about.
• The calendar is where you see all of it at once.

The next three modules take the first three in turn, because choosing between them wrongly is the most expensive mistake available in this part of the product — and the fourth, the calendar, is where you will spend the most time without it ever being the thing that made the content.

Lesson 4: The Word Means Three Things

Bolta uses "campaign" for three unrelated things internally. You only navigate to one of them, but you will see the other two in the interface and it is worth knowing which is which.

1. Content Campaigns — this course. Found at /dashboard/campaigns. A themed run of content with a strategy, a window, a CTA and a content mix.
2. Calendar campaign labels — a grouping tag you can put on posts in the calendar so related posts show a coloured chip together. Purely a label. It has no strategy, no window, and generates nothing.
3. Hunter campaigns — the acquisition monitor. It watches a query on a platform and surfaces or replies to matching conversations. Entirely different machinery and an entirely different lifecycle.

If someone says "start a campaign" and means content, they mean the first one. The calendar chips and the Hunter monitors are not the same object and cannot be converted into one another.

Lesson 5: What a Campaign Owns

A campaign is smaller than it looks, and that is a feature. Being precise about what it controls saves you from looking for settings that live somewhere else.

A campaign owns:

• Its name, theme and audience — the subject, in your words
• Its strategy key — the one angle
• Its window — a start date and a duration in weeks
• Its call to action — text and URL
• Its targeting — which social accounts it publishes to
• Its content plan and mix — what formats, how many, on which days
• Its voice profile — which voice it writes in
• Its context — the notes you typed and any sources you attached
• Its per-campaign setting overrides — tone, post time, image quality and more
• Its lifecycle status — draft, scheduled, active, paused, completed, archived

A campaign does NOT own:

• Run status. Whether a run succeeded is derived from the run records every time it is read, never stored on the campaign. This is why the detail page can correct itself while you are looking at it.
• Dispatch. The campaign does not execute anything. It hands a validated objective to the same dispatcher every routine uses.
• Authorization. A campaign grants nothing. If your plan does not entitle you to a run, naming it in a campaign does not change that.
• Results. There is no results table and no cached rollup. Every number on the results section is derived on read from the same posts and publication records every other screen reports from. A copied number is a number that starts disagreeing with reality the week after it is copied.

That last point is worth internalising, because it explains a behaviour you will notice: campaign numbers can change without you doing anything. A post that publishes an hour after you looked will be counted the next time you look. Nothing was recalculated — it is derived fresh every time.

What to take away

• A campaign is a subject plus a window. It is finite by construction.
• Four objects, four jobs: agent = who, routine = when, campaign = what about, calendar = where you see it all.
• Use a Routine for baseline presence; use a Campaign for a push about something.
• "Campaign" names three things in Bolta; only one of them writes content.
• Nothing about a campaign's outcome is stored — it is derived every read, which is why it is always current and occasionally changes under you.