B2C Marketing Lists

Opted-in Australian consumer records, collected through surveys, competitions and partner programs where the individual gave marketing consent. The universe is maintained at around 20 million current profiles.

Every record carries the source it came from and the date consent was given, so the provenance of any contact on your list can be traced back to a specific collection event instead of taken on trust.

Consent is held at the record level, not asserted at the list level. Each profile carries its consent source and the date it was captured, and records without current marketing consent never enter the list universe at all. They are not filtered out at export; they were never available to select in the first place.

That distinction matters when you are asked to substantiate a send. The consent evidence for any individual contact travels with the record, so the question "why did you contact this person?" has a per-record answer.

Every phone record is checked against the Do Not Call Register before the list is delivered to you, and the date of that wash is recorded with the file.

Timing is critical here. Compliance is assessed as at the date you make the call, not the date you acquired the list, so a file washed months ago and dialled today gives you no protection at all. Recording the wash date is what lets you show the register was checked, and how recently.

For lists you hold over time, the DNC Check endpoint and Insiight both re-wash on a schedule, so the file stays current between campaigns instead of quietly ageing out of compliance.

It answers the consent half of the question, which is the half that cannot be fixed retrospectively. Every contact is opt-in confirmed with its source and date recorded, and phone records are DNC-washed before delivery.

The rest stays with you. The Spam Act also requires that your message accurately identifies the sender and includes a functional unsubscribe facility, and that opt-outs are honoured promptly. Those are properties of your campaign, not of the list.

A clean list with a non-compliant message is still a breach. But a compliant message sent to a list whose consent you cannot substantiate is the more common and more expensive failure.

Location, demographics and household attributes: the dimensions that determine whether an offer fits the person receiving it.

Filtering, counting and previewing are free. You can build a segment, see how many records it returns, narrow it, and count again as many times as you like before committing to anything. Nothing is charged until you download.

That is deliberate: it means audience sizing happens before the budget conversation, not after it.

Per downloaded record. There is no minimum list purchase and no subscription to maintain.

Because filtering and counting cost nothing, you can size an audience precisely and then download only the records you intend to use. No buying a block of 50,000 because that was the smallest package available and working out later that only 12,000 of them fit the offer.

Not indefinitely, and that is a data problem, not a licensing one. People move, change numbers and register on the Do Not Call list continuously, so a file that was accurate at download begins decaying the day you receive it.

Insiight washes purchased lists on a schedule so they stay current between campaigns, re-validating contact points and re-checking DNC status.

That is generally cheaper than replacing the list outright, and considerably safer than calling it as-is on the assumption that the original wash still holds.

Yes, through three endpoint groups:

• Marketing Contact Lookup — opt-in records retrieved by contact point
• Phone — DNC status checks, per record
• Address — validation and autocomplete

This suits teams who would rather check a record at the moment of use than work from a downloaded file: washing DNC status immediately before a dialler session, for example, instead of relying on the wash date that applied at delivery.