how a call runs
what it reaches
Data Manager API
server to server · straight to the platform’s API
access granted once · OAuth · scoped to this account
no browser session · no password sharing · no scraping
what you get
personal data never travels raw · Personal details are turned into fingerprints on your machine before anything leaves it. They are never written to any record, and the tool refuses outright if it is handed raw data.
a blank list means nobody · An empty list of permitted accounts denies everything rather than allowing everything, and a blocked account stays blocked even if it also appears as permitted. A wrong configuration reaches nothing.
undo is deny by default · An upload is only undone if it was recorded as undoable when it was made. Nothing is quietly rolled back, and nothing personal is kept just in case.
| tool | type of access | what it does | why it exists |
|---|---|---|---|
| audiences.list | reads only | lists every audience already uploaded | what has already been sent, before anything is sent again |
| matches.status | reads only | shows how much of each list the platform matched | how much of a list the platform could use |
| consent.check | reads only | reads what each record may be used for | what each record may be used for, before it travels |
| audience.upload | adds new | hashes a list on your machine | a list reaches the platform only after you approve, and only hashed |
| audience.append | adds new | adds to a live list once you approve | grows a live list without rebuilding it, on your approval |
| audience.remove | changes or removes | takes a list down | takes a list out of use in one deliberate step |
covers
13 of the 22 methods in the Data Manager API v1, in full: ingestion, marketing data insights, user lists and partner links. Not covered: the two user-list licence programmes, 9 methods, which need a design and an entitlement the work does not have.
how it operates · alone, or with the rest of the fleet
alone
lists · match rates · consent in one view
01
you ask · “Sync last quarter’s buyers to the ads platforms.”
02
it picks · two reads first · the segment itself, and what is already uploaded
03
comes back · the list, hashed on your machine · nothing sent yet
04
lands · your yes releases one upload through the gates · receipt and undo attached
with GA4
GA4 knows what visitors actually did. Read together, a list is built from real behaviour on your site, not from a guess about who might be interested, before it is sent anywhere.
01
you ask · “Build a list of people who reached checkout and left.”
02
it picks · the funnel read in GA4 first, then the audience and consent reads here · reads only until you approve
03
comes back · the segment defined from real behaviour on the site, and what each record may be used for
04
lands · the list, hashed on your machine · nothing sent until your yes releases one upload through the gates
with Google Ads and Meta
The advertising servers are where a list goes to work. Read together, a list that was hashed and approved here is followed to the audiences it feeds on each platform, and the match rate each one reports comes back in the same readout.
01
you ask · “Did last week’s list reach both platforms, and how much of it matched?”
02
it picks · the audiences read here, then the audience-status read on Google Ads and on Meta · reads only
03
comes back · what was uploaded, where it landed, and the match each platform reports for it
04
lands · one readout for one list across both platforms · match rates as reported, never as proven revenue