Google Ads
arnabbagxd/Brand-building-skills
Plan, build, and optimize Google Ads campaigns — Search, Shopping, Performance Max, Display, and YouTube — including keyword research, match types, bidding strategy, Quality Score, ad extensions…
Sets up and verifies conversion tracking before ad spend: Meta Pixel and CAPI, Google Ads, GA4, TikTok, server-side GTM, consent mode, UTMs and a pre-launch checklist.
Install Ad Conversion Tracking Setup
$ npx skills add minhnv0807/ai-business-skills --skill 53-tracking-setup-global -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install minhnv0807/ai-business-skills 53-tracking-setup-global --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/minhnv0807/ai-business-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/en/53-tracking-setup-global .claude/skills/53-tracking-setup-global && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "53-tracking-setup-global" agent skill from https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/53-tracking-setup-global into .claude/skills/53-tracking-setup-global/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "53-tracking-setup-global", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/53-tracking-setup-globalType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add minhnv0807/ai-business-skills --skill 53-tracking-setup-global -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install minhnv0807/ai-business-skills 53-tracking-setup-global --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/minhnv0807/ai-business-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/en/53-tracking-setup-global .agents/skills/53-tracking-setup-global && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "53-tracking-setup-global" agent skill from https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/53-tracking-setup-global into .agents/skills/53-tracking-setup-global/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "53-tracking-setup-global", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add minhnv0807/ai-business-skills --skill 53-tracking-setup-global -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install minhnv0807/ai-business-skills 53-tracking-setup-global --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/minhnv0807/ai-business-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/en/53-tracking-setup-global .cursor/skills/53-tracking-setup-global && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "53-tracking-setup-global" agent skill from https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/53-tracking-setup-global into .cursor/skills/53-tracking-setup-global/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "53-tracking-setup-global", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/minhnv0807/ai-business-skills.git --path skills/en/53-tracking-setup-global--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add minhnv0807/ai-business-skills --skill 53-tracking-setup-global -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install minhnv0807/ai-business-skills 53-tracking-setup-global --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/minhnv0807/ai-business-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/en/53-tracking-setup-global .gemini/skills/53-tracking-setup-global && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "53-tracking-setup-global" agent skill from https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/53-tracking-setup-global into .gemini/skills/53-tracking-setup-global/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "53-tracking-setup-global", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install minhnv0807/ai-business-skills 53-tracking-setup-globalInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add minhnv0807/ai-business-skills --skill 53-tracking-setup-global -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/minhnv0807/ai-business-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/en/53-tracking-setup-global .github/skills/53-tracking-setup-global && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "53-tracking-setup-global" agent skill from https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/53-tracking-setup-global into .github/skills/53-tracking-setup-global/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "53-tracking-setup-global", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add minhnv0807/ai-business-skills --skill 53-tracking-setup-global -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install minhnv0807/ai-business-skills 53-tracking-setup-global --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/minhnv0807/ai-business-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/en/53-tracking-setup-global .opencode/skills/53-tracking-setup-global && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "53-tracking-setup-global" agent skill from https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/53-tracking-setup-global into .opencode/skills/53-tracking-setup-global/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "53-tracking-setup-global", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
53-tracking-setup-global- GitHub stars
- 610
- Token cost
- ~3.7k tokens
- SKILL.md length
- 1,671 words
- Files
- 2 (incl. references)
- Skills in repo
- 142
- Repo updated
- First seen
- Licence
- MIT
At a glance
Sets up and verifies conversion tracking before ad spend: Meta Pixel and CAPI, Google Ads, GA4, TikTok, server-side GTM, consent mode, UTMs and a pre-launch checklist.
- Works in 9 steps: Choose the measurement architecture → Consent management (do this before any… → Install per platform → …
- Setting up pixels and server-side events before launching paid campaigns
- SKILL.md covers Information gathering, Principles, Workflow and Troubleshooting, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
This skill treats verified tracking as a precondition for advertising: ads should not launch until tracking checks out green, because spend before that cannot be measured and changing events mid-campaign breaks historical comparisons. It covers Meta Pixel with the Conversions API, Google Ads conversions with Enhanced Conversions, GA4, TikTok Pixel with the Events API, server-side Google Tag Manager, UTM conventions and attribution windows under iOS ATT.
It starts with up to four questions: which ad platforms and objective, what runs the website and whether the head tag or GTM can be edited, which markets receive traffic, which decides consent rules such as GDPR and ePrivacy for the EU and UK or CCPA and CPRA for California, and whether the sale closes on the site or offline, which would need CRM or offline conversion import. A reference file holds per-platform install steps and consent mode parameters.
It ends with a pre-launch verification checklist and is also used when conversions are not being recorded or Meta and Shopify numbers disagree. Broad audits of a live account, analysis of data once it flows and campaign hierarchy are left to other named skills.
When your agent uses it
- Setting up pixels and server-side events before launching paid campaigns
- Fixing conversions that are not being recorded in an ad platform
- Reconciling mismatched Meta and Shopify purchase numbers
- Adding consent mode for visitors covered by GDPR or CCPA
- Verifying tracking when a launch is close and nothing has been checked
Example prompts
- “Set up Meta Pixel and the Conversions API for our Shopify store before the Friday launch.”
- “Our GA4 purchase events are not showing up in Google Ads. Help me find out why.”
- “Draft a UTM naming convention for Meta, Google and TikTok campaigns.”
- “Walk me through the pre-launch tracking checklist for a lead-gen landing page on Webflow.”
Requirements
- Edit access to the site's head tag or Google Tag Manager
- Access to the ad accounts being set up
Workflow steps
9 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 0360adc. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Ad Conversion Tracking Setup loads about 3.7k tokens when it runs, and up to ~5.6k if it reads all its reference files. Until then it costs about 187 tokens; SKILL.md has 1,671 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from minhnv0807/ai-business-skills at commit 0360adc, republished under its MIT licence (© minhnv0807). 1,671 words, ~3,679 tokens.
Download SKILL.mdSave it as
.claude/skills/53-tracking-setup-global/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- 53-tracking-setup-global
- description
- Use when conversion TRACKING must be set up or fixed before spending — Meta Pixel and Conversions API, Google Ads conversions with Enhanced Conversions, GA4, TikTok Pixel and Events API, server-side GTM, consent mode for GDPR and CCPA, UTM conventions, iOS ATT attribution windows, and a pre-launch verification checklist. Trigger on 'tracking setup', 'pixel setup', 'CAPI', 'GA4 events', 'conversions are not being recorded', 'Meta and Shopify numbers do not match'. Also use when launch is imminent and nothing has been verified. Not for — auditing a live account broadly, see `21-ads-audit-global`; analyzing data once it flows, see `13-data-analysis-global`; the campaign hierarchy, see `52-account-structure-global`.
- metadata.version
- 1.0.1
- metadata.category
- performance
- license
- MIT
- triggers
- tracking setup, pixel setup, conversions API, CAPI, GA4 setup, server-side tracking, consent mode, UTM convention, conversion tracking not working
- output
- File .md — tracking setup checklist per platform, consent plan, UTM template, event mapping, CRM/offline conversion plan, pre-launch verification checklist…
- related
- product-marketing-context-global, 52-account-structure-global, 54-media-plan-global, 21-ads-audit-global, 12-landing-page-brief-global, 13-data-analysis-global
Tracking Setup (Global)
Ads without verified tracking is driving blind. Hard rule: do not launch ads until tracking verifies green. Every dollar spent before verification is unmeasurable. Set it up correctly the first time — changing events mid-campaign destroys historical comparability.
Full per-platform install steps and the consent mode parameter reference: read
references/platform-tracking-setup.md.
Information gathering
Ask up to 4 questions:
- Which ad platforms and objective? Meta / Google / TikTok / LinkedIn / YouTube — lead (form or message) / purchase / traffic?
- What runs the website or landing page? Shopify / WordPress / Webflow / Framer / custom — and is there access to edit the head tag or install GTM?
- Which markets receive traffic? This decides the consent requirements: EU/UK means GDPR and ePrivacy, California means CCPA/CPRA, other US states have their own opt-out laws.
- Where does the sale actually close? On site (pixel-measurable) or offline via sales calls, demos, or DMs (needs CRM/offline conversion import)?
Principles
- No green, no launch. Verification comes before spend, every time.
- Consent is part of tracking, not a legal afterthought. In the EU/UK, tags must not fire before consent. Getting this wrong risks fines and, on Google, loss of remarketing audiences.
- One installation method only. GTM plus hardcoded tags equals duplicate events and doubled phantom conversions.
- Client-side plus server-side, deduplicated. Browser-only tracking loses a large share of events to ad blockers, ITP, and iOS ATT. Send the same event from both sides with a shared event ID.
- Consistent UTMs. Define the convention once, before anyone builds a link. GA4 cannot repair inconsistent casing or naming after the fact.
- Measure to revenue, not to lead. If 1,000 leads produce 10 sales, you must be able to tell whether the failure is in ads or in sales. That requires CRM or offline conversion import.
- Expect platform numbers to disagree. Ads managers use different attribution windows and modeled conversions. Pick one source of truth for decisions and use the others as directional.
Workflow
1. Choose the measurement architecture
| Layer | Purpose | Minimum |
|---|---|---|
| Client-side pixel/tag | Fast setup, on-page events | Meta Pixel, Google tag, TikTok Pixel |
| Server-side API | Recovers events lost to blockers and ITP | Meta Conversions API, TikTok Events API, Google Enhanced Conversions |
| Analytics | Cross-channel truth, funnel analysis | GA4 with key events configured |
| Consent layer | Legal gate in front of everything above | CMP plus Google consent mode v2 |
| CRM / offline | Connects leads to actual revenue | CRM with source fields, offline conversion import |
Server-side GTM is the recommended container for anything beyond a simple store: it centralizes event forwarding, improves data quality, and keeps first-party cookie lifetimes usable under ITP.
2. Consent management (do this before any tag fires)
This is a first-class requirement, not an optional extra.
EU / UK — GDPR and ePrivacy:
- Install a certified consent management platform. Meta requires a CMP for EU traffic; Google requires a Google-certified CMP for EEA/UK traffic to keep personalized advertising and audience features.
- Implement Google consent mode v2. The four signals are
ad_storage,analytics_storage,ad_user_data,ad_personalization. Default them todeniedfor EEA/UK before the banner is answered, then update on consent. - Non-essential tags must not fire before consent is granted. Consent must be as easy to refuse as to accept, and withdrawable.
- Keep a consent log — which user, which choice, when, which policy version.
California — CCPA/CPRA (and comparable US state laws):
- Provide a visible opt-out of sale/sharing of personal information.
- Honor the Global Privacy Control browser signal as a valid opt-out.
- On Meta, apply Limited Data Use for California traffic.
Email and SMS: CAN-SPAM in the US and GDPR in the EU require documented opt-in for marketing sends and a working unsubscribe. Any list uploaded as a Custom Audience or Customer Match list must have that consent on record — see 14-email-marketing-global.
Record the decision in the output file: which CMP, which regions gated, who verified.
3. Install per platform
Full step-by-step checklists live in references/platform-tracking-setup.md. Summary of what must exist:
| Platform | Client-side | Server-side | Verification tool |
|---|---|---|---|
| Meta | Pixel with standard events (PageView, ViewContent, AddToCart, Lead, Purchase) | Conversions API with event_id deduplication, Event Match Quality >= 6.0 | Meta Pixel Helper, Test Events |
| Google Ads | Google tag / GTM conversion actions | Enhanced Conversions (hashed email/phone), consent mode v2 | Tag Assistant, conversion diagnostics |
| GA4 | GA4 tag, key events marked as conversions | Measurement Protocol or server-side GTM | GA4 DebugView, Realtime |
| TikTok | TikTok Pixel (ViewContent, AddToCart, SubmitForm, CompletePayment) | Events API with deduplication | TikTok Pixel Helper, Events diagnostics |
| Insight Tag with conversion rules | Conversions API for CRM-side events | LinkedIn Insight Tag Helper |
Only one primary conversion action per objective should be enabled for bidding. Extra enabled conversions inflate counts and confuse smart bidding.
4. iOS ATT and attribution windows
Since iOS 14.5, a large share of iOS users opt out of app tracking, so platform-reported conversions are partly modeled rather than observed.
- Meta's post-ATT default is a 7-day click / 1-day view attribution window. Compare periods on the same window or the trend is meaningless.
- Verify the domain and configure Aggregated Event Measurement with a prioritized list of up to 8 web events per domain. The event you optimize for must be ranked highest.
- Expect ads manager conversions and GA4 last-click conversions to differ, often materially. Decide up front which one drives budget decisions.
- Server-side events plus Enhanced Conversions and good Event Match Quality recover a meaningful share of the loss. This is the main reason server-side is no longer optional.
- Third-party cookie deprecation compounds this. Prioritize first-party data collection — email capture, account creation, CRM — over pixel-only audience building.
5. UTM convention
https://domain.com/lp?utm_source=[source]&utm_medium=[medium]&utm_campaign=[campaign]&utm_content=[ad_name]| Parameter | Convention | Example |
|---|---|---|
| utm_source | meta / google / tiktok / linkedin / klaviyo | meta |
| utm_medium | paid_social / paid_search / display / email / organic | paid_social |
| utm_campaign | [product]_[audience]_[market]_[MMYY] | course-a_cold_us_0726 |
| utm_content | [creative-type]_[hook-type]_[version] — matches the ad name | vid_pain_v1 |
Lowercase, no spaces, no special characters. utm_content must equal the ad name defined in 52-account-structure-global so ads manager and GA4 reconcile in both directions. Add utm_term only for search keywords.
Show full SKILL.md (703 more words)Show less
6. GA4 event mapping
| GA4 event | Trigger | Platform equivalent |
|---|---|---|
| page_view | All pages | PageView (Meta), ViewContent (TikTok) |
| view_item | Product or offer page | ViewContent (Meta) |
| add_to_cart | Cart add | AddToCart (Meta/TikTok) |
| begin_checkout | Checkout started | InitiateCheckout (Meta) |
| generate_lead | Form submit or qualified message | Lead (Meta), SubmitForm (TikTok), Conversion (Google) |
| purchase | Payment confirmed, with value and currency | Purchase (Meta/TikTok/Google) |
Each action fires exactly one event. Mark the event that matches the ads objective as a key event in GA4. Always send value and currency on purchase — without them ROAS cannot be computed and multi-market revenue cannot be normalized.
7. CRM and offline conversions
Required whenever the sale closes off-site (B2B, high-ticket, coaching, agency, phone or DM sales):
- Capture source on every lead. CRM fields: source, medium, campaign, ad content, GCLID or fbclid, timestamp, owner, stage, disqualification reason, closed revenue.
- Import offline conversions weekly. Meta offline/CAPI conversions and Google Ads offline conversion import via GCLID or Enhanced Conversions for Leads. This teaches bidding from real revenue instead of raw lead count.
- Reconcile monthly. Compare CRM lead count against ads manager lead count. A gap above 20% signals a tracking or attribution problem, not a sales problem.
Uploaded CRM data must be hashed and covered by consent.
8. Verify green before launch
All must pass. One missing item means do not launch:
- Pixel/tag fires on landing page and confirmation page
- Correct conversion event type selected — not PageView
- No duplicate events (one action, one event in the events manager)
- Server-side API live, deduplication working, Meta EMQ >= 6.0
- Google Enhanced Conversions enabled and receiving hashed data
- Consent mode v2 implemented; tags blocked before consent in EEA/UK; Limited Data Use applied for California
- Test event: complete one real conversion and confirm it is recorded
- Domain verified and Aggregated Event Measurement events prioritized
- UTMs on all ad links and matching the convention
- GA4 receiving paid sessions (confirm in Realtime)
- CRM source capture live if the sale closes off-site
9. Ongoing checks
Daily (2 minutes): events flowing in the last 24 hours on every platform; Google Ads conversions recording; GA4 showing paid sessions.
Weekly: server-side match rate above 70%; no duplicate events; lead counts across ads manager, GA4, and CRM within 20% of each other; every live link carries a correct UTM; consent banner still firing correctly after any site release.
Troubleshooting
| Problem | Common cause | Fix |
|---|---|---|
| Pixel does not fire | Tag missing on the page or blocked by consent gate | Check GTM preview and the consent state; confirm the tag is allowed after consent |
| Duplicate events | GTM and hardcoded tag both installed | Remove one; verify event_id deduplication |
| Low match rate / low EMQ | No hashed email or phone sent server-side | Add customer parameters to the server payload |
| Conversion not recorded | Wrong event name or wrong trigger page | Check spelling and that the trigger is the confirmation page |
| GA4 far below ads manager | Different attribution windows plus modeled conversions | Compare on the same window; treat one source as decision-grade |
| Remarketing audiences shrinking in the EU | Consent mode v2 missing or misconfigured | Implement all four consent signals and a certified CMP |
| Leads arrive with no source | No CRM source capture | Add hidden UTM/click-ID fields to every form |
Output structure
File name: tracking-setup-[product]-[YYYYMMDD].md
# Tracking Setup — [Product/Campaign]
Platforms: [list] · Site platform: [x] · Markets: [x] · Objective: [Lead/Purchase]
## 1. Measurement architecture [client, server, analytics, consent, CRM]
## 2. Consent plan [CMP, regions gated, consent mode v2, LDU, log owner]
## 3. Platform setup status [table with status per item]
## 4. Attribution settings [window per platform, AEM priority list]
## 5. UTM convention [parameters and real project examples]
## 6. Event mapping [GA4 to platform events]
## 7. CRM / offline conversions [fields captured, import cadence]
## 8. Pre-launch verification [green checklist, verified by, date]
## 9. Ongoing check schedule [who, when, alert thresholds]Related skills
52-account-structure-global: build campaigns only after tracking is green;utm_contentmust match ad names.54-media-plan-global: the objective in the plan determines which events must be tracked.21-ads-audit-global: periodic tracking audit (match rate, duplicates, EMQ).12-landing-page-brief-global: the landing page must expose the events and form fields this setup needs.13-data-analysis-global: reads the clean data this system produces.
Quality checklist
- Setup checklist complete for every platform in the plan
- Consent plan explicit: CMP, consent mode v2 signals, regions, California opt-out, consent log
- Server-side layer live with deduplication and a documented match rate
- Attribution window stated per platform, with an agreed decision-grade source
- UTM convention documented with real examples and matching ad names
- Event mapping complete from page_view to purchase, with value and currency
- Offline or CRM conversion path exists if the sale closes off-site
- Green verification checklist completed, dated, and signed off by a named person
- Daily and weekly checks scheduled with alert thresholds (match rate >70%, source gap <20%)
- The hard rule is restated in the output: not green means do not launch
© minhnv0807, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/en/53-tracking-setup-global of minhnv0807/ai-business-skills.
- SKILL.md
- references/platform-tracking-setup.md
Open the folder on GitHubat commit 0360adc
Compare with similar skills
Ad Conversion Tracking Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ad Conversion Tracking Setup this skillminhnv0807/ai-business-skills | 610 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Google Adsarnabbagxd/Brand-building-skills | 724 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Google Consent Mode V2mukul975/Privacy-Data-Protection-Skills | 297 | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Utm Buildercognyai/claude-code-marketing-skills | 104 | — | ~4.3k | Automated safety check: Notes | None | |
| Blog GoogleAgriciDaniel/claude-blog | 2.3k | 1 repos | ~3.3k | Automated safety check: Notes | MIT | |
| Paid Ads AuditAgriciDaniel/claude-ads | 9.8k | — | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
Google Consent Mode V2
mukul975/Privacy-Data-Protection-Skills
Configuring Google Consent Mode v2 for privacy-compliant measurement and advertising.
Utm Builder
cognyai/claude-code-marketing-skills
UTM Parameter Strategy & Builder — naming conventions, GA4 channel grouping rules, auto-tagging, common mistakes, and BigQuery validation queries
Blog Google
AgriciDaniel/claude-blog
Google API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity…
Paid Ads Audit
AgriciDaniel/claude-ads
Runs a source-grounded paid advertising audit across up to 12 ad platforms, with parallel platform workers, deterministic scoring and a versioned JSON bundle.
Soku CLI
About-Intelligence/soku-cli
Guides an agent through the soku command line tool for ads, GA4 and PostHog data reads, ads writes, SEO hosting, automations, files and skill management.
More from minhnv0807/ai-business-skills
All 142 skills in this repoDesign Master
minhnv0807/ai-business-skills
Handles eight kinds of marketing visual requests, from logos and campaign key visuals to infographics and quote graphics, by generating images or writing paste-ready prompts.
Offer Design
minhnv0807/ai-business-skills
Designs or repairs what a business sells, covering the promise, value stack, bonuses, guarantee, honest scarcity and a tiered ladder, rather than price or copy.
Global SEO Growth
minhnv0807/ai-business-skills
Covers six SEO layers for a website: crawl and index audit, local SEO, search-intent content, AI search visibility, schema markup and backlink or directory distribution.
B2B Lead Generation
minhnv0807/ai-business-skills
Plans B2B pipeline work from ICP definition and prospecting through lead scoring, outbound sequences, sales assets and MQL to SQL handoff, aiming at qualified pipeline.
Community Seeding Plan
minhnv0807/ai-business-skills
Plans honest participation in outside communities such as Reddit, Discord and Facebook Groups, with a rules-based community list, roster, posts, replies and calendar.
Global Marketing Plan
minhnv0807/ai-business-skills
Builds a full marketing plan for a period, from objectives and segments to channel mix, budget, timeline, KPIs and risks, adapted to the US, EU, SEA or LATAM.
Related
Works with
Categories
Questions about Ad Conversion Tracking Setup
What does Ad Conversion Tracking Setup do?
Sets up and verifies conversion tracking before ad spend: Meta Pixel and CAPI, Google Ads, GA4, TikTok, server-side GTM, consent mode, UTMs and a pre-launch checklist. This skill treats verified tracking as a precondition for advertising: ads should not launch until tracking checks out green, because spend before that cannot be measured and changing events mid-campaign breaks historical comparisons. It covers Meta Pixel with the Conversions API, Google Ads conversions with Enhanced Conversions, GA4, TikTok Pixel with the Events API, server-side Google Tag Manager, UTM conventions and attribution windows under iOS ATT.
When should I use Ad Conversion Tracking Setup?
Ad Conversion Tracking Setup fits situations like: setting up pixels and server-side events before launching paid campaigns; fixing conversions that are not being recorded in an ad platform; reconciling mismatched Meta and Shopify purchase numbers; adding consent mode for visitors covered by GDPR or CCPA.
How do I install Ad Conversion Tracking Setup in Claude Code?
Run `npx skills add minhnv0807/ai-business-skills --skill 53-tracking-setup-global -a claude-code`. Or copy the skill folder (skills/en/53-tracking-setup-global in minhnv0807/ai-business-skills) into .claude/skills/53-tracking-setup-global in your project. Claude Code loads it when a task matches its description.
How do I install Ad Conversion Tracking Setup in Codex?
Run `npx skills add minhnv0807/ai-business-skills --skill 53-tracking-setup-global -a codex`. Or copy the skill folder (skills/en/53-tracking-setup-global in minhnv0807/ai-business-skills) into .agents/skills/53-tracking-setup-global in your project. Codex loads it when a task matches its description.
Can I use Ad Conversion Tracking Setup in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add minhnv0807/ai-business-skills --skill 53-tracking-setup-global -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/53-tracking-setup-global, .gemini/skills/53-tracking-setup-global, .github/skills/53-tracking-setup-global and .opencode/skills/53-tracking-setup-global in your project.
What does Ad Conversion Tracking Setup need to run?
SKILL.md names no scripts, command-line tools or credentials: Ad Conversion Tracking Setup is instructions for the agent only. Our summary lists: Edit access to the site's head tag or Google Tag Manager; Access to the ad accounts being set up.
Does Ad Conversion Tracking Setup access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Ad Conversion Tracking Setup safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Ad Conversion Tracking Setup use?
Ad Conversion Tracking Setup is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ad Conversion Tracking Setup use?
About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2k tokens, read only when the agent opens those files.
What are the alternatives to Ad Conversion Tracking Setup?
Skills that share tags, products or a category with Ad Conversion Tracking Setup: Google Ads (arnabbagxd/Brand-building-skills, 724 stars), Google Consent Mode V2 (mukul975/Privacy-Data-Protection-Skills, 297 stars), Utm Builder (cognyai/claude-code-marketing-skills, 104 stars) and Blog Google (AgriciDaniel/claude-blog, 2.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ad Conversion Tracking Setup?
minhnv0807 (a GitHub user) maintains it in minhnv0807/ai-business-skills, which has 610 GitHub stars. The repository holds 142 skills in this directory. The repository was last updated on September 12, 2026.
Source: minhnv0807/ai-business-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.