Fill in the link, rules, and rows below with your own. Examples use Doughnut Labs, a SaaS company that sells disruptive Doughnut Technology.
Why lists are not customer profiles
These are two different things, and the customer profile library is explicit that a profile “describes a type of customer, not a single named person or account.”
Both directions are legitimate. A profile can generate a list, which is what define a customer profile describes. A list can also arrive from sales, from an event, or from a data provider with no profile behind it, and that list still needs a home, an owner, and an expiry. This store is for the file either way.
A list that arrived without a profile behind it is worth writing a profile for eventually, because a profile is what lets you rebuild the list next quarter. It is not a precondition for launching. Record the selection criteria in the register below and move.
Where it is
Handling rules
Set these once with whoever owns data protection at your company, then follow them per list.Upload templates
Build every list to the template for the platform before uploading it. A list assembled ad hoc matches at a lower rate and fails in ways that only show up after the file is in.
Each download has the header row and one example row with fake data. Delete the example row before you add your own. The mobile ID file has the header row only.
The register
One row per list. Metadata only. Identity and provenance. Where the list came from and who chose what went in it.
Size and expiry. How big it is, where it runs, and when it stops being true.
Match counts and match rates stay in the ad platform. Check them there before each refresh.
Naming
Every file follows the file naming conventions, using the same four-part shape as a customer profile:LIST_q2-target-accounts_20260401_v01.csv
The as-of date is doing real work here. It is what the ad set / ad group / variant naming conventions date identifier refers to, and it is why an audience built in April is comparable to itself and not to the same list refreshed in October.
Before you upload
1
Check the row count against the platform floor
Every platform has a minimum, and a list below it cannot serve. LinkedIn needs at least 300 rows to upload and at least 300 matched companies to run, recommending 1,000. Check the template for your platform before promising a launch date.
2
Record the provenance while the supplier is still in the room
Who picked these accounts, on what criteria, as of when. This is the field that becomes unrecoverable fastest, because the person who knows moves on to the next quarter.
3
Upload and check the match in the platform before anything else is briefed
Matching takes time and can fail the campaign outright. Doing it first means a short list is a scheduling problem, not a write-off of finished creative.
4
Set the refresh date and the retention date
Both, at upload. A list with no refresh date ages silently; a list with no retention date is a data protection problem waiting to be found by somebody else.
When a list changes mid-flight
Treat the audience the same way you treat attribution and bid strategy: decided at brief stage, left alone after launch. On account-based campaigns the audience is the campaign. Adding forty accounts in week three changes what the campaign is, and the results from before and after cannot be compared. Nothing in the platform flags this, and the spend line looks continuous.Related resources
- Asset directory Every location in one index.
- Customer profile library The profiles that describe types of buyer, not named accounts.
- Define a customer profile The path from a profile to an exported list.
- File naming conventions The convention every file here follows.
- LinkedIn company list CSV template The account-based upload format.
- Launching a LinkedIn campaign Where the match check gates the build.
MCP wiring
MCP wiring
Type: library
Domains: tracking, legal, linkedin, meta
Provides:
Uses:
Best for: channel: linkedin, metaAsks, in order:
Domains: tracking, legal, linkedin, meta
Provides:
library:audience-listUses:
customer-profile, legal-triggers, naming-conventionBest for: channel: linkedin, metaAsks, in order:
- Which platform? Options:
options:list-upload-template. Skip when: campaign brief names it. - Who supplied it and on what criteria, as of when? Options: your answer. Skip when: recorded.
- Refresh and retention dates? Options: your answer. Skip when: handling rules set defaults.
Get the complete Marketing OS
Subscribe to Snow Doughnut, our free weekly newsletter, and get the Notion workspace where you do the work: tasks, a marketing calendar, name generators, briefs, and more.
Have us run it for you
We implement this system, use it to help you grow and scale, then hand it all off to you when you’re ready.