Stop deleting rows in Excel before every broadcast
Tag the behaviour when it happens, then exclude by rule rather than by hand. Registered, clicked, replied, purchased, wrong region: each becomes a condition you write once and reuse, so every future campaign applies it automatically. Editing the file before each send guarantees that somebody eventually forgets.
You're running a webinar. Two hundred people already registered from the last campaign, and you'd rather not invite them again. So you export, sort, delete rows, save a new version, and upload it. Then you do it again next week with a different set.
That process breaks for a predictable reason: it relies on a person remembering, at night, under time pressure.
Replace the manual delete in four steps
Write down what you actually want to exclude
Be specific. “People who registered for this webinar” is a different rule from “people who registered for any webinar in the last 90 days”.
Most exclusion mistakes are definition mistakes rather than tool mistakes.
Capture the behaviour at the moment it happens
Registered, clicked the link, replied, tapped the button, bought, asked to stop. Each one should write to the contact when it occurs, not get reconstructed from a report later.
If the behaviour isn't captured, no amount of clever filtering will find it afterwards.
Build the exclusion as a saved rule, not a saved list
A list is a snapshot and goes stale the moment somebody registers. A rule re-evaluates itself every time you send.
Read it as a sentence before you trust it: everyone in Bangalore who enquired in the last 90 days, excluding anyone already registered.
Check the count before you send, every time
A rule that suddenly matches 40 people when it matched 400 last week is telling you something changed.
Watch the number, not just the rule.
Common exclusions and how to build them
| You want to skip | Build it as |
|---|---|
| Anyone who already registered | A behaviour tag written at registration, excluded by rule |
| A whole region or country | A field on the contact, filtered at send time |
| People contacted in the last seven days | A last-activity date window |
| Anyone who asked you to stop | A permanent suppression list that overrides every campaign |
| Existing customers, on an acquisition campaign | A lifecycle stage on the record |
| People who bounced or blocked | Automatic suppression, kept visible so the count makes sense |
Make exclusions boring
Keep one suppression list that always wins. Opt-outs and complaints should override every campaign, every time, with no way to accidentally send around them.
Name your rules like sentences. “Whitefield, 90 days, not registered” beats “Segment 4 final v2” when you come back to it in three months.
Stop keeping the master list in a spreadsheet. Every manual exclusion problem traces back to the same root cause: the truth lives in a file rather than in a record.
A rule can only exclude what you captured. If registrations were tracked in a Google Form nobody connected to anything, the exclusion has to be built from that export at least once.
Getting it wrong is worse than sending twice. An over-broad rule that quietly removes half your audience looks like a successful campaign, which is how it goes unnoticed for months. Check the count.
Write the rule once and forget it
Amplifeed tags behaviour as it happens and applies your exclusions on every send, so “everyone except people who already registered” stops being an evening of deleting rows.
See it on your own segmentsRelated questions
Can I exclude people without editing my CSV?
Yes, if the behaviour is stored on the contact rather than only in the file. Tag it when it happens, then exclude by rule at send time.
What's the difference between a list and a segment?
A list is fixed at the moment you built it. A segment is a rule that re-evaluates itself, so it stays correct as people register, reply or move region.
How do I handle opt-outs?
Keep a suppression list that overrides every campaign and can't be bypassed by uploading a fresh file. Treat it as permanent.
Can I exclude by region?
Yes, provided region is stored as a field on the contact. If it only exists in the file name, it can't be filtered on.