Deploy Conversion Tracking From Speech
Over one weekend, a human sent short Slack messages — dictation-style one-liners — and the agent executed the full conversion-tracking stack on this site, verified it live in production, and reported back with proof each time. Zero dashboards opened by a human, zero tickets, no agency handoff.
What was getting in the way.
Conversion tracking normally means a ticket, a handoff, a dashboard session, and a wait — and when it finally lands, "installed" is taken on faith. Nobody proves the tag actually fires on the live site, single-page-app navigations quietly go uncounted or get attributed to the wrong page, and analytics events drift out of parity with ad-platform conversions because they were wired up in two different places at two different times.
Context
The agency's own site. The same weekend and the same channel also carried an ordered first-party engagement telemetry upgrade — per-section engagement on use-case pages, scroll depth, dwell, and the pre-success form interaction funnel — shipped and end-to-end verified the same night, on the same speech-to-production loop.
How the work runs.
- 01
Instruction arrives as speech
Saturday 9:53 PM ET, a human sends one Slack line: "add ga4 G-…". No ticket, no spec, no dashboard.
- 02
Read the codebase first
The agent reads the site's existing tagging setup and adds GA4 to the Google tag loader already in place, so it shares the existing EU/UK consent gate rather than introducing a second script.
- 03
Handle the single-page app
A route-change tracker sends a pageview on every in-app navigation, with the first load deduped against the loader's own initial pageview.
- 04
Wire conversions for parity by construction
The generate_lead event is placed in the contact form's success path in the same code block as the existing Google Ads conversion, so every form success fires both or neither.
- 05
Catch the bug before visitors do
In testing, the agent found that on SPA navigations the pageview initially carried the previous page's URL and title — the router updates state before the history and title commit. Fixed before release; without it, every GA4 pageview would have been attributed to the wrong page.
- 06
Prove it on production
A headless browser on the live site captured the actual gtag loaders and real /g/collect network hits — page_view on load and on an in-app navigation — before the agent reported done. GA4 realtime showed active users within minutes. Instruction to verified-live: 11 minutes.
- 07
Configure the platform, not just the site
Sunday 12:18 PM ET: "add a key event to GA4 for on form success, use the same trigger as the google ads conversion fire for parity." 61 seconds later the agent had created the generate_lead key event through the Google Analytics Admin API (counting method ONCE_PER_EVENT) with its service-account access and verified it in the property's key events list. No site change was needed — parity was already structural.
Evidence from the workflow.
Each system has a role.
Intake — the entire instruction interface: human one-liners in, verified reports out
Slack
Action — the agent reads, edits, and ships the site itself
Site codebase + deploy pipeline
Action — Data API and Admin API via service account: tag config and key-event creation
Google Analytics 4
Action — the existing conversion the GA4 event is wired alongside for parity
Google Ads gtag
Assurance — real production network hits captured before any "done" is reported
Headless browser verification
Record of truth — first-party engagement and attribution events
Postgres (first-party events)
Why this is Operator.
Owns a workflow end to end, running the process inside the authority you set.
- 01
Site code, tag installs, and analytics configuration execute autonomously inside granted access. Ad spend, campaign settings, and ad-account changes stay human-approved. Every "done" report must carry live verification evidence, not assumptions.
Impact / Outcomes
Instruction → verified live in 11 minutes for the GA4 install; 61 seconds for the key event configuration.
2 human one-liners, 0 dashboards opened by a human.
GA4 and Google Ads conversion parity guaranteed by construction — same trigger, same guard, every form success fires both or neither.
A wrong-page attribution bug caught before a single visitor was miscounted.
Find where a workflow like this fits.
Start with the systems, work, constraints, and authority already present in your operation.