Track
- Checks that your key events (leads, purchases) actually fire in GA4.
- Audits your GTM container for outdated, duplicate and untriggered tags.
- Verifies that your Google Ads conversions are recording.
Every Monday at 7am, your Google stack checks itself. Code computes, Claude explains, you decide.
Most tracking problems aren't hard to fix. They're just never noticed: a lead form that stopped firing, a campaign spending with zero conversions, a page quietly losing traffic.
The main workflow runs on a schedule, once per client and per week. Each step hands clean data to the next.
Enter your first name and email to unlock the three files. They download straight to your computer.
Offer, architecture, access setup, alert rules, implementation, testing, sales and client follow-up.
Collects GA4, Ads, GSC and GTM data, applies rules, runs the Claude analysis, and sends the report and alert.
Alerts the Ops team if an execution fails. Import it first.
In n8n, go to Workflows → Import from File. Import gz-error-handler.json first, then gz-tracking-autopilot.json.
In the main workflow's settings, set “Ops — Error Handler” as the Error Workflow.
Create the credentials (Google OAuth2, Anthropic API key, SMTP, Google Sheets) and replace every REPLACE_ME in the “Load Client Config” node.
Run “Manual Run (Test)”, review the email you receive, adjust the thresholds, then activate the workflow.
No. You need to know your way around n8n and Google credentials. The playbook covers every step.
No, it is read-only. Fixes (phase 2) go through human approval.
Yes, you only need to swap one HTTP node.
About 2 hours per client once access is granted. The Google Ads developer token can take a few days.
Yes. Generative Z handles installation, configuration and team training.