Building the target audience

Segment by shared objection

The instinct is to build the audience the way territories are built, by size and region and industry. That is how accounts are owned, but it is not necessarily how they argue. Since the agent drafts against one brief for the whole campaign, the audience should group accounts that share the objection the brief answers.

The test is simple. If two groups of accounts would need different arguments to be persuaded, not different examples but different arguments, they belong in separate campaigns whatever their firmographics say. If accounts across three revenue bands all stall on the same concern, they belong in one campaign whatever their size says.

This is also the cheapest way to avoid the most common disappointment with generated copy. A campaign whose audience spans two incompatible arguments produces assets that hedge, because hedging is the only way to address both. Reviewers read the hedge as weak writing and start editing sentences, when the actual defect was upstream in who was included.

Check the evidence before you commit

The reason to draft a landing page per account is that it can reference that account's situation. That only works when the situation is recorded somewhere the agent can reach: the signals on the account, the engagement history, the stakeholders, notes from the last conversation. An account with a name, a revenue band and nothing else does not become specific because it was written about individually.

So spot-check before finalizing. Open three accounts from the list you have selected and read what is actually on the record. If two of the three are thin, you have found the real constraint on this campaign, and it is not the brief. Either narrow the audience to the accounts where the evidence exists, or accept that this campaign should generate one master page rather than per-account pages, which is a decision the next module covers directly.

Size is a review decision

Every account in the audience can produce an asset, and every asset is nominally somebody's to approve. So audience size is also a decision about review load and about credit consumption, both worth making deliberately rather than discovering when the assets tab fills up.

This is not an argument for staying small. A later module gives you a sampling discipline that makes large campaigns tractable. It is an argument for knowing the number now, naming the person who owns review, and confirming they can absorb it before you move on.

A worked selection

Continuing the example campaign: the objection is "migration risk", so the audience is accounts that have shown platform intent but stalled at evaluation. You search Segments and find two candidates: "Mid-market, evaluating ops tooling" (defined in RevTech: mid-market band, intent signal on ops-platform topics, no open opportunity) and a HubSpot list called "Ops webinar attendees FY26".

The segment wins for the core audience, because you can open its definition and see exactly why an account is in it, and it keeps admitting new accounts as they come to match. The HubSpot list is a snapshot of one event, maintained by whoever owns the webinar program. It is useful as a supplementary audience, but as the core it would freeze the campaign at one moment of one channel. You select the segment, add the list as a secondary, and then run the evidence check: three accounts opened, two have intent signals and named stakeholders, one has nothing but a form-fill. That ratio is good enough to proceed per-account for briefs, with the thin accounts noted for the campaign-level page instead.