This is taking longer than expected.

Try againBrowse the library
AI Blocks

All AI specialists

Hire an AI conversion tracking planner

Plan or fix your ad conversion tracking across GA4, Google Ads and Meta. Get an event list, a double-count check and a step-by-step test plan.

What you give

  • What counts as a conversion for you, such as a purchase, a lead form or a booked call, and what each is worth
  • The ad platforms you run, such as Google Ads, Meta, LinkedIn or TikTok
  • Your site type and platform, such as a Shopify store or a lead site on WordPress

What you get

  • A list of conversion events, each with its trigger, details to send and platforms that receive it
  • A plan for which conversion counts toward bidding and which are only for reporting
  • A plan to stop the same sale being counted twice
  • A consent and privacy section for your regions

An example

You are launching or redesigning a website, and need a tracking plan before the first ad runs.

You ask: “Plan or fix your ad conversion tracking across GA4, Google Ads and Meta. Use the material I attach and ask for anything essential that is missing.”

You get back:

  • Conversion definitions. Each conversion, its value and whether it teaches bidding or only reports.
  • Event plan. Each event with its trigger, the details it carries and where it goes.
  • Deduplication. A shared ID for each event, so browser and server events count once.

An example, not your task.

Words used here

  • GA4: Google Analytics, the tool that counts your site visits

Hire this specialist

It is free and needs no account. Download the pack, give it to your AI and tell it the job. Your AI asks for anything it is missing, then does the work and checks it.

Download the specialist

Related specialists

Skills and workflows for this job: Track your numbers

Details

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

  • A list of conversion events, each with its trigger, details to send and platforms that receive it
  • A plan for which conversion counts toward bidding and which are only for reporting
  • A plan to stop the same sale being counted twice
  • A consent and privacy section for your regions
  • A test plan for each event, with the tool to use and the result to expect
  • A ranked list of likely causes when your counts disagree

How it does the job well

  • You cannot verify the live setup. Say what you saw and what you assumed.
  • Do not ask for, or accept, passwords, API keys or customer lists in the chat.
  • Write for one named audience and one action. Each asset has a single job.
  • Use the customer's own words from reviews, calls or surveys before inventing language.
  • Every claim needs proof the business can show. Leave unproven claims out or mark them.
  • Judge results against the business goal, such as profit or qualified leads, not clicks alone.

Mistakes it avoids

  • Generic copy that could fit any brand.
  • Comparing periods or campaigns that are not comparable, such as different dates, budgets or tracking.
  • Calling a test winner before there is enough data.

What a good result looks like

An example, not your task: You are launching or redesigning a website, and need a tracking plan before the first ad runs.

  • Conversion definitions. Each conversion, its value and whether it teaches bidding or only reports.
  • Event plan. Each event with its trigger, the details it carries and where it goes.
  • Deduplication. A shared ID for each event, so browser and server events count once.
  • Consent and privacy. What changes in tracking when a visitor refuses cookies.
  • Test plan. A test for each event with the tool, the steps and the expected result.
  • Likely causes of mismatch. A ranked list of why your counts differ, each with the test that settles it.

How the work is checked

  • Every claim traces to the brand brain or supplied evidence.
  • Each recommendation states the expected effect, the cost and how it will be measured.
  • Copy fits the platform's length limits and the brand voice.
  • States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

  • Define the conversions. It confirms what counts as a conversion and its value, and which of them should teach the ad platform.
  • Map the events. It lists each event, its trigger, the details it must carry and where it goes.
  • Plan deduplication. It sets one shared event ID, so a browser and a server event for the same sale count once.
  • Add consent and privacy. It notes what changes when a visitor refuses cookies, and what each region needs.
  • Write the tests. It names the tool for each check, such as Tag Assistant or the Meta test events tool, and the result to expect.
  • Rank the causes. For any mismatch, it lists likely causes from most to least likely and the test that settles each.

How the role works

  1. Checks your task, context and available tools.
  2. Picks the methods needed and prepares a work plan.
  3. Carries out supported tasks, with each method's limits and review gates.
  4. Checks the real deliverables and corrects supported faults.
  5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id paid-media-tracking-specialist only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/paid-media-tracking-specialist/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

  • What counts as a conversion for you, such as a purchase, a lead form or a booked call, and what each is worth
  • The ad platforms you run, such as Google Ads, Meta, LinkedIn or TikTok
  • Your site type and platform, such as a Shopify store or a lead site on WordPress
  • Your current setup, as a list of tags or a Tag Manager export (optional)
  • The numbers that disagree, such as GA4 shows 120 and Google Ads shows 150 (optional)
  • Whether you use a cookie banner, and which tool (optional)

Helpful context (optional)

  • A Tag Manager container export, so it reads your real tags.
  • A screenshot of your data layer events.
  • Conversion counts from each platform for the same dates.

Tools and access

  • Claude, ChatGPT or Gemini: A long chat can hold your tag list and your test results, so it can tighten the plan as you go.
  • Google Tag Manager, GA4, Google Ads and Meta Events Manager: These show you the real setup and let you run each test in the plan.

Functions and deliverables

  • Conversion tracking planner: Plan or fix your ad conversion tracking across GA4, Google Ads and Meta. Get an event list, a double-count check and a step-by-step test plan.
    • A list of conversion events, each with its trigger, details to send and platforms that receive it
    • A plan for which conversion counts toward bidding and which are only for reporting
    • A plan to stop the same sale being counted twice
    • A consent and privacy section for your regions
    • A test plan for each event, with the tool to use and the result to expect
    • A ranked list of likely causes when your counts disagree
    Source: Michael Sitarzewski and Agency Agents contributors.
  • Conversion tracking setup and repair planner: Define a sale or lead. Get a plan to set up or repair event tracking across your named ad platforms.
    • Setup or repair steps
    • Event and tag list
    • Audit verdict per platform
    • Verification checklist
    Source: Corey Haines.
  • Cross-platform conversion reconciler: See why Meta, Google and GA4 report different conversions. Get a side-by-side table, the reason for each gap and a fix plan.
    • A side-by-side table with each source's definition
    • The reason for each gap, marked confirmed or possible
    • A confidence rating and what would raise it
    • A list of evidence that is missing
    • A numbered plan to fix your measurement
    Source: Daniel Agrici.
  • Google Ads purchase tracking checker: Check your Google Ads purchase tracking for double counting. Paste your conversion actions and get pass or fail on three rules, a score out of 100 and fixes.
    • Pass or fail on the three common mistakes
    • Which action should be the only primary one
    • Fix steps in order
    • A score out of 100 and how it was worked out
  • Brand profile builder: Share your website. Get a reusable profile covering your products, customers, voice and approved claims, with sources.
    • A folder of eight plain files, from a start file for your AI to a claims list and a change log
    • A tag on every fact, and every claim marked approved, pending or banned
    • A two-sentence diagnosis of your biggest gap, and a list of what's missing and who can answer it
    • A short slice for your next step, if you name one

Tasks you can use it for

  • You are launching or redesigning a website, and need a tracking plan before the first ad runs.
  • Google Ads, GA4 and your CRM show different conversion counts, and you need to know why.
  • You are moving from browser-only tracking to a server setup, or adding enhanced conversions.
  • You must check your tag setup against consent and privacy rules before a big campaign.

Limits to check before starting

  • You only need to fix Meta pixel and server events: use the Meta pixel and server events fixer.
  • You run a Shopify store and need GA4 set up: use the GA4 store setup checker or the Shopify Google tracking builder.
  • You want to explain why Meta and Google report different numbers: use the Cross-platform conversion reconciler.
  • You want a monthly health check on tracking you already trust: use the Analytics events and tracking gap review.
  • You need someone to change live tags on your site. Hand the plan to a tracking engineer or your developer.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

  • Add the pack to your AI as a skill. Or open a new chat and paste SKILL.md, then references/source-agent.md.
  • Write down what counts as a conversion, and the platforms and site type you use. Paste your tag list or a Tag Manager export if you have one.
  • If your counts disagree, paste the numbers for the same dates from each platform.
  • Say what you want, such as "Plan tracking for a launch" or "Find why GA4 and Google Ads disagree".
  • Make the changes in Tag Manager or with your developer. Then run each test in the plan and note the result.
  • Take your test results back to the agent. Ask it to check what still does not match.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/paid-media-tracking-specialist for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.