HUX-L0 — Tracking foundation

Part 1 — the plain-english view

Before anything watches the ads, the ads must be measurable.

What it watches

Nothing — it's plumbing. It installs: the Meta pixel + server-side events, GA4 analytics, Google Ads conversion import, and Search Console verification
Plus offline-to-online bridges: promo codes and QR codes so showroom sales can credit online ads

When & how it speaks

It doesn't. Once done, every marketing loop downstream speaks with real conversion numbers instead of guesses.

Why it exists

AED 720K went to ads over 14 months with zero verified sales — not because the ads definitely failed, but because nothing was ever connected that could tell us. Every ads loop (L3, L5, L6, FIN-3) is only as honest as this foundation.

AED 720K

spent with no way to know what worked — the cost of missing plumbing

4 installs

Meta pixel + server events, GA4, Ads conversion import, Search Console

5 loops

downstream depend on it: L2 (search data), L3, L5, L6, and FIN-3's “results” column

🎯

Decide the owner

Who installs, given the agency dispute — the pending decision

🔌

Install tracking

Shopify-native: pixel, GA4, conversion import

🔍

Verify Search Console

Also unlocks the search-watch loop's data

🏷️

O2O bridges

Promo + QR codes for showroom attribution

✅

Hand over

Loops downstream switch from “spend” to “spend vs sales”

What it will never doSends no data anywhere new — it wires the shop's own analytics; customer privacy posture unchanged.

Where it stands today · July 2026Waiting on one decision: who installs the tracking, given the ongoing agency dispute. Everything is Shopify-native and reversible; the work itself is measured in days, not weeks.

Part 2 — under the hood

How it's wired: systems, models, and the path a number takes.

For implementers and the technically curious. The full build sheet — verified queries, thresholds, and build notes — lives on the specs page.

Readshuxberry.com (Shopify)

The shop that needs to become measurable

→

StepNative installs

Pixel + server events, GA4, conversion import

→

StepVerification

Search Console + test purchases traced end-to-end

→

StateHonest baseline

From here on, “results” means verified sales

→

DeliversDownstream loops

L2/L3/L5/L6 and FIN-3 inherit real numbers

System we read Automated step State / memory Human decision

System	Role in this loop
Shopifyhuxberry.com	All installs are Shopify-native — no custom code to maintain.
Meta + Googlepixel / GA4 / conversion import	The measurement layer on the platforms where the spend happens.
Search Consolegoogle	Site verification — also the data source the search-watch loop needs.

Model / brain	What it does here
Nonehuman project	This is configuration work by a person, checklist-driven — AI wrote the checklist and verifies the result.

State & memory

None — once installed, the state lives where it should: in the analytics platforms.

Delivery

A verified end-to-end test purchase, traced from ad click to sale, is the definition of done.

Safety rails

Read-only for everyone else; the installer follows the platform-native paths only. No customer data leaves our own analytics accounts.

Before it can run for real

Nish's decision on who installs (agency dispute context)

Full build sheet →