Customer Match can use first-party customer information to reach or exclude audiences, subject to platform rules and applicable privacy requirements. A list upload does not guarantee a usable audience, and technical acceptance does not establish that the data was collected or shared appropriately.
Confirm permitted use and list purpose
Define whether the list is for targeting, observation, or suppression and identify the source of each record. Review the organization’s privacy notices, consent or other applicable basis, contracts, and the platform’s current policy with the responsible privacy owner before activation.
Minimize the data included and limit access to people who need to prepare or manage the audience. Do not repurpose service or sensitive information for advertising without explicit review.
- Document source, purpose, owner, and refresh cadence.
- Check opt-outs and suppression before upload.
- Review current platform policy and regional requirements.
Validate identifiers and audience handling
Normalize permitted identifiers consistently and remove invalid or duplicate records. Keep a secure source-to-upload process and avoid placing raw customer data in shared campaign documents. Follow the platform’s current hashing, formatting, and upload requirements rather than relying on an old template.
Check the platform’s audience status and size indicators after processing. A small or unmatched list can limit delivery; do not compensate by relaxing privacy rules or adding unrelated records.
- Test a controlled sample before a large refresh.
- Record processing errors and match outcomes.
- Set an appropriate minimum audience and access rule.
Maintain accuracy and remove stale records
Refresh the audience on a schedule that reflects how quickly customer status changes. Remove people who opt out or no longer meet the stated purpose, and validate that updates reach the destination. Keep a log of upload dates, source versions, and exclusions.
Review performance against the intended objective, but do not infer a causal lift from platform reporting alone. Compare with a suitable baseline or test where feasible, and document measurement limitations.
- Track refresh success and suppression timing.
- Assign an owner for failed updates.
- Review audience use and retention at regular intervals.
How did this article land?
Choose one reaction. You can change it anytime.