ad-landing-tracking
Skill1 starsChanged 9 days agoMITView on GitHub
Track a paid ad click from landing page to payment: click-id and UTM allowlist, first-touch and latest-click cookies, ids carried through checkout into payment metadata, one shared event id for browser and server dedup, variant pages keyed by a fixed slug, UTM naming, safe reports, dry-run spend scripts, and a paused-first launch. Use when you build or audit ad landing pages, attribution capture, or a small paid test, and conversions do not match clicks.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- pooriaarab/skillsword for word, first seen Nov 16, 2026
Other versions1 project uses a version of this.
Word for word · 1
- pooriaarab/skills★ 1100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository335 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accept-x402-paymentsSkill
- ad-auto-optimizerSkill
- ad-conversion-hubSkill
- ad-creative-generationSkill
- ad-creative-templatesSkill
- ad-experimentsSkill
- ad-image-prompt-librarySkill
- ad-lofi-ugcSkill
- adobe-express-addonSkill
- ad-platform-credentialsSkill
- ad-research-to-creativeSkill
- ads-amazonSkill
- ads-apple-searchSkill
- ads-baiduSkill
- ads-bilibiliSkill
- ads-chatgptSkill
- ads-copilotSkill
- ads-criteoSkill
- ads-discordSkill
- ads-douyinSkill
- adsense-site-setupSkill
- ads-googleSkill
- ads-hotstarSkill
- ads-kakaoSkill
- ads-kuaishouSkill
- ads-lgSkill
- ads-lineSkill
- ads-linkedinSkill
- ads-mercadolibreSkill
- ads-meta-aiSkill
- ads-metaSkill
- ads-microsoftSkill
- ads-mojSkill
- ads-naverSkill
- ads-nextdoorSkill
- ads-outbrainSkill
- ads-perplexitySkill
- ads-pinterestSkill
- ads-quoraSkill
- ads-redditSkill
- ads-rokuSkill
- ads-samsungSkill
- ads-sharechatSkill
- ads-shopeeSkill
- ads-snapchatSkill
- ads-spotifySkill
- ads-stackadaptSkill
- ads-stravaSkill
- ads-taboolaSkill
- ads-tencentSkill
- ads-tiktokSkill
- ads-trade-deskSkill
- ads-twitchSkill
- ads-vkSkill
- ads-wazeSkill
- ads-weiboSkill
- ads-xiaohongshuSkill
- ads-xSkill
- ads-yahoo-japanSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 14 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈14
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Do not use it to pick a platform or write ad copy.
- Distinctive: line 23
Write cookies on the first touch and on new or changed params only, after consent where the law needs it.
- Distinctive: line 24
Read ids at the purchase click.
- Distinctive: line 25
Use one event id in the browser and on the server.
- Distinctive: line 27
Run every spend or upload script as a dry run first.
- Distinctive: line 33
Carry: Put the allowlisted params on the CTA link, in storage, and into checkout metadata.
- Distinctive: line 36
Read: Use one metric window for all channels.
- Distinctive: line 37
Launch: Follow the checklist below.
- Distinctive: line 38
Prove: Check pixel and server events on the live page with a clean browser.
- Distinctive: line 44
Stop at the first item that fails.
- Distinctive: line 49
Check the spend cap. Use a lifetime or total cap where the platform has one.
- Distinctive: line 50
Create the ad paused. Read back targeting, link and budget.
- Distinctive: line 51
Wait for the stop rule's minimum clicks.
- Distinctive: line 52
Read the first result on one metric window.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ad-landing-tracking
Capture every click id once, keep it until the sale, and send it back to the ad platform with one shared event id.
This skill covers the page and the pipe. For the event taxonomy and platform adapters, use ad-conversion-hub. For hypothesis design and budgets, use ad-experiments.
Use it when
- You build a landing page for paid traffic.
- Platform conversions are lower than your own counts.
- You add a variant page or a new platform to a working setup.
Do not use it to pick a platform or write ad copy.
Rules that never bend
- Allowlist the params you keep. Drop the rest.
- Write cookies on the first touch and on new or changed params only, after consent where the law needs it.
- Read ids at the purchase click. Do not stamp them at signup.
- Use one event id in the browser and on the server. Make it once.
- Show unknown as unknown. Never show it as zero.
- Run every spend or upload script as a dry run first.
- Launch every ad paused. A person activates it.
Workflow
- Capture. Keep click ids and UTM fields in two lists. Build one allowlist from both. Keep first touch for source reports and the latest Meta and Reddit click id for sending. Write cookies only after consent where the law needs it. Never store the raw query string. Details: identifiers-and-cookies.md.
- Carry. Put the allowlisted params on the CTA link, in storage, and into checkout metadata. Read them back in the payment webhook. Details: same file.
- Send. Make one event id once: derive it from a stable key, or create it in the browser and send it to the server. Use each platform's exact field name. Details: events-and-dedup.md.
- Vary. Serve each variant at a fixed slug. Put the arm in the UTM fields and a
variantparam. Details: variants-and-naming.md. - Read. Use one metric window for all channels. Keep the last good report. Details: reporting-and-launch.md.
- Launch. Follow the checklist below.
- Prove. Check pixel and server events on the live page with a clean browser. An automated browser sends nothing by default. Details: verify-events-live.md.
For page rules (canonical, no header or footer, catalog-built copy, no paid content), see ad-landing-pages.md.
Launch checklist for a small test
Stop at the first item that fails.
- Fire a test event from the browser and one from the server. Use the platform's test id. Confirm both appear and merge into one event.
- Click a live ad URL. Confirm the first-touch cookie holds the UTM fields and the latest-click cookie holds the click id.
- Buy through checkout with a test card. Confirm the webhook reads the click id from the payment metadata.
- Check the spend cap. Use a lifetime or total cap where the platform has one. Otherwise set a daily budget times the days, with an end date. Also set a hard account spend limit. A daily budget alone is not a cap.
- Create the ad paused. Read back targeting, link and budget. Compare with your plan. Activate only if all match.
- Wait for the stop rule's minimum clicks. Do not read results before that.
- Read the first result on one metric window. Check unknown cells before you read the zeros.
Failure notes
| Symptom | Likely cause | Fix |
| Click id missing after a redirect | The redirect response did not set the cookie | Set the cookie on every response path |
| Events count twice in the platform | Event ids differ, or a field name has the wrong case | Use the shared id and the exact name per side |
| Fast bounces never appear in analytics | First page view fires after hydration | Send it from the inline init script |
Page shows {{token}} | A token had no value | Replace it with a default or empty text |
| Leads vanish with no error | Login check covers the lead API | Exempt the public lead API and test as anonymous |
| Report went blank | Every row failed to measure | Keep the last good report |
| Zero pixel events in an automated check | navigator.webdriver is true or a blocker runs | Use the clean check in verify-events-live.md |
| Lead counts twice | Event names or ids differ, or the server sends Lead on repeat sign-ups | Same name and id on both sides; send Lead on first sign-up only |
What we could not find
The source review found no sample-size rule, no power analysis, no significance test and no bandit. The only stop rule is a floor on spend, conversions and return. It is not a test of significance.
For measurement design, see the measurement guide when it lands.
Unproven here: page speed budgets, cache lifetimes for ad pages, and any ranking of page structures.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

