
Attribution
Pick this one when your dashboards disagree, which for most teams is always. The skill covers two tracks: interpreting attribution (choosing among first-touch, last-touch, linear, position-based, and data-driven models, plus MMM, incrementality tests, and self-reported "how did you hear about us" data) and building your own first-party attribution, like stitching bookings back to their source. Its best feature is the refusal to pretend one number is true. It insists on showing first-touch and last-touch side by side, since the gap between them is the insight, and it's blunt that data-driven models collapse toward last-click when conversion volume is thin. It also draws clean boundaries: event tracking lives in analytics, pixels in conversion-tracking, and pipeline stages in revops. Expect a model-comparison table and reference notes on the math.
- skills.sh installs
- 45.9K
- GitHub stars
- 59.5K
- last updated
- Oct 26, 2026
Install
$ npx -y skills add coreyhaines31/marketingskills --skill attribution --agent claude-codeInstalls into .claude/skills of the current project.
Files
Attribution
You help users answer the hardest question in marketing: which of my efforts actually caused this conversion and this revenue? Attribution is where marketers lose the most money — to channels that look good in one dashboard and terrible in another, to "direct" and "branded search" that hide the real source, and to models that quietly encode an opinion as if it were fact.
This skill has two pillars. Know which one the user needs before you dive in:
- (A) Interpretation — choosing an attribution model, picking a measurement approach, and reconciling the conflicting numbers your tools report. This applies to everyone, even with zero engineering.
- (B) Own your attribution (first-party) — instrumenting and stitching attribution yourself when you control the site/app. This is the build track. Use it when the user says "I want to track this myself" or is hitting a conversion that lives on a domain they don't own.
Most requests start with (A). Reach for (B) only when they control the surface and want to build.
Sponsors
Details
- Repository
- github.com/coreyhaines31/marketingskills
- Categories
- Testing & QA, DevOps & CI/CD, AI & Agent Building, Data Science & ML, Automation & Workflows, Marketing & SEO, Sales & Marketing
- First seen
- Oct 26, 2026
More from coreyhaines31/marketingskills
All 68- Influencer Marketing45.8K
- Aso Audit17.8K
- Seo Audit250.4K
- Copywriting250.4K
- Marketing Psychology174.5K
- Content Strategy174.4K
- Ai Seo161.6K
- Copy Editing159K
- Programmatic Seo158.9K
- Marketing Ideas155.2K
- Ad Creative143.9K
- Cold Email136.1K
- Site Architecture131.3K
- Churn Prevention128.5K
- Sales Enablement126.7K
- Customer Research124K
- Revops121K
- Lead Magnets121K
- Competitor Profiling103K
- Cro100.5K
- Community Marketing97.2K
- Social95.3K
- Image95.3K
- Video94.3K