How Ivee Hub works

Three views of the same system — the click journey, the launch checklist, and the proof tiers.

1 · The click journey (where the number comes from)

Every ad click is captured by Ivee before it reaches the client — and measured on the way through.

Google Ad
tracking template installed
→
Ivee Smart Page
RedTrack mints click id
?cmpid
→
Continue →
appends the bridge id
?ivid=
→
Client site
iv.js reads ivid
→
iv.js
fires landing +
verified_visit
Ivee relay
first-party /i/collect
→
RedTrack (S2S)
system of record
→
Google Ads CAPI
revenue / ROAS — Phase 2 config flip
Runs inside Ivee External Phase 2

2 · Launch checklist (no PASS, no launch)

Six checkpoints, each with a named owner and a machine-verifiable pass. Dashed = strongly recommended (sets the tier); solid = required to launch.

0.1
Brief
→
0.2
Smart Page
→
0.3
GA4 access
→
0.4
Ads + domain
→
0.5
iv.js
→
0.6
Test click
→
🚀 Launch
0.6 (automated test click into RedTrack) is the universal non-negotiable — it IS the "zero-error setup" milestone.

3 · Proof tiers (degraded is fine — the code is an upgrade)

The campaign launches no matter what. Client cooperation raises the tier; it never gates the launch.

Ads-only

zero client cooperation · now

  • Smart Page verified loads
  • Continue clicks
  • shown beside their GA4

Verified ★

+ 3 lines (iv.js) + GA4 · the target

  • engaged-session KPI, provable
  • reconciled to their GA4
  • defended vs any analytics

Revenue

+ checkout S2S + CAPI · Phase 2

  • purchases / revenue
  • ROAS, CPA
  • feeds Google bidding