Marketing Attribution Guide
Which marketing actually drives revenue — models, blind spots, and first-party truth
- What
- Which marketing actually drives revenue — models, blind spots, and first-party truth
- Cost
- Free
- Needs
- none — guidance for marketing teams and founders
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — answers the hardest marketing question: which marketing actually drives conversions and revenue. Pillar A is interpretation: what attribution can and can't tell you, the models (first-touch, last-touch, multi-touch), the three measurement paradigms, self-reported attribution, reconciling conflicting sources ("Google/Meta says X but GA says Y"), and the blind spots — with a fork by business type. Pillar B is owning your attribution: the identity graph, closing the `identify()` gap, stitching conversions on a third-party domain, guardrails not to skip, and reporting the last mile. Produces a structured Attribution Readout (the question, source of truth, what each source says, model comparison, confidence and gaps, recommendation) with tool integrations and related skills. Distinct from influencer-marketing (lot 32, partnerships) — this one is measurement truth. Pure guidance, no paid services. By @coreyhaines31, listed here with credit to its creator. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: none — guidance for marketing teams and founders Install "Marketing Attribution Guide" for me. Which marketing actually drives revenue — models, blind spots, and first-party truth Repository: https://github.com/coreyhaines31/marketingskills/blob/main/skills/attribution/SKILL.md 1. Fetch the SKILL.md file for the coreyhaines31-attribution skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "coreyhaines31-attribution". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.