Home/Audiences/Platform rules
Audiences

LinkedIn audience rules to design around

LinkedIn audience rules set minimum sizes, upload limits, delays and access conditions. None of them is a problem if the plan accounts for them early. Here is each rule and what it changes in practice.

Timing at a glance

The clock on an audience

Two scales: hours after an upload, and days while an audience sits in the account.

Hours after upload

The first match is the longest wait. Later updates are shorter.

First match: up to 48 h Update: about 24 h Upload 24 h 48 h

Days in the account

An audience that sits unused is archived, then expires.

Expires In use Archived if unused Created 30 days 90 days
300matched members needed to run
300,000rows allowed in one CSV upload, at most
48hours at most to the first match
24hours, about, for a list update to apply

Four groups, each with a consequence

Size

An audience needs at least 300 matched members to run. Under that, the count shows 0.

A 0 can mean too narrow, not empty. We count a niche before building it, and widen it or join a second list with OR when it falls short.

A CSV upload holds up to 300,000 rows.

Very large lists are split into several files under the limit.

Timing

The first match takes up to 48 h.

Upload ahead of the launch date. A same-day launch on a new list is a risk we avoid.

Updates take about 24 h. Streaming keeps a live segment near real time.

Changes to a list are timed a day before they need to be in effect. Segments that change often are streamed.

Audiences unused for 30 days are archived and expire after 90.

Build close to launch and keep the source list, so an archived or expired audience is rebuilt from the list and not from scratch.

Matching

Contact lists match on hashed email, plus name, title, company and country. Company lists match on domain.

Lists are prepared in the exact upload format, with the supported fields filled wherever we have them. Company files need clean domains and no personal data.

Members who opted out of third-party data are removed from the final count.

The audience is always smaller than the list that went in. Plans are made on the matched count, not on the file size.

LinkedIn does not publish a match rate.

We test a small sample of every contact list before scaling it, and size each list on its own.

Access

Building audiences by code needs the Advertising API plus Matched Audiences approval.

Access is a first item on the project plan, so it is settled before a launch date is set.

Rate limits apply per app and per member, and reset daily at 00:00 UTC.

Large batches of audience changes are spread over days instead of pushed in one run.

What a launch plan looks like

These rules set the order of work. A campaign built around them has no waiting on launch day.

Count first

Check that the niche clears the 300 member minimum before building anything.

Upload early

Leave room for the first match, up to 48 h, and for a small sample test on contact lists.

Launch while in use

Start the campaign soon after the audience is ready so it never sits idle for 30 days.

Refresh with lead time

Allow about 24 h for changes, or stream a segment that moves often.

Rebuild from the source list

If an audience is archived or expires after 90 days, it is recreated from the list we kept.

Questions about LinkedIn audience rules

Why does my audience show 0?

The count shows 0 when the audience is under 300 matched members. It does not mean the niche is empty. The usual fixes are fewer filters, a wider signal, or a second list joined with OR.

Can I know the match rate before I pay for ads?

LinkedIn does not publish one. We test a small sample of the contact list first and report what came back. Company lists match on domain.

Who handles the access approval?

Tell us what you already have on the ad account when you contact us. We plan the access step first, so it never blocks a launch date.

Plan around the rules, not into them

Send us the niche. We count it, test the match and give you a launch order that respects every limit above.