smithery.ai

attribution

Use to define measurement, data sharing, and ROI reporting for joint campaigns.

First seen Apr 4, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,402 B
  • docs SUMMARY.md 98 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Co-marketing Attribution Playbook Skill

When to Use

  • Planning measurement strategy for joint campaigns or events.
  • Reconciling attribution discrepancies between partner analytics stacks.
  • Preparing executive or partner reports on shared pipeline/revenue impact.

Framework

  1. Taxonomy Alignment – agree on UTM structure, campaign IDs, stages, and conversion definitions.
  2. Data Exchange – determine cadence, format, security requirements, and normalization rules.
  3. Attribution Models – select methods (first/last/multi-touch, split attribution, weighted models) and document assumptions.
  4. Governance – define owners for metric updates, dispute resolution, and audit trails.
  5. Storytelling – package dashboards and narratives for stakeholders, highlighting joint impact and next steps.

Templates

  • Attribution worksheet (source → partner → funnel stage → revenue).
  • Data sharing checklist (fields, format, frequency, security).
  • Reporting deck outline (KPIs, insights, actions).

Tips

  • Run attribution dry-runs before launch to catch data gaps.
  • Include qualitative context (partner reach, brand lift) alongside quantitative metrics.
  • Pair with track-source command to keep reports consistent across cycles.