Every dealer group sits on the best targeting data in the market: who actually bought, and when. Most of it lives in a DMS export on a shared drive. The ad platforms never see it, and the agency that asked for it last quarter is still "working on the upload."
That gap is the whole story. Platforms bid on audiences they can model, and the only audience that proves a dealer's market is the one that already paid the dealer. This piece covers what a sold-log can feed, what it cannot, and where AUTONOMi's own build is still unfinished.
What Is a Sold-Log, and Why Does the Ad Platform Never See It?
A sold-log is the list of units a store has delivered. A customer list is the buyers and service visitors with their contact details. Often it is the same export. Neither was built for advertising, so neither leaves the store without someone deciding it should.
Agencies are the usual bottleneck. They request the file in the onboarding kickoff, receive it, and then it sits. Nobody owns the upload, nobody is measured on it, and the retainer invoice does not change either way. The result is a dealer paying to find buyers while the best list of buyers is excluded from the targeting.
This is the same argument we made about targeting in-market buyers from the sold-log and the lot: the signal is already inside the store. The question is whether anything reads it.
How can dealer groups activate first-party data in AI search and advertising?
Split the question in two, because the two halves behave differently.
In advertising, activation is mechanical. A customer list is normalized, hashed, uploaded to a platform's customer-match endpoint, and matched against the platform's own users. AEGIS keeps a customer list's contacts normalized and SHA-256-hashed, the form every platform's customer-match upload takes, as the dealer's first-party audience asset.✓ Nov 17 That is a real, shipping path.
In AI search, there is no equivalent upload. No answer engine accepts a customer file. What a dealer controls there is the quality of the pages the engines read, which is a content and data-hygiene problem, not an audience problem. Treat the two separately and be suspicious of any vendor who sells them as one product.
So the honest scope of this article is advertising. The customer list powers three jobs: exclude people who just bought, retarget service and equity customers, and seed prospecting from real purchasers.
Why Does the Purpose of the List Matter More Than the File?
A single list can mean four different things. Sold customers should be excluded from conquest and used as a seed. Service customers are a retention audience. Leads who never bought are a retargeting audience and must never be treated as customers. Mix them and the exclusion hits prospects while the seed teaches the platform to find people who only browse.

Every dataset upload in AUTONOMi requires the dealer to say what the list is for: sold customers, service customers, sales and service customers, leads, or other with a mandatory context line.✓ Nov 17 Claude resolves "other" and lists that arrive without a word, and the document records that the purpose was inferred.
The sold-versus-service problem is the common trap. On a sales and service list, Claude finds the column that tells a sale from a service visit, and a contact that nothing narrows is kept as both a buyer and a service customer, never service-only. That default errs toward not losing a buyer.
Consent belongs in this conversation too. A list is only as usable as the record of why the people on it agreed to be contacted. We covered the exposure in the GM data settlement and what it means for a dealer's own list. Customer match is not texting, but provenance is the same question.
What Does AEGIS Build From One Upload?
AEGIS cuts the pool by the purpose the dealer set for the upload (sold, service, sales and service, leads, or other) into segments. Those segments are all customers, sales customers, new, CPO and used buyers, buyers in the last 12 months where the list says what they bought and when, service customers, and prospects. Prospects are a retargeting audience only, never a customer audience. Each segment becomes a customer-list audience on each connected platform: Meta, Google, TikTok and Microsoft.
Each segment becomes a customer-list audience on each connected platform.On Meta, each segment becomes a customer-file Custom Audience, plus a 1% Lookalike once Meta matches at least 100 contacts.✓ Nov 17 On Google, it becomes a Customer Match list, plus a Demand Gen Lookalike segment once Google matches at least 1,000, which is Google's replacement for the retired similar audiences.✓ Nov 17
TikTok gets a Customer File audience, with a Lookalike once at least 1,000 are matched.✓ Nov 17 Microsoft Advertising gets a Customer Match list; Microsoft models its own Similar Audiences, and its API cannot create one.✓ Nov 17
Those match thresholds matter for a small store. A single rooftop with a short buyer list may not clear 1,000 matched contacts on Google or TikTok, and the lookalike simply will not exist yet. That is a platform rule, not a bug. A dealer group uploading one list across many rooftops clears it sooner.
The segment names also matter for the next question. A dealer who sees "buyers in the last 12 months" as a built audience can ask for it to be excluded from a conquest campaign, instead of hoping an agency remembers.
What Is Wired Today, and What Is Not?
This is where most vendors blur the line, so here it is plainly.

