Practice III — AI Architecture
Perseus
Tracking SuiteAn 884-line tracking layer paired with GTM server-side. Stealth dual-pixel proxy.
01
Overview
Client-side tracking has collapsed. iOS privacy regimes, ad-blocker proliferation, and the deprecation of third-party cookies have moved the centre of gravity to the server. Most agencies have not followed; their attribution model is still founded on a Meta pixel and a GA4 client snippet, with all the integrity that implies.
Perseus moves the entire signal chain server-side. The dual-pixel proxy reconstitutes Meta and TikTok signals at the server boundary, behind HttpOnly cookies, with bot detection, deduplication, and exit-intent telemetry layered before the platforms ever receive the event. The advertiser owns the signal; the platform receives only what the architecture chooses to forward.
02
Specifications
- Stack: JavaScript · GTM Server-Side · CAPI
- Dual-pixel proxy: Meta + TikTok
- 884 lines of tracking code, version-controlled
- Bot detection, deduplication, exit-intent telemetry
- Scroll-fallback and engagement signals
- HttpOnly-cookie ID-fallback environments
- Multi-touch attribution feeding BigQuery / Snowflake
- Resistant to ad-blocker categories and iOS 17/18 privacy regimes
03
Engagement
Engagements within this module proceed by written brief. Submissions are evaluated within five business days. Acceptance opens a scoping conversation; mandate is governed by bilateral contract.