# Verify conversion tracking before launch

Paid campaigns can waste budget when conversions, UTMs, and attribution rules are inconsistent. This skill creates a practical pre-flight review and a reusable event specification from your exports and test conversion.

## Install

```bash
npx skillstore add aaron-he-zhu/conversion-signal-qa
```

## Metadata

- Status: approved
- Slug: aaron-he-zhu-conversion-signal-qa
- Version: 19.0.0
- Author version: 19.0.0
- Skillstore revision: r2
- Version status: valid
- Tree hash: 501ddbcbc7f0a3a849040e93d5984cff5af8752c886bab4089fa1d0943405407
- Author: aaron-he-zhu
- GitHub username: aaron-he-zhu
- License: Apache-2.0
- Repository: https://github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/ad/activate/conversion-signal-qa
- Ref: adcb3549b15782055d0beb6d29f113d20de08f92
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: filesystem, external\_commands, network
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/aaron-he-zhu-conversion-signal-qa
- Manifest: https://skillstore.pages.dev/api/skills/aaron-he-zhu-conversion-signal-qa/manifest

## Capabilities

- Creates a pass, fail, or needs-input pre-flight checklist for conversion tracking.
- Reviews GA4 Conversions and Traffic-acquisition exports supplied by the user.
- Builds a consistent UTM naming convention without personal data in parameters.
- Defines conversion events, values, currencies, and stable deduplication identifiers.
- Flags attribution-window mismatches, offline import gaps, and iOS-ATT modeled gaps.
- States launch readiness and routes scoring work to the related account-audit skill.

## Use Cases

- Check a campaign before launch: Review a planned Google and Meta campaign for event firing, UTM coverage, and launch blockers.
- Standardize account measurement: Create a shared UTM and conversion-event specification for a multi-channel advertising account.
- Investigate reporting differences: Identify likely UTM, attribution-window, and deduplication gaps behind differences between platform and GA4 reports.

## Prompt Templates

### Start a tracking pre-flight

```
Create a pre-launch conversion tracking checklist for my Google Ads campaign. The primary conversion is purchase.
```

### Build a UTM convention

```
Build a UTM naming convention and event specification for Google Search, Meta paid social, and LinkedIn. We track purchases and leads.
```

### Review supplied GA4 exports

```
Review my GA4 Conversions and Traffic-acquisition exports for UTM gaps and event-firing issues. Mark every check pass, fail, or needs-input.
```

### Resolve measurement prerequisites

```
Google and Meta report more conversions than GA4. Use my exports to identify tracking prerequisites, state dedup and attribution-window gaps, and produce a launch-readiness report.
```

## Limitations

- It relies on exports and test results that the user provides.
- It does not access Google Ads, Meta, GTM, or pixel APIs by default.
- It does not quantify double counting or perform incrementality analysis.
- It does not score ROAS readiness or make budget decisions.

## Best Practices

- Provide recent GA4 Conversions and Traffic-acquisition exports, plus the campaign platforms and conversion actions.
- Run one real manual test conversion before marking the account launch-ready.
- Use a single documented source of truth and keep attribution windows, currency, and timezone comparable.

## Anti Patterns

- Do not mark a missing export or test conversion as a pass.
- Do not place emails, names, or order data in UTM parameters.
- Do not treat platform-reported conversions as reconciled order counts.

## Security Audit

- Audited at: 2026-07-26T10:07:23.952\+00:00
- Summary: All 39 static findings are false positives caused by Markdown formatting, relative documentation links, and marketing terminology. The skill contains no executable commands, network requests, path traversal behavior, prompt-injection language, or evidence of data exfiltration. It explicitly treats pasted exports as untrusted and requires consent before saving results.

## Stats

- Views: 0
- Downloads: 4
- Favorites: 0
- Popularity score: 0