Automatic attachment of these audiences to Google, TikTok and Microsoft ad groups at deploy time is not wired yet.✓ Nov 17 The Meta plan composer wires them today; the other three platforms expose the audiences to the composer and attach them as each platform's build lane is extended.✓ Nov 17
In practice: the audiences are built and matched on every connected platform. On Meta, they are used in the campaign plan, for exclusion and for lookalike prospecting. On the others, the audience exists and is visible to the composer, but a person should not assume every Google, TikTok or Microsoft ad group is already excluding buyers. That attachment step is the open work.
We would rather print that gap than have a dealer discover it in a report. An audience that is built but not attached does nothing for spend, and a group that believes otherwise will misread its own results.
How Do You Know the Audience Is Doing Anything?
Measurement has to be read the way the platform reports it. A customer-match audience shows its matched size, and a campaign that uses it shows spend and conversions against that audience. Those are platform-reported figures, and they are not units sold. The CRM or DMS holds the sale.
A ledger with one row per platform and segment, holding status, sizes and the platform's own ids, backs the dealer's Your Audiences panel, the Vault, and the agents' query tool. That ledger is how a controller checks that a list went where it was supposed to go.
Do not stretch it into an attribution claim it cannot carry. The cleaner way to connect audience spend to leads is the tagging discipline in carrying the click's own tag into the lead, with the CRM taking over where the ad platform stops seeing.
The AUTONOMi Approach to First-Party Audiences
When a dealer uploads a historical sold-log, AEGIS recognizes it as data rather than instructions, and Claude maps the file's columns onto a canonical sales schema, whatever format the DMS exports.✓ Nov 17 AEGIS classifies two questions independently: is the file a sold-log, and is it a customer list. A file that is both feeds both sales history and the contact store.✓ Nov 17
Audience building runs automatically after every customer-list upload and on a daily audience backfill, and every ad build can refresh it.✓ Nov 17 The Strategic Advisor and every channel composer see the asset in aggregate, as counts, identifier coverage, desk and date span, never an individual contact, and propose its use: lookalike seeds, recent-buyer exclusions, and service and equity re-marketing.✓ Nov 17
The ad accounts the audiences are built in are dealer-owned; AEGIS operates with delegated OAuth access, and the dealer can revoke it at any time. That is the ownership model. We make no claim here about what happens to any audience after access is revoked, because the factsheet that governs this piece does not describe it. Ask that question of any vendor, including us, and get the answer in writing.
The same sold-log also feeds merchandising, which then reasons over actual sales alongside live inventory: sold velocity per model and what to order more of.✓ Nov 17 One upload serves the advertising and the stocking decision.
Who Loses When the List Finally Gets Uploaded?
The agency that asks for the list and never uploads it. Its value was the gatekeeping: holding the one file that makes targeting specific, and keeping the dealer from seeing whether it was used. When a dealer can upload the file once, name its purpose, and read a ledger of what each platform received, the retainer has to justify itself on something else.
The next step for a group is small. Pull the sold-log and the customer export from your DMS, decide what each list is for, and put it in front of a system that builds the audiences and shows you the ledger. If you want to sign up and upload your first sold-log through AUTONOMi, the Meta audiences are the part that works end to end today, and the other three platforms follow as their build lanes are extended.



