RCSync DocsPowered by Whisp
Sign in

Your audience

Saved audiences

Build a group of contacts from what you know about them, save it, and send to it — with dynamic audiences re-checked every time they're used.

Two kinds of audience

  • Dynamic — a saved set of conditions. Membership is worked out fresh every time the audience is used, so it always reflects your contact list as it is now.
  • Static — a fixed list of contacts, frozen when you saved it. It only changes when you change it.

Dynamic is the default and usually what you want. A weekly recurring campaign pointed at a dynamic audience automatically picks up everyone who opted in since its last run.

Creating one

Both start on Contacts. Tick the rows you want — or build a segment and tick the page, then Select all N matching — and use Save as audience. With a segment active you are asked which kind you want: these N contacts freezes a snapshot, and this segment saves the conditions to be re-checked on every run. Ticking rows with no segment can only be a snapshot, since there is no query to re-run.

What you can filter on

  • Area code and exchange — the first three, or first six, digits of a US number.
  • Tags — labels you've put on contacts, on a contact's own page or in bulk from the list. The condition offers the tags actually in use, so a tag nobody has been given can't be picked. See Contacts → Tags.
  • How they were added — imported, opted in by keyword, added through your own system, and so on.
  • Consent status — one of four: opted in, opted out, no consent record, or not opted out. The last is the one to reach for by default, and it is not the same as “opted in”: it means everyone who has not asked you to stop, which includes people with no consent record at all. Whether those people are actually messageable is still decided at send time by your own permission to contact them.
  • Reachability — has, or does not have, a phone number or an email address.
  • Engagement — as a recency window (“clicked in the last 30 days”) or a count (“at least 2 link clicks”). Sent, delivered, opened, replied, and link clicks and chip taps separately, plus Engaged (any), which counts clicks, chip taps and replies together.
  • Campaign history — was sent, or engaged with, a specific campaign (or wasn't, or didn't).
  • Clicked link URL — matches part of the link a contact clicked, so “/offers/spring” finds everyone who tapped any link under that path. It is a substring on purpose: delivered links carry tracking parameters, so an exact URL would match almost nobody. Matching ignores case.
  • Date added, and last activity.
  • Your custom fields — declared on Contacts → Custom fields, or from a column while confirming an import; only a field declared as a number can be compared with “more than” or “less than”.

Conditions combine with all (every condition must hold) or any (at least one).

A note on “hasn't engaged”

A condition like last engaged more than 90 days ago deliberately includes contacts who have never engaged at all. They plainly haven't engaged in the last 90 days, and leaving them out would quietly exclude the people a re-engagement campaign is aimed at.

Estimated reach

As you build a segment, RCSync shows an estimated reach. It is an estimate, and it is deliberately labelled as one.

The estimate counts contacts matching your conditions. When a campaign actually sends, it is filtered again — opt-outs are removed, unreachable numbers and addresses are dropped, and anyone over your brand's frequency cap is held back. The number that sends is therefore normally smaller than the estimate, and the campaign's own report is the accurate one.

Using an audience in a campaign

On a campaign's Audience step, choose a saved audience instead of uploading or pasting a list. At send time the audience is resolved into a recipient list, and everything after that — batching, suppression, cost estimates — works exactly as it does for an uploaded list. See Campaign audiences.

Recurring campaigns

A recurring campaign re-resolves its dynamic audience on every run. You can also tell it to skip anyone an earlier run already reached, which turns a recurring campaign into a rolling welcome message for new contacts rather than a repeat send to the same people.

If an audience matches nobody

Activating a campaign whose audience currently matches no contacts is refused, with a message saying so. This is a real state worth catching — a filter with a typo, or a segment that has emptied out since you built it — and it's better caught at activation than discovered in a report showing zero sends.