Free guide

Custom audience GDPR basics for UK advertisers

Uploading a customer list to Meta, LinkedIn or TikTok to build a custom audience means sharing personal data with an ad platform. Under UK GDPR that needs a lawful basis, clear information for the people on the list and respect for their choices. This guide explains the custom audience GDPR questions UK advertisers should answer before uploading, in plain language. It is general information, not legal advice.

Last verified 22 September 2026 · 1 live platform fact · How this is maintained


Custom audiences are one of the most effective tools in paid social. They let you show ads to existing customers, exclude them from acquisition campaigns or build lookalikes from your best buyers. Because they rely on personal data such as email addresses and phone numbers, they also sit squarely within data protection law. The Academy's glossary explains custom audience and GDPR.

What happens when you upload a list

Ad platforms typically hash the list, turning each email or phone number into a scrambled code, then match those codes against their own users. Matched people join the audience; unmatched data is discarded. Hashing reduces risk, but it does not take the activity outside data protection law, because the purpose is still to identify and target individuals.

The questions to answer first

QuestionWhy it matters
What is our lawful basis?Every use of personal data needs one
Did our privacy notice explain this use?People must be told how their data is used
Can people object or opt out?Rights to object apply, especially to marketing
Are we sending only what is needed?Data minimisation
How long will the audience be kept?Storage limitation
What do the platform's terms say?Roles and responsibilities

Lawful basis

Most UK businesses rely on either consent or legitimate interests for custom audiences. Legitimate interests can be appropriate for marketing to existing customers when people would reasonably expect it and their rights are respected, but it needs a documented assessment balancing your interests against theirs. Consent is needed in some situations, for example where electronic marketing rules or your own earlier promises require it. The ICO publishes guidance on direct marketing and on targeting, which is the place to check specifics. The Academy's glossary explains the ICO.

Privacy notices

Your privacy notice should say that you may share contact details with advertising platforms to show relevant ads or to exclude existing customers, name the kinds of platforms involved and explain how to object. Adding this after the fact does not cover data collected under a notice that never mentioned it, so review older lists carefully.

Respecting opt-outs

People who have unsubscribed from marketing or objected to profiling should be removed from lists before upload. Build suppression into the process, so every refresh of an audience strips out anyone who has opted out. Using an opt-out list as an exclusion audience is a common pattern, but check it fits your notices and records.

Electronic marketing rules

PECR governs electronic marketing such as emails and texts, and the rules on cookies and similar technologies that power pixel-based audiences. Website custom audiences built from a pixel depend on cookie consent: if visitors refuse marketing cookies, the pixel should not fire for them. The Academy's guide to cookie consent for ad pixels covers this in detail, and the glossary explains PECR.

Minimising and securing data

Upload only the fields needed for matching, usually email and phone, rather than whole customer records. Keep upload files out of shared drives and delete local copies afterwards. Limit who in the team can create and download audiences, and use two-factor authentication on ad accounts.

Retention and refresh

Old lists drift out of date and may include people who no longer expect to hear from you. Set a retention period for custom audiences, refresh them from the current customer database rather than ancient exports and delete audiences you no longer use.

Platform terms and roles

Each platform has custom audience terms that set out who is responsible for what. Typically you confirm that you have the right to share the data and the platform processes it to create the audience. Read the terms for each platform you use and keep a record that you accepted them.

Building first-party audiences in other ways

Lists are not the only route to reaching people who know you. Engagement audiences built from people who interacted with your posts, videos or lead forms on the platform itself rely on platform data rather than files you upload. Communities also help: group posts often outperform Page posts for organic reach; community-building channel✓, which can keep existing customers close without uploading any list.

Agencies and freelancers

When an agency or freelancer runs ads for a client, the client usually remains responsible for the customer data. Agree in writing who uploads lists, where files are stored and how opt-outs reach the person managing audiences. Avoid emailing customer files; use the client's own ad account and access controls instead.

Record keeping

Document your lawful basis, any legitimate interests assessment, the privacy notice wording in force when data was collected, the suppression process and when audiences were created and deleted. Good records make it easier to answer questions from customers, clients or the ICO.

A worked example

A subscription box company wants to exclude current subscribers from its acquisition ads. It checks its privacy notice, which already mentions sharing hashed contact details with advertising platforms, completes a short legitimate interests assessment and removes anyone who has opted out of marketing. It uploads only email addresses, refreshes the exclusion audience monthly from the live database and deletes the local file after each upload.

Common mistakes

Learning the rules

The Academy's legal and ethical module in the third level covers UK GDPR, PECR and advertising rules for social media, and the paid social module covers audiences. Content on this page is general information rather than legal advice. The free assessment shows where you would start.

Common questions

Is it legal to upload customer lists to Facebook in the UK?

It can be, if you have a lawful basis, your privacy notice told people their details may be shared with ad platforms, opt-outs are respected and you follow the platform's terms. Check ICO guidance for specifics.

Does hashing make custom audiences GDPR compliant?

Hashing reduces risk but does not take the activity outside UK GDPR, because the purpose is still to match and target individuals. You still need a lawful basis and transparency.

Do website custom audiences need cookie consent?

Yes. Pixel-based audiences rely on cookies or similar technology, so under PECR the pixel should only fire for visitors who have consented to marketing cookies.

Go deeper

Modules that teach this properly

Related guides

All guides on paid social →

Next step

Find out where you actually stand

A five-minute placement assessment scores you across six skill areas and builds a path through all 28 modules — skipping whatever you already know. No card needed.

Take the free assessment