# Conversion tracking Human Guide

## What This Is For
The Conversion Tracking skill provides end-to-end management of Google Ads conversion measurement infrastructure. It gives the agent a clearer input/output frame for conversion optimization: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the Conversion tracking agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for conversion tracking.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the Conversion tracking guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- User asks about "conversion tracking setup" or "conversion configuration"
- User mentions "conversions not recording" or "missing conversions"
- User wants to "debug conversion tracking" or "verify tracking"
- User asks about "enhanced conversions" or "first-party data"
- User mentions "offline conversions" or "CRM import"
- User asks about "attribution modeling" or "data-driven attribution"
- User wants to "set up Google tag" or "configure gtag"
- User mentions "conversion value rules" or "conversion actions"
- User asks "why is smart bidding not working" (often tracking related)
- Validate conversion tracking monthly by comparing Google Ads data against backend/CRM records
- Use enhanced conversions to recover 5-15% of conversions lost to cookie restrictions
- Set conversion counting to "one" for lead-gen and "every" for e-commerce

## Decision Points And Nuance
The original skill emphasizes: Description, Use When, Architecture, Implementation, Integration with Buddy™ Agent, Best Practices, Platform Compatibility, Related Skills, Keywords.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- Starting without a clear audience or goal.
- Asking for a final artifact before sharing examples or constraints.
- Accepting a generic first draft without checking it against the intended use.

## Copy-And-Paste Prompt
```text
Use the Conversion tracking human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the itallstartedwithaidea/agent-skills skill entry for `conversion-tracking`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# Conversion Tracking

Part of [Agent Skills™](https://github.com/itallstartedwithaidea/agent-skills) by [googleadsagent.ai™](https://googleadsagent.ai)

## Description

The Conversion Tracking skill provides end-to-end management of Google Ads conversion measurement infrastructure. Accurate conversion tracking is the foundation of every optimization decision — without it, bid strategies, budget allocation, and keyword valuations are operating blind. This skill handles setup, validation, debugging, and attribution modeling across the full conversion stack: Google tag, enhanced conversions, offline conversion imports, and conversion value rules.

The skill covers the complete conversion action hierarchy: macro conversions (purchases, leads, sign-ups) that drive bidding, and micro conversions (page views, add-to-cart, video plays) that inform audience building and funnel analysis. It configures conversion windows, view-through settings, and counting methods (one-per-click vs. every) based on business model requirements. Enhanced conversions using first-party data (email, phone, address) are set up to recover measurement gaps caused by cookie deprecation and privacy regulations.

Attribution modeling is a critical component. The skill evaluates and configures data-driven attribution (DDA), compares it against last-click and other models, and helps advertisers understand the true value contribution of upper-funnel campaigns. For businesses with offline sales cycles, it manages the offline conversion import pipeline via CRM integration, ensuring that revenue data flows back to Google Ads for accurate ROAS calculation.

## Use When

- User asks about "conversion tracking setup" or "conversion configuration"
- User mentions "conversions not recording" or "missing conversions"
- User wants to "debug conversion tracking" or "verify tracking"
- User asks about "enhanced conversions" or "first-party data"
- User mentions "offline conversions" or "CRM import"
- User asks about "attribution modeling" or "data-driven attribution"
- User wants to "set up Google tag" or "configure gtag"
- User mentions "conversion value rules" or "conversion actions"
- User asks "why is smart bidding not working" (often tracking related)

## Architecture

```mermaid
flowchart TD
    A[Conversion Strategy Definition] --> B[Conversion Action Setup]

    B --> C[Primary Conversions\nPurchase, Lead, Sign-up]
    B --> D[Secondary Conversions\nAdd-to-Cart, Page View]

    C --> E[Google Tag Implementation]
    D --> E

    E --> F[Base Tag: gtag.js]
    E --> G[Event Snippets]
    E --> H[Google Tag Manager]

    F --> I[Enhanced Conversions]
    G --> I
    I --> I1[Email Hashing]
    I --> I2[Phone Hashing]
    I --> I3[Address Matching]

    J[CRM / Backend Data] --> K[Offline Conversion Import]
    K --> K1[Click ID Matching: GCLID]
    K --> K2[Enhanced Conversions for Leads]
    K --> K3[Store Sales Import]

    I1 --> L[Conversion Validation Engine]
    I2 --> L
    I3 --> L
    K1 --> L
    K2 --> L
    K3 --> L

    L --> M{Validation Status}
    M -->|Healthy| N[Attribution Model Configuration]
    M -->|Issues Detected| O[Debugging Pipeline]

    O --> P[Tag Diagnostics]
    O --> Q[Data Discrepancy Analysis]
    O --> R[Cross-Platform Reconciliation]

    N --> S[Data-Driven Attribution]
    N --> T[Conversion Value Rules]
    N --> U[Conversion Window Optimization]
```

## Implementation

Conversion tracking validation and debugging framework:

```javascript
async function validateConversionTracking(customerId) {
  const conversionActions = await getConversionActions(customerId);
  const tagDiagnostics = await runTagDiagnostics(customerId);
  const recentConversions = await getRecentConversions(customerId, 7);