Skills conversion-signal-qa
πŸ“¦

conversion-signal-qa

v19.0.0 Content revision r2 Safe πŸ“ Filesystem accessβš™οΈ External commands🌐 Network access

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.

Supports: Claude Codex Code(CC)
πŸ₯‰ 77 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "conversion-signal-qa" from https://skillstore.io/skills/aaron-he-zhu-conversion-signal-qa.md and its manifest at https://skillstore.io/api/skills/aaron-he-zhu-conversion-signal-qa/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Test it

Using "conversion-signal-qa". Check conversion tracking for Google and Meta before launch.

Expected outcome:

  • Pre-flight status: fix first because the manual test conversion is missing.
  • UTM rule: use lowercase source and medium values with one approved vocabulary.
  • Deduplication gate: declare GA4 or ecommerce order IDs as the source of truth.

Using "conversion-signal-qa". Build a UTM and event specification for purchase and lead campaigns.

Expected outcome:

  • UTM convention with approved values for source, medium, campaign, content, and term.
  • Event specification for purchase and lead events with value, currency, and deduplication IDs.
  • A list of modeled-data and offline-import flags to monitor after launch.

Security Audit

Safe
v7 β€’ 7/26/2026 Open versioned report

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.

3
Files scanned
167
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: claude View Audit History β†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/aaron-he-zhu-conversion-signal-qa/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/aaron-he-zhu-conversion-signal-qa/security.svg)](https://skillstore.io/skills/aaron-he-zhu-conversion-signal-qa?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/aaron-he-zhu-conversion-signal-qa?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/aaron-he-zhu-conversion-signal-qa/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/aaron-he-zhu-conversion-signal-qa.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA Β· BibTeX Β· CFF)

APA citation

aaron-he-zhu. (2026). conversion-signal-qa security audit report (audit version 7) [Author version 19.0.0]. Skillstore. https://skillstore.io/skills/aaron-he-zhu-conversion-signal-qa/audits/7

BibTeX citation

@techreport{aaron-he-zhu-aaron-he-zhu-conversion-signal-qa-2026, author = {aaron-he-zhu}, title = {conversion-signal-qa security audit report (audit version 7)}, institution = {Skillstore}, year = {2026}, number = {7}, url = {https://skillstore.io/skills/aaron-he-zhu-conversion-signal-qa/audits/7}, note = {Author version 19.0.0} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "conversion-signal-qa security audit report (audit version 7)" version: "19.0.0" type: report authors: - name: "aaron-he-zhu" date-released: "2026-07-26" url: "https://skillstore.io/skills/aaron-he-zhu-conversion-signal-qa/audits/7" identifiers: - type: other value: "skillstore:aaron-he-zhu-conversion-signal-qa:audit:7" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
41
Architecture
100
Maintainability
87
Content
67
Community
91
Spec Compliance

What You Can Build

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.

Try These Prompts

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.

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.

Avoid

  • 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.

Frequently Asked Questions

Does this skill require API access?
No. It works from user-provided exports and a manual test conversion. APIs are optional conveniences.
Which platforms can it review?
It supports any paid platform when you provide the relevant exports and conversion details, including Google and Meta.
What is the main output?
It produces a tracking pre-flight checklist, a UTM convention, an event specification, and a launch-readiness statement.
Does it fix pixels or tags directly?
No. It identifies what to fix from the available evidence. It does not directly control pixel, tag-manager, or ad-platform APIs.
Does it reconcile double-counted conversions?
No. It verifies that a deduplication rule exists and flags gaps. Detailed order matching belongs to a reconciliation workflow.
Will it save my results?
It asks for permission before saving a pre-flight report or reusable specification for future sessions.

Developer Details

License

Apache-2.0

Author version

v19.0.0

Skillstore revision

r2

Ref

adcb3549b15782055d0beb6d29f113d20de08f92

Maintenance freshness

7/28/2026

Usage

3 downloads Β· 0 views

File structure

πŸ“ references/

πŸ“„ preflight-checklist.md

πŸ“„ utm-event-spec.md

πŸ“„ SKILL.md