CAVEMANAIQ all four storylines
storyline 01 · the first click

Should we switch the social ads off?

GA
ME
TM
G4
SC
MC
DM
DB
01
01 · one console

Seven dashboards to one console

the console · all seven servers, one login
ask anything…
7 servers docked · each holding its own login
Meta, Google Ads and GA4 each answer confidently, and no two answers agree · each one sees only its own half of the journey.
02 · you ask · on the record

The question is the whole interface

“ Our social ads get clicks and no sales. Should we switch them off?
you
the console
on the record
7 servers docked · each holding its own login
handed to the agent, word for word · nothing runs unasked
▸ we write the request down before we send it
▸ and the answer when it comes back
Nobody had ever compared the platform totals with the shop’s own orders.

What had to be settled before any number was believed

Two platforms reporting the same two weeks will always disagree.

what had to be settled first

one window, agreed firstTwo weeks, one timezone, one definition of a completed order.
first click or last clickSeeing a purchase is not causing one.
what each campaign was built to sendRead from the campaigns themselves, before counting anything.
whose number is itThree different quantities. Never averaged, never swapped.
03 · dispatch

The agent decides who to ask

THE MCP FLEET
THE PLATFORMS · reached by API, not by login
the agent
reasoning: what do I need, in what order?
DB the database 01
the orders that actually happened
ME Meta 02
what social entered against those orders
GA Google Ads 03
what search entered, same window
G4 GA4 04
how each session arrived
03
GA
Ads
spend · conversions
Google Ads API
your ad account · Google’s cloud
02
ME
Meta
spend · conversions
Meta Marketing API
your ad account · Meta’s cloud
TM
GTM
stands down
GTM API
the tag container running on your site
04
G4
GA4
events · funnels
GA4 Data + Admin APIs
your site’s events · browser + server
SC
GSC
stands down
Search Console API
how Google search sees your site
MC
MC
stands down
Merchant Center API
your product feed · Google’s cloud
DM
DM
stands down
audience · conversion upload
your audience lists · Google’s cloud
YOUR OWN RECORDS · READ THROUGH THE DATABASE MCP, NOT A VENDOR CLOUD
01
DB
the database
your own records
the database · your own records
your own order records
Both platforms are asked what they entered against the order.
data plane · no human · always running

THE DATA PLANE · runs whether or not anyone is watching
a shopper · not you
the site · code running
every visit writes the record · no one at the wheel
Google’s servers · ads runtime
no change here
Meta’s servers · ads runtime
no change here
04 · gather

The evidence converges on the session

ME
Meta
claimed conversions
GA
Ads
claimed conversions
G4
GA4
how each session arrived
DB
the database
your own order records
one payload · assembling
Meta
claimed conversions
Ads
claimed conversions
GA4
how each session arrived
the database
your own order records
all 4 answers in · ready to combine
The same purchases, claimed twice.
05 · the readout

Ask where the people who left actually went

what had to be settled first
Two platforms reporting the same two weeks will always disagree.
one window, agreed firstTwo weeks, one timezone, one definition of a completed order.
first click or last clickSeeing a purchase is not causing one.
what each campaign was built to sendRead from the campaigns themselves, before counting anything.
whose number is itThree different quantities. Never averaged, never swapped.
the attribution finding
built from ME GA G4 DB
the claimboth platforms counted the same orders · each reporting only its own half
what happenedthe social advertisement brought them in, they left without buying, they returned through search and bought there
the trapswitching social off would have switched off the demand that search was harvesting
Retune the social campaigns to the job they are already doing · qualified arrivals, not immediate purchases.
Not what did social convert, which has a known and useless answer.
06 · the loop closes

The loop closes

you, again
the attribution finding · yours
One reconstructed order, end to end
first recorded visit through a social advertisement, no purchase, later arrival through a search shopping advertisement, sale completed there.
fleet: reads only · the decision stayed with a person
Nothing was paused automatically.
07 · how it ended

How it ended

how it ended

a conclusion was corrected
Exact credit split: unknown.
Each campaign type sends a different amount of detail by design, so the record is full where the sender was generous and thin where it was not.
The social campaign names its creative in words but sends no advertisement number · a gap at the sending end, not the receiving one.
A correct field in a database is never proof of a complete record.
No lift is claimed · two things moved at once.