CONTACTS AND AUDIENCES
Build an audience you can defend
An audience is a list you can explain to the person who asks why they were messaged. That means a filter you can read back, an export that never leaves your browser, and a build that stops when it cannot see the opt-out list.
Everybody who has ever messaged one of your connected numbers is a contact. WhatsApp audience segmentation is not about storing them — it is about choosing a defensible subset of them and proving later which subset it was.
What you can filter on
The most useful filters are about behaviour rather than fields.
When they last wrote
The filter most audiences are really about: somebody who messaged this week is a different proposition from somebody who messaged last year. You can filter on the first message too, and on how many messages a contact has sent.
Which number they reached
A contact belongs to the number they wrote to. An audience can be scoped to one number, which is also what keeps a campaign sending from the number the conversation already happened on.
Whether they came from an advert
A contact who arrived by tapping a Click-to-WhatsApp advert carries that fact, so an audience can be the people your adverts brought in.
Country, number type and marks
The country a number was allocated in, whether it is a mobile, a landline or an internet (VoIP) number, and whether somebody has marked the contact suspicious or blocked them.
The export is built in your browser
The rows never pass through a third party, because they never leave the page.
Choosing export builds the CSV in your browser from the rows already on the page, and the download is a local file. No copy is stored anywhere for it, so there is nothing to expire, nothing to leak and nothing to delete afterwards.
A spreadsheet you import is read in your browser too, and it carries one refusal worth knowing about: a phone number a spreadsheet saved in scientific notation is rejected rather than imported. By the time a number reads as 9.71E+11 its last digits are already gone, and an audience built from it would message whoever now owns the number it rounded to.
What makes a build refuse
Each of these is a build that produced nothing rather than a list that was quietly wrong.
The opt-out list could not be read
The build stops. An opt-out list that cannot be read never widens an audience; nothing is built until it can be read. This is the one failure on the page that cannot be taken back once a send has happened.
The block list could not be read
Same answer, same reason. Somebody who was blocked must never reappear in a list because the block list could not be read.
An exclusion could not be resolved
If an audience is these people, minus another list, and that list cannot be read, the build is refused. A missing exclusion must never widen a list.
It is larger than the ceiling
Past the member ceiling the build is refused outright and the previous members are kept, so a mistake in a filter does not destroy a list that was already correct.
An audience remembers how it was made
A saved audience holds either the members themselves or the filter that produced them. Only an explicit refresh re-runs a stored filter, and it runs with the access of the person who pressed it — so an audience never grows overnight on its own.
Removing a person by hand is recorded as an exclusion rather than a deletion, which means a later refresh cannot put them back. That is the difference between a list you can defend and a list that happens to be right today.
Where it sits
WhatsApp marketing campaigns
What an audience is for, and why a retry never sends anybody a second copy.
WhatsApp shared inbox
Where a contact’s conversation lives, and who may open it.
WhatsApp data protection
Where the contacts are stored and how long each thing is kept.
Build one on your own contacts
From the blog
Further reading on this subject.
Campaigns that keep a number healthy
Consent, audience segmentation and pacing that keep campaigns working.
WhatsApp marketing from your Bitrix24 CRM
Campaigns to CRM segments, automation by deal stage and UTM lead tracking.