Pixelyoursite Wordpress Ads

PixelYourSite WordPress Ads

When To Use

Use this skill when a user asks about PixelYourSite Professional setup or measurement debugging for WordPress, WooCommerce, GA4, Google Ads, Meta Pixel, Meta CAPI, Meta domain verification, Google Tag Manager, automatic events, custom events, cross-subdomain tracking, UTM templates, conversion labels, enhanced conversions, or tag/debug evidence.

Do not use this skill to mutate live WordPress, WooCommerce, Google Analytics, Google Ads, Meta, GTM, ConsentMagic, CDN, or cache settings. Give manual steps, evidence checklists, and diagnosis states only.

Intake First

Before recommending settings, collect the minimum context from references/intake-and-scope.md:

1. Site topology: root domain, subdomains, checkout domains, redirects, and whether each host is a WordPress install.
2. Active stack: PixelYourSite version/license tier, WooCommerce status, consent plugin, cache/minify/CDN, GTM loader, and relevant theme/form/checkout plugins.
3. Destinations: GA4 Measurement IDs, Google Ads AW IDs and conversion labels, Meta Pixel/Dataset IDs, GTM container IDs, and which destination is owned by PixelYourSite native tags versus GTM.
4. Business goals: purchases, lead forms, phone clicks, account signups, diagnostics, remarketing/audience use, and which Google Ads conversions are primary.
5. Evidence: redacted screenshots or summaries from Tag Assistant, GA4 DebugView, Meta Test Events, PixelYourSite logs, browser network/cookies, and platform conversion status.
6. Privacy boundary: never ask the user to paste raw click IDs, API secrets, CAPI tokens, Meta test event codes, customer data, downloaded logs, raw event payloads, private account exports, or unredacted screenshots into chat, transcripts, repo files, or artifacts.

If the prompt already describes a symptom, route through references/debugging-runbook.md before settings advice.

Route By Topic

Load only the references needed for the current question:

• Official source breadcrumbs and drift checks: references/source-map.md
• Intake, scope, privacy, and output states: references/intake-and-scope.md
• GA4 Measurement ID, Measurement Protocol, DebugView, enhanced measurement overlap, and cross-domain boundaries: references/google-analytics-ga4.md
• Google Ads AW IDs, conversion labels, enhanced conversions, Tag Assistant, primary/secondary conversion choices, and URL parameters: references/google-ads-conversions.md
• Meta Pixel/Dataset ID, CAPI access token, advanced matching, test event code lifecycle, event groups, Super Pack targeting, extra pixels, and domain verification: references/meta-facebook-capi.md
• Google Tag Manager container/dataLayer choices, container import, Super Pack targeting, and duplicate prevention: references/google-tag-manager.md
• Automatic events, custom events, event intent classification, form/tel/link events, and diagnostic events: references/automatic-and-custom-events.md
• WooCommerce Purchase/AddToCart/ViewContent tracking, order status, value, product IDs, feed matching, server-side purchase, and new_customer: references/woocommerce-tracking.md
• Global settings, external IDs, AJAX/sendBeacon, attribution persistence, exclusions, cache, subdomain cookies, and UTMs: references/global-settings-subdomains-utm.md
• No-fire, duplicate-fire, unverified/inactive conversion, wrong label, Meta CAPI, GTM split, server-side API, consent, cache, redirect, subdomain, and checkout debug flows: references/debugging-runbook.md

Operating Rules

• Force one tracking owner per destination ID: PixelYourSite native tag or GTM, not both.
• Separate analytics from optimization: GA4 can receive broader analytics events; Google Ads primary conversions should be business-valued outcomes.
• Treat enhanced conversions, CAPI, advanced matching, user-data capture, and consent mode as policy- and consent-dependent.
• Keep debug conclusions evidence-based: confirmed, suspect, not checked, or blocked.
• Summarize sensitive values by shape and presence only, such as AW id present, conversion label missing, or click_id_present=yes.
• If the user already provided sensitive values, do not repeat them. Redact the value and continue with presence/shape summaries only.
• If evidence is partial, state the next proof needed and stop short of claiming readiness.

Response Shape

For setup requests, answer with:

1. Missing intake questions.
2. Destination-owner decision.
3. Manual configuration checklist.
4. Verification evidence needed.
5. Privacy/compliance caveats.

For debug requests, answer with:

1. Expected event and platform conversion goal.
2. Evidence table using confirmed, suspect, not checked, and blocked.
3. Most likely cause, only if evidence supports it.
4. Next proof and stop condition.
5. Manual correction checklist after the blocker is understood.

Validation

Run the local validator after editing this skill:

.agents/skills/pixelyoursite-wordpress-ads/scripts/check.sh

Run the repo-level validator before shipping:

scripts/check-skills.sh