Fix the pixels and events that aren't firing.
Overview
You're paying for traffic, and whether that money works comes down to a few events reaching your ad platforms: page view, add to cart, checkout, purchase. When one breaks, every report downstream is wrong. The agent loads your live page, watches what actually fires, and hands you a table of what's present, missing, or double-counting. Everything in the report is observed, not inferred. Start with your highest-spend landing page.
Before you start
- A live page URL to audit. That's the whole list.
- Connected ad and analytics integrations are optional; they sharpen the expected-tracking list.
The prompt
Paste this into the agent. The bold values are yours to change:
Audit the tracking on this page: [your page URL]. The conversion that matters here is [a completed purchase through Shopify checkout].
1. Build the expected list. Check my connected integrations, my Scripts & Pixels settings, and the scripts in the page source. List every tracking tool you find: Meta pixel, GA4, TikTok, Google Ads, TripleWhale, Northbeam, Elevar, Klaviyo onsite, and any GTM container plus the tags inside it.
2. Verify what actually fires. Load the page and watch network requests and the dataLayer for: a page view on load, view_item (or this page's equivalent), add_to_cart when the cart button is clicked, and begin_checkout on the checkout handoff.
3. Check the handoff. When the cart moves from this page's domain to my checkout domain, confirm UTM parameters and session identity carry over, so the purchase can be attributed back to this page and its ad.
4. Check for double-firing (the same event sent twice by two installs of the same tag) and consent order: if a consent banner is present, confirm pixels wait for consent instead of firing first.
5. Report a table: tool, event, and one of present / missing / firing twice / fired before consent, with a severity for each gap and a recommended fix. Don't change anything until I approve.
The money event is the one line to edit. Purchase for ecommerce, the booking click for a booking page, the form submit for lead gen, selling-plan opt-in for a subscription funnel.
What the agent does
- Builds the expected-tracking list from your connected integrations, Scripts & Pixels, and the page source. You don't fill out a manifest; it's derived.
- Loads the live page and observes network requests and dataLayer events through a real browsing session, including clicking through to the cart and checkout handoff.
- Diffs expected against observed for the four standard events plus your money event.
- Reports present / missing / firing twice / fired before consent, each with severity and a fix.
- Offers to apply approved fixes in Scripts & Pixels, or tells you where the fix lives when it's outside our reach (your GTM container, Shopify checkout settings).
Try it on your store
The prompt opens in the agent ready to edit, with your store and tools connected.