[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ACXJM9D5BA4Z2KBECG8K6S":3,"skill-same:01M7ACXJM9D5BA4Z2KBECG8K6S":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":6,"updatedAt":35,"install":36,"resources":49},"01M7ACXJM9D5BA4Z2KBECG8K6S","conversion-tracking",null,"Set up, audit, verify, or fix conversion delivery for forms, bookings, signups, calls, and purchases across analytics and ad platforms. Use for GTM\u002Fpixels, CAPI, enhanced conversions, server-side delivery, missing or duplicate conversions. For tracking plans and UTMs use `analytics`; for assigning credit use `attribution`; for campaign strategy use `ads`.","iamwaqargulzar\u002FMarketing-Agent-OS","iamwaqargulzar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96654715?v=4","01M7ACMBN0TACNXY53QYG8KDF6","Waqar Gulzar","01M7ACMBNP5ZX60H8CD3JK0633",8,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fskills\u002Fconversion-tracking\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: conversion-tracking\ndescription: \"Set up, audit, verify, or fix conversion delivery for forms, bookings, signups, calls, and purchases across analytics and ad platforms. Use for GTM\u002Fpixels, CAPI, enhanced conversions, server-side delivery, missing or duplicate conversions. For tracking plans and UTMs use `analytics`; for assigning credit use `attribution`; for campaign strategy use `ads`.\"\nlicense: Apache-2.0\nmetadata:\n  version: \"1.0.0\"\n  domain: \"paid-measurement\"\n  provenance: \"marketing-agent-os\"\n---\n\n# Conversion Tracking\n\nMeasure the defined business outcome and verify its delivery, rather than equating a tag firing with a received conversion. Read `references\u002Fskill-contract.md` for evidence, permissions, and handoffs.\n\n## Scope and permissions\n\nStart with the exact user-named site\u002Fproperty, desired outcome, destinations, existing implementation, and available evidence. Read relevant product context when present; do not invent missing setup or explore unrelated connected accounts.\n\nA diagnosis request authorizes investigation, not implementation. A live form submission, booking, order, test conversion, tag publication, account edit, or upload can change records and bidding signals. Use an authorized staging\u002Fsandbox fixture where possible; obtain explicit scope for real submissions and writes. Report a blocked validation step instead of manufacturing a receipt.\n\n## Setup or audit\n\n1. Define the conversion precisely: accepted lead, confirmed booking, account created, paid order, qualified opportunity, or another specified outcome. A phone-link click measures click intent, not a completed call; a file click does not prove a completed download.\n2. Inventory existing browser tags, native platform integrations, backend events, CRM jobs, and offline uploads. Browser inspection cannot establish that no server-side sender exists. Ask for the unresolved sender inventory before adding another source.\n3. Locate the authoritative success signal. Prefer the backend\u002Forder\u002Faccepted-submission record when available. Otherwise use the provider's documented success callback\u002Fevent for the installed version. Do not substitute submit clicks, popup close, page exit, or an unguarded thank-you-page visit.\n4. Check existing consent handling, destination eligibility, field provenance, event\u002Fvalue\u002Fcurrency mapping, identifiers, deduplication, and error\u002Fretry behavior. Do not put raw contact details in URLs, analytics events, console output, or generic dataLayer payloads. Hashing does not remove permission and data-use requirements.\n5. Choose a delivery option from `references\u002Fdelivery-options.md`; preserve a working native path when adequate. A server-side sender does not bypass consent, access restrictions, or a missing success signal.\n6. For diagnosis, report the supported cause, excluded causes, unknowns, and smallest reversible proposed change. For an explicitly requested fix\u002Fsetup, implement only the authorized change and retain a rollback path.\n7. Follow `references\u002Fverification.md` to prove detection, sending, destination receipt, and deduplication separately. If account access, a safe test, or sufficient observation time is unavailable, name the exact unverified boundary.\n\n## Platform-specific work\n\nCheck current first-party documentation for the destination and installed tool version before producing a snippet, GTM import, API payload, or consent configuration. Do not retrieve or execute unreviewed remote snippets. Validate identifiers and keep secrets out of generated public assets; import\u002Fpreview is not publication.\n\nCross-origin iframe success notifications require documented origin\u002Fsource\u002Fpayload checks. The parent page cannot read arbitrary iframe contact fields. An exposed event is not permission to exfiltrate them; consider a supported native integration, provider webhook, or backend record instead.\n\nDistinguish browser receipt, accepted platform event, matched\u002Fattributed conversion, and bidding eligibility. Refunds\u002Fcancellations and primary\u002Fsecondary conversion settings depend on the destination's current supported behavior, not a universal recipe.\n\n## Output and handoff\n\nReturn the conversion definition, sender inventory, source evidence, consent\u002Fdata flow, cause or setup plan, exact authorized change, test record IDs\u002Ftimestamps, destination receipt, rollback, and remaining unknowns. Label consequential evidence `measured`, `user-provided`, `calculated`, `estimated`, or `proxy`.\n\nDo not report DONE for end-to-end tracking when only local firing is verified. Use DONE_WITH_CONCERNS for a useful partial result, BLOCKED for a hard dependency, or NEEDS_INPUT for a material choice. Hand general event\u002FUTM design to `analytics`, credit reconciliation to `attribution`, and CRM lifecycle definitions to `revops`.\n","# Conversion Tracking\n\nMeasure the defined business outcome and verify its delivery, rather than equating a tag firing with a received conversion. Read `references\u002Fskill-contract.md` for evidence, permissions, and handoffs.\n\n## Scope and permissions\n\nStart with the exact user-named site\u002Fproperty, desired outcome, destinations, existing implementation, and available evidence. Read relevant product context when present; do not invent missing setup or explore unrelated connected accounts.\n\nA diagnosis request authorizes investigation, not implementation. A live form submission, booking, order, test conversion, tag publication, account edit, or upload can change records and bidding signals. Use an authorized staging\u002Fsandbox fixture where possible; obtain explicit scope for real submissions and writes. Report a blocked validation step instead of manufacturing a receipt.\n\n## Setup or audit\n\n1. Define the conversion precisely: accepted lead, confirmed booking, account created, paid order, qualified opportunity, or another specified outcome. A phone-link click measures click intent, not a completed call; a file click does not prove a completed download.\n2. Inventory existing browser tags, native platform integrations, backend events, CRM jobs, and offline uploads. Browser inspection cannot establish that no server-side sender exists. Ask for the unresolved sender inventory before adding another source.\n3. Locate the authoritative success signal. Prefer the backend\u002Forder\u002Faccepted-submission record when available. Otherwise use the provider's documented success callback\u002Fevent for the installed version. Do not substitute submit clicks, popup close, page exit, or an unguarded thank-you-page visit.\n4. Check existing consent handling, destination eligibility, field provenance, event\u002Fvalue\u002Fcurrency mapping, identifiers, deduplication, and error\u002Fretry behavior. Do not put raw contact details in URLs, analytics events, console output, or generic dataLayer payloads. Hashing does not remove permission and data-use requirements.\n5. Choose a delivery option from `references\u002Fdelivery-options.md`; preserve a working native path when adequate. A server-side sender does not bypass consent, access restrictions, or a missing success signal.\n6. For diagnosis, report the supported cause, excluded causes, unknowns, and smallest reversible proposed change. For an explicitly requested fix\u002Fsetup, implement only the authorized change and retain a rollback path.\n7. Follow `references\u002Fverification.md` to prove detection, sending, destination receipt, and deduplication separately. If account access, a safe test, or sufficient observation time is unavailable, name the exact unverified boundary.\n\n## Platform-specific work\n\nCheck current first-party documentation for the destination and installed tool version before producing a snippet, GTM import, API payload, or consent configuration. Do not retrieve or execute unreviewed remote snippets. Validate identifiers and keep secrets out of generated public assets; import\u002Fpreview is not publication.\n\nCross-origin iframe success notifications require documented origin\u002Fsource\u002Fpayload checks. The parent page cannot read arbitrary iframe contact fields. An exposed event is not permission to exfiltrate them; consider a supported native integration, provider webhook, or backend record instead.\n\nDistinguish browser receipt, accepted platform event, matched\u002Fattributed conversion, and bidding eligibility. Refunds\u002Fcancellations and primary\u002Fsecondary conversion settings depend on the destination's current supported behavior, not a universal recipe.\n\n## Output and handoff\n\nReturn the conversion definition, sender inventory, source evidence, consent\u002Fdata flow, cause or setup plan, exact authorized change, test record IDs\u002Ftimestamps, destination receipt, rollback, and remaining unknowns. Label consequential evidence `measured`, `user-provided`, `calculated`, `estimated`, or `proxy`.\n\nDo not report DONE for end-to-end tracking when only local firing is verified. Use DONE_WITH_CONCERNS for a useful partial result, BLOCKED for a hard dependency, or NEEDS_INPUT for a material choice. Hand general event\u002FUTM design to `analytics`, credit reconciliation to `attribution`, and CRM lifecycle definitions to `revops`.\n",{"name":5,"license":15,"metadata":24,"description":7},{"domain":25,"version":26,"provenance":27},"paid-measurement","1.0.0","marketing-agent-os","main","ad108f7eb3f6764136d02fb875772ebb34f54078","skills\u002Fconversion-tracking",2,"https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar","iamwaqargulzar.com","2026-11-03 21:14:34",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill conversion-tracking",{"tool":42,"command":43},"bunx","bunx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill conversion-tracking",{"tool":45,"command":46},"pnpm","pnpm dlx skills add iamwaqargulzar\u002FMarketing-Agent-OS --skill conversion-tracking","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fskills\u002Fconversion-tracking\u002FSKILL.md",true,[50,56,60],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fdelivery-options.md","REFERENCE","参考文档",2048,"https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fskills\u002Fconversion-tracking\u002Freferences\u002Fdelivery-options.md",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fskill-contract.md",2437,"https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fskills\u002Fconversion-tracking\u002Freferences\u002Fskill-contract.md",{"path":61,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fverification.md",2360,"https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fskills\u002Fconversion-tracking\u002Freferences\u002Fverification.md",[65,72,79,86,93,100],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7AG5VYEX7J2R2AAD54A7YT7","video","When the user wants to create, generate, or produce video content using AI tools or programmatic frameworks. Also use when the user mentions 'video production,' 'AI video,' 'Remotion,' 'Hyperframes,' 'HeyGen,' 'Synthesia,' 'Veo,' 'Sora,' 'Runway,' 'Kling,' 'Seedance,' 'Hailuo,' 'MiniMax,' 'Pika,' 'Hunyuan,' 'Wan,' 'video generation,' 'AI avatar,' 'talking head video,' 'programmatic video,' 'video template,' 'explainer video,' 'product demo video,' 'record a product demo,' 'feature demo video,' 'in-app demo,' 'video pipeline,' 'copy this edit,' 'match this video style,' 'reverse-engineer this video,' 'edit like this reference,' or 'make me a video.' Use this for video creation, generation, and production workflows. For video content strategy and what to post, see social. For paid video ad creative, see ad-creative.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fvideo\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7AG5FMXWA33FQDNS9PS1TE6","social","When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter\u002FX, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' 'viral content,' 'what should I post,' 'repurpose this content,' 'tweet ideas,' 'LinkedIn carousel,' 'social media strategy,' 'grow my following,' 'TikTok video,' 'Reels,' 'Shorts,' 'video script,' 'video hook,' 'short-form video,' 'create a reel,' 'social listening,' 'brand mentions,' 'competitor monitoring,' 'top posts to comment on,' 'find people asking for,' 'carousel,' 'slide-by-slide,' or 'document post.' Use this for social content, repurposing, scheduling, video scripts, and listening. Posts avoid AI tells like 'it's not X, it's Y' reveals and broetry. For broader content strategy, see content-strategy. For paid ads, see ad-creative. For earned media, see public-relations.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fsocial\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7AG559W96W3DGE31KXYY78S","sms","When the user wants to plan, build, or optimize SMS, MMS, or WhatsApp marketing — including welcome flows, abandoned cart texts, post-purchase, win-back, promotional sends, or transactional\u002Fauth SMS. Also use when the user mentions \"SMS marketing,\" \"text message campaigns,\" \"SMS sequence,\" \"SMS automation,\" \"abandoned cart text,\" \"post-purchase SMS,\" \"Klaviyo SMS,\" \"Postscript,\" \"Attentive,\" \"Twilio,\" \"A2P 10DLC,\" \"TCPA,\" \"SMS compliance,\" \"short code,\" \"toll-free SMS,\" \"MMS campaign,\" \"should I do SMS,\" \"SMS vs email,\" \"WhatsApp marketing,\" \"WhatsApp Business API,\" \"WhatsApp templates,\" or \"click-to-WhatsApp.\" For email sequences, see emails. For SMS copy framing, see copywriting. For opt-in popups that capture phone numbers, see popups.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fsms\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7AG4WJ9EDSECNTQN0FEAYCQ","site-architecture","When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions \"sitemap,\" \"site map,\" \"visual sitemap,\" \"site structure,\" \"page hierarchy,\" \"information architecture,\" \"IA,\" \"navigation design,\" \"URL structure,\" \"breadcrumbs,\" \"internal linking strategy,\" \"website planning,\" \"what pages do I need,\" \"how should I organize my site,\" \"site navigation,\" \"which website builder should I use,\" \"migrate my website,\" or \"add a blog to my existing site.\" Use this whenever someone is planning what pages a website should have, how they connect, and where to build them. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fsite-architecture\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7AG4MH58GRMSHC0TADAWQ69","signup","When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions \"signup conversions,\" \"registration friction,\" \"signup form optimization,\" \"free trial signup,\" \"reduce signup dropoff,\" \"account creation flow,\" \"people aren't signing up,\" \"signup abandonment,\" \"trial conversion rate,\" \"nobody completes registration,\" \"too many steps to sign up,\" or \"simplify our signup.\" Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see onboarding. For lead capture forms (not account creation), see cro.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fsignup\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7AG4CGGH35KYDFHYSS1BQZ5","seo-audit","When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions \"SEO audit,\" \"technical SEO,\" \"why am I not ranking,\" \"SEO issues,\" \"on-page SEO,\" \"meta tags review,\" \"SEO health check,\" \"my traffic dropped,\" \"lost rankings,\" \"not showing up in Google,\" \"site isn't ranking,\" \"Google update hit me,\" \"page speed,\" \"core web vitals,\" \"crawl errors,\" \"indexing issues,\" \"stuck on page 2,\" \"striking distance keywords,\" \"title tag rewrite,\" \"low CTR,\" \"local SEO,\" \"Google Business Profile,\" or \"map pack.\" Use this even if the user just says something vague like \"my SEO is bad\" or \"help with SEO\" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.","https:\u002F\u002Fgithub.com\u002Fiamwaqargulzar\u002FMarketing-Agent-OS\u002Fblob\u002Fmain\u002Fupstreams\u002Fsource-d\u002Fskills\u002Fseo-audit\u002FSKILL.md",[],[]]