There is a question dealers keep typing into search that looks like a vocabulary problem: what is the actual difference between digital sales and digital marketing? Autonomi published a piece this week arguing that the question is not about vocabulary at all. It is about who owns the data sitting between the two teams, and the honest answer at most stores is a name that is not on the building.
The marketing side owns the ad accounts and the agency relationship. The sales side owns the CRM. Whoever built the website owns the pixel. Nobody owns the number that connects them: cost per delivered unit, by channel, verified against what actually closed. That number should be the most argued-over line on the monthly summary. At most dealerships it is either missing or a polite approximation.
Disclosure before the argument, because it is load-bearing: Floof Digital was the platform engineering partner on the Autonomi build. We architected and hardened the system this post describes. So take the enthusiasm with the appropriate salt, and take the technical claims with more confidence than usual, because we are not reading a press release about this one. We wrote the access model.
The distinction the whole thing turns on
Access and ownership feel like the same thing right up until the relationship ends. They are not the same thing, and the difference is decided by one boring historical fact: who created the account.
On Google, an agency's manager account that is granted partner access to a dealer-owned Ads account changes nothing about ownership. The dealer keeps the data and can unlink the agency whenever it likes. But when the agency created the account under its own manager account, which is an extremely common setup, ownership runs upward into the agency's infrastructure rather than sitting with the dealer. Meta works the same way. A dealership that owns its Business Manager and grants partner access keeps its pixel history and its audiences if the relationship ends. A dealership whose pixel lives inside the agency's Business Manager can find itself starting from zero.
Same story for the GA4 property, and the same story for the Google Tag Manager container. A container installed by an agency under the agency's account is the agency's container no matter whose website it fires on. Every conversion event configured in it, every audience built from it, every attribution window calibrated against it lives in infrastructure the dealer does not control. Transferring it is usually possible. Most dealers have never asked, because most dealers have never been told the question exists.
Being listed as a user on an account someone else administers is not ownership. It is access, and access is contingent on a relationship continuing.
What is actually in the account
Here is the part that turns an administrative footnote into a balance-sheet item. The thing accumulating inside those accounts is not campaign settings. It is compounding capital.
Years of audience signal. Pixel-collected behavior from your own website. Lookalike seed populations built from your actual buyers. Quality Score history on Search. Smart bidding that has spent months learning your market, your seasonality, your inventory mix. Product feed reputation in Merchant Center. None of that lives in the relationship. All of it lives in the account.
Which means the exit is where the invoice arrives. When an agency leaves and the dealer never owned the account, the history leaves too, and the next agency starts from a cold account with no learning and no audiences. Every dollar of media that built those signals bought an asset that just walked out the door. The replacement cost does not appear anywhere as a line item. It appears as higher cost per lead and worse performance for the next six to twelve months, absorbed quietly as normal variation and never traced back to its actual cause.
Autonomi makes the sharpest version of this point about acquisitions. Buy a rooftop, and if the pixel history and account signals do not come with it, you are paying to rebuild them in the acquired store's marketing budget for the better part of a year. That cost was never on the deal sheet. It was never modeled. It is just there, in the CPLs, for months.
Why the relationship cannot be audited
The next consequence is structural, and it needs stating carefully because it is not an accusation.
If the ad accounts live in the agency's Business Manager and the analytics property was created by the agency's team, then every number the agency reports is produced from inside the agency's own infrastructure. There is no independent source of truth available to the dealer. That is not a claim that agencies lie. Plenty are excellent and would hand you everything tomorrow if you asked. It is a description of an access model in which the dealer cannot verify anything without asking the party being verified to go get it.
Any auditor would recognize this instantly, and the same defect shows up in the reporting itself. The platform dashboard shows every click and form fill the pixel fired. The sales log shows every conversation that reached a human. Between those two records sits a gap that can be enormous in both directions: leads the platform claimed that never got logged, and sales that closed from channels the platform never got credit for. Meanwhile Safari's tracking prevention and ordinary script blockers routinely suppress client-side pixels before they fire, so the form gets submitted and the conversion never gets recorded. Marketing's numbers read better than reality. Sales' complaints about lead quality read louder than the data supports. Both teams are telling the truth about their own evidence set. Neither has the other's.
And the number that would settle it cannot be produced by the analytics platform. GA4 is built to answer the click question, not the margin question. It has no native access to cost of goods, front-end gross, or deal-level data in the DMS. Connecting a dollar of spend to whether the resulting sale was margin-positive requires a join to systems outside GA4 entirely. That join is the whole ballgame, and it is exactly the thing nobody owns. We have written before about what happens when the reporting layer is telling you a comfortable story. This is the version where the comfort is architectural.
What we built, and why it is designed this way
Floof was engaged on the Autonomi build as the platform engineering and strategic partner: architecture, multi-cloud delivery, data and identity, security and compliance. An intense, focused build. Which means we were in the room for the decision this article is really about, and it is worth explaining what that decision looked like from the engineering side.
You can promise a client that their data is theirs. That is a policy. Policies are enforced by goodwill and survive exactly as long as the relationship does. Or you can build the system so that the promise is a structural property and there is no mechanism by which it could be otherwise. That is architecture, and it holds after everyone who made the promise has moved on.
The published model is the second kind. Every ad account, GA4 property, GTM container, Business Manager asset and Merchant Center ID that the platform operates on belongs to the dealer. AEGIS reaches them through OAuth with delegated credentials, which the dealer can revoke at any moment. It reads and writes through the platform APIs rather than keeping a shadow copy inside Autonomi's own infrastructure. The consequence is the cleanest test of the whole design: when a dealer offboards, there is no data migration, because there is nothing to migrate. The accounts were always theirs.
Two supporting pieces matter as much. Every allocation decision, campaign change and budget adjustment is hash-chained into a dealer-readable audit trail through AXIOM, the governance layer, so the dealer can read what was done and when without asking the operator to pull a report. And the measurement layer is provisioned as server-side tagging infrastructure that belongs to the dealer, forwarding conversions server to server and deduplicating against the client-side events, which recovers the conversions that browser privacy controls suppress. Note the ownership point, because it is easy to skip: server-side infrastructure deployed by a vendor recovers the conversion but leaves the dealer just as unable to audit it. The recovery only counts if the pipe is yours.
This is also why the hybrid request that dealer groups keep making actually works here. Keep one channel in-house, hand the rest over, flip a switch to take a channel back. That is only clean when the account was the dealer's the entire time. You cannot gracefully hand back something you were holding in your own name. The full engagement is written up on our Floof x Autonomi case study.
The playbook, for anyone who is not a dealer
Strip the automotive vocabulary and this is a governance problem that belongs to almost every business buying media through somebody else. DMAIC at the strategic layer, disciplined delivery underneath. Six things worth doing this quarter, in order.
Run the ownership inventory. One spreadsheet. Every ad account, analytics property, tag container, business manager, merchant feed and tagging server. For each: who created it, who is the owner of record, whose payment method is attached, and who would still have it if the current vendor relationship ended on Friday. Most of the value of this exercise is delivered by the number of cells you cannot fill in.
Learn the difference between admin and owner on each platform, specifically. They are genuinely different objects with different consequences, and "we have full access" is the sentence people say right before discovering they do not have the thing they thought they had. Check the actual ownership record on the platform, not the reassurance in the email.
Take back the container and the property first. If you can only move one thing, move the tag container and the analytics property. They are the cheapest to transfer, they govern what gets collected everywhere else, and they are where the reconstruction cost is highest if you lose them.
Put the tagging server in your own infrastructure. Server-side tagging is the right answer to browser-level suppression, and it is only half an answer if the pipe carrying your conversions belongs to the party reporting on them.
Name the one number and give it an owner. Cost per delivered unit, or whatever your equivalent closed-revenue number is, defined jointly by marketing and sales, joined to the system where deals actually close, with one named human accountable for it being correct. Every version of this failure that we have watched traces back to a metric that was everybody's business and nobody's job.
Write ownership into the contract at the start, not at the divorce. The clause is short and nobody objects to it during onboarding: accounts are created in the client's name, the client is owner of record, vendor access is delegated and revocable, and all assets survive termination. Negotiating this while you are leaving is a very different conversation from including it while you are arriving.
Our position
Vendors should be replaceable. Data should not be. Almost every expensive marketing failure we get called into starts with an organization that had those two backwards: a data layer that could only be read through a vendor, and a vendor that had therefore become impossible to replace.
The uncomfortable implication of the Autonomi piece is that this arrangement does not require anyone to behave badly. No villain is necessary. Accounts get created by whoever is standing there on day one, ownership is never revisited because nothing is visibly broken, and the compounding value quietly accrues in someone else's name for years. The bill only arrives at the exit, which is the one moment nobody is planning for.
So the fix is not a better dashboard or a smarter analytics consultant. It is a decision about where institutional memory lives and who can act on it, enforced in the structure rather than promised in a relationship. That is an operations decision wearing a technology costume, and it is the kind we take. We built it that way on Autonomi because when you are the engineer holding the pen, you get exactly one chance to decide whose name goes on the account.
Your agency is not going to steal your account history. It is just going to leave with it, and you will pay to build it again.