Connect your AI assistant to both Google Analytics 4 and PixelYourSite MCP at the same time and you get three things that are impossible to do efficiently any other way: verify that your existing events are working correctly, build new tracking events based on what GA4 shows actually converts, and find events sitting in GA4 that are ready to be activated on your ad platforms.
This guide covers all three. A good starting point is verifying what you already have before building new, but use whichever workflow fits what you need right now.
Connect Claude, ChatGPT, Gemini, or any MCP-compatible client to your site via PixelYourSite MCP, and to your GA4 property via GA4 MCP. Everything created or changed in PYS goes to all your connected platforms simultaneously: Meta, Google Ads, TikTok, Pinterest, and Bing.
To follow this guide you need PixelYourSite MCP connected to your site and the GA4 MCP server connected to your GA4 property. See Getting Started with PixelYourSite MCP for the PYS side. GA4 MCP setup instructions are at developers.google.com/analytics/devguides/MCP.
A useful setup: PYS data in GA4
PixelYourSite pushes traffic source, landing page, and UTM data to the dataLayer on every page load. If your GA4 property has custom dimensions configured to read those dataLayer variables, your GA4 reports return PYS attribution data directly: the same referrer domains and UTM values that PYS stores and uses in its source and landing_page conditions.
This makes all three workflows cleaner. Watch this video to set it up.
Workflow 1: Verify your existing events are working
Creating an event and testing it once is not the same as knowing it works at scale. This workflow uses GA4 data to verify that your PYS events (WooCommerce, EDD, and custom) are actually firing correctly in production.
Check your WooCommerce funnel
“Read my current PYS WooCommerce event configuration, then pull event counts from GA4 for each of those event names over the last 30 days.”
The assistant reads which WooCommerce events PYS has enabled, then queries GA4 for their counts. A healthy funnel shows progressive drop-off: many view_item events, fewer add_to_cart, fewer begin_checkout, fewest purchase. What to look for:
- A step with near-zero events: that event is not firing or has a name mismatch
add_to_cartandbegin_checkoutcounts that are nearly identical: the checkout step may be misconfiguringpurchaseevent count significantly lower than actual WooCommerce order count: events are being lost to consent blocking, caching, or CAPI not compensating correctly
“Compare the purchase event count in GA4 against my WooCommerce order count. Are there significant discrepancies?”
If yes, check CAPI status. A large gap between GA4 purchase events and actual orders usually means browser-side events are being blocked and server-side delivery is either off or misconfigured.
Check lifecycle events
If PYS lifecycle events are enabled (NewCustomer, ReturningCustomer, FrequentShopper, VIPClient), ask:
“Pull event counts for my PYS lifecycle events from GA4 over the last 90 days.”
If NewCustomer count is significantly higher than purchase count, something is wrong with the trigger logic. If FrequentShopper has zero events, either no customer has hit the threshold or the event is misconfigured. These discrepancies are invisible without looking at GA4 data.
Check the content ID
“Pull a sample of item_id values from recent purchase events in GA4.”
The assistant queries GA4 with itemId as a dimension on purchase events. If those IDs are integers (WordPress post IDs), your content ID is set to product_id, which is correct for most setups. If they look like SKUs, have prefixes, or are blank, your content ID configuration needs attention. This catches mismatches before they become dynamic ads problems.
Check custom events
“Read all my PYS custom events that are configured for GA4 or GTM, then check whether each one is appearing in GA4 data over the last 30 days.”
The assistant reads the event name for each PYS custom event on GA4/GTM platforms, then queries GA4 for counts. For each event:
- Zero count: not firing, name mismatch, or trigger condition too narrow
- Very low count relative to site traffic: trigger condition may be excluding most qualifying visitors
- Count looks right: working as expected
“Show me all event names in GA4 that I am not tracking in PixelYourSite.”
This catches events firing in GA4 from other sources (GTM tags, other plugins, theme scripts) that PYS does not know about. Some may be worth adding to PYS so they also fire on ad platforms.
Workflow 2: Build new events from GA4 data
Most tracking events get created based on assumptions. This workflow uses your actual analytics to decide what to build. Works best on sites with at least a few hundred conversions in GA4 over the past 90 days.
Start with the analysis
This is a multi-step conversation. The assistant makes separate calls to GA4 MCP and PYS MCP and you guide it through the findings.
“Check my GA4 data for the last 90 days. Which pages and traffic sources drive the most conversions?”
Once you have the findings:
“Now check my current PixelYourSite event setup. Given what GA4 shows, what tracking events am I missing?”
The assistant compares what GA4 shows is valuable against your current PYS configuration and proposes what to create.
Find your best pages
“Which pages lead to conversions most often? Show me the top 10 with their conversion rates.”
You will often find pages performing far above average with no dedicated pixel event. The assistant creates a page_visit event scoped to that URL and sends it to your relevant platforms in one step.
Compare traffic sources by quality
“Which traffic sources bring visitors who actually convert? Compare by conversion rate, not session count.”
A source with 500 sessions and a 4% conversion rate is more valuable than one with 5,000 sessions and a 0.3% rate. Build dedicated events for your best sources and exclusion events for your worst.
Find what to exclude
“Which traffic sources have the lowest conversion rate over the last 90 days?”
GA4 shows which sources never convert. PYS creates an event scoped to those referrer domains. That event becomes an exclusion audience in Meta and Google Ads. Retargeting budget stops going to visitors who will not buy.
Workflow 3: Activate GA4-only events on ad platforms
This is where the two MCPs create the most unexpected value. You likely have custom events configured in PYS for GA4 or GTM that are accumulating real data but have never been enabled on Meta, Google Ads, TikTok, or Pinterest. Those events represent audiences and signals sitting unused.
Find the dormant signals
“Read all my PYS custom events. Which ones are configured for GA4 or GTM only, with no Facebook, Google Ads, or TikTok? Then pull their event counts from GA4 over the last 90 days.”
The assistant reads the platform configuration for each custom event from PYS MCP, identifies the GA4-only ones, and queries GA4 for their counts. It then presents a ranked list: events with the highest counts that are not yet on ad platforms.
Get activation recommendations
For each high-volume GA4-only event, the assistant reasons about how to use it on ad platforms based on its trigger type, event name, and volume:
High-intent click event (e.g. PricingCTAClick, 3,000 events) Enable on Facebook and Google Ads. Use as a retargeting custom audience with a direct offer creative. Use as a lookalike seed. 3,000 pricing CTA clickers is a quality seed. Add as an audience observation signal in Google Ads Search campaigns.
Content engagement event (e.g. ContentReader, 15,000 events) Enable on Facebook and TikTok. Use as a retargeting audience with content-to-offer creative. High volume but mid-funnel. Better as a retargeting pool than a lookalike seed on its own.
High-intent multi-condition event (e.g. HighValuePaidVisitor, 180 events) Enable on Facebook. Volume is too low for a strong lookalike right now but worth retargeting directly with a high-urgency offer. Monitor monthly. Once it reaches 500+ events, seed a lookalike.
Lead event (e.g. ContactFormSubmitted, 450 events) Enable on Facebook as Lead, Google Ads as generate_lead, GA4 already has it. These are primary conversion events and should be on every platform. The assistant adds the missing platforms directly.
Activate in one step
“Enable PricingCTAClick on Facebook as a custom event and on Google Ads. Keep the existing GA4 configuration.”
The assistant updates the event configuration in PYS, adding the new platforms while preserving the existing ones. Two-step confirm. Done.
WooCommerce use case
A WooCommerce store runs all three workflows in one session.
Workflow 2 finds that hiking and camping category pages convert at 8% vs 2% site average, and one traffic source drives volume but never converts. Two new events created: HighValueCategoryView scoped to those category URLs, and an exclusion event for the non-converting source.
Workflow 1 finds that begin_checkout in GA4 has 40% fewer events than add_to_cart, a normal drop-off, but purchase is running 35% below actual WooCommerce order count. CAPI is enabled but the assistant checks and finds the token was saved incorrectly. Fixed in the same session.
Workflow 3 finds three GA4-only custom events: a SizeGuideViewer event with 2,200 events (created months ago for analytics, never added to ad platforms), a ContentReader event with 8,000 events, and a ProductVideoView event with 1,100 events. The assistant proposes enabling all three on Facebook and Google Ads, explains the audience strategy for each, and adds them with confirmation.
One session. All three workflows. Every platform updated.
Non-WooCommerce / services use case
A B2B services company runs Workflows 2 and 3.
Workflow 2 finds that /services/enterprise drives 40% of client conversions with only 8% of traffic and no pixel event. Two non-converting traffic sources identified. Three events created: EnterprisePageView, a high-quality source event, and an exclusion event.
Workflow 3 finds a GAOnly custom event called PricingCTAClick with 1,800 events over 90 days, created for analytics purposes and never activated on ad platforms. Also finds ContactFormSubmitted configured for GA4 only despite being the primary conversion event. The assistant adds Facebook Lead, Google Ads generate_lead, and TikTok to ContactFormSubmitted, and enables PricingCTAClick on Facebook and Google Ads with a retargeting strategy.
For agencies
Connect both MCPs to a client site and run all three workflows in one session. The assistant reads GA4, checks the current PYS event setup across all three dimensions (what to build, what is working, what is dormant) and implements the agreed changes directly.
What previously took a GA4 audit, a pixel audit, a cross-reference spreadsheet, and a recommendations document takes four or more hours. With both MCPs connected it takes 30 minutes. The client sees the analysis and the implementation in one meeting. Run this quarterly.
GA4 MCP setup
The official GA4 MCP server requires Python 3.10+ and a Google Cloud project with the GA4 Data API and Admin API enabled. One-time terminal setup using Application Default Credentials. Full instructions at developers.google.com/analytics/devguides/MCP.
Read-only. Cannot change your GA4 configuration. Maintained by the Google Analytics team.