/attribution-model
Set up attribution models. Use when: multi-touch attribution, credit distribution rules, GA4 config, channel contribution.
$ npx -y skills add indranilbanerjee/digital-marketing-pro --skill attribution-model --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/attribution-model
Context preview
The summary Claude sees to decide when to auto-load this skill.
Set up attribution models. Use when: multi-touch attribution, credit distribution rules, GA4 config, channel contribution.
SKILL.md
attribution-model.SKILL.mdname: attribution-model
description: "Set up attribution models. Use when: multi-touch attribution, credit distribution rules, GA4 config, channel contribution."
/digital-marketing-pro:attribution-model
Purpose
Design and recommend a multi-touch attribution model with implementation guidance, credit distribution rules, and platform-specific configuration. Produces a complete attribution strategy tailored to the business's data maturity, sales cycle, and analytics infrastructure.
Input Required
The user must provide (or will be prompted for):
- **Sales cycle length**: Average number of days from first touchpoint to conversion (e.g., 7 days for e-commerce, 90+ days for B2B enterprise)
- **Active marketing channels**: All channels currently running — paid search, paid social, organic search, email, display, video, affiliate, direct mail, events, referral, content marketing, etc.
- **Conversion types**: The key conversion events being tracked — lead form, MQL, SQL, opportunity, customer, revenue, or e-commerce purchase
- **Data maturity level**: Current analytics sophistication — beginner (basic GA4, limited tagging), intermediate (UTM tracking, CRM integration, multi-platform), or advanced (data warehouse, CDI, unified user IDs)
- **Current analytics tools**: Platforms in use — GA4, HubSpot, Salesforce, Adobe Analytics, Mixpanel, custom data warehouse, or third-party attribution tools
- **Touchpoint volume**: Approximate monthly interactions across all channels (thousands, tens of thousands, hundreds of thousands)
- **Offline touchpoints**: Whether offline channels (trade shows, phone calls, direct mail, in-store visits, sales meetings) play a role in the customer journey
- **Budget allocation philosophy**: How budget decisions are currently made — gut feel, last-click data, blended ROAS, executive direction, or existing attribution data
- **Previous attribution approach**: Any existing attribution model in use and its known shortcomings or limitations
- **Key business questions**: What specific decisions attribution data needs to inform — budget allocation, channel investment, campaign optimization, executive reporting, or vendor evaluation
Process
1. **Load brand context**: Read `~/.claude-marketing/brands/_active-brand.json` for the active slug, then load `~/.claude-marketing/brands/{slug}/profile.json`. Apply brand voice, compliance rules for target markets (`skills/context-engine/compliance-rules.md`), and industry context. **Also check for guidelines** at `~/.claude-marketing/brands/{slug}/guidelines/_manifest.json` — if present, load restrictions and relevant category files. Check for custom templates at `~/.claude-marketing/brands/{slug}/templates/`. Check for agency SOPs at `~/.claude-marketing/sops/`. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults. 2. **Assess data maturity and touchpoint landscape**: Map all active touchpoints across channels, evaluate tracking coverage (what percentage of interactions are captured), identify user identity resolution capabilities (logged-in vs. anonymous, cross-device stitching), and score overall data readiness on a 1-5 scale. 3. **Evaluate attribution model options**: Score each model in the canonical taxonomy — see `skills/funnel-architect/attribution-models.md` (the single source for model definitions, the selection decision tree, and platform implementation notes) — against the business context on data requirements, accuracy, actionability, and implementation complexity. Do not re-derive the model list here; consume it from that reference. 4. **Recommend primary model with rationale**: Select the best-fit model based on sales cycle length, data maturity, touchpoint volume, and business questions. Provide a clear explanation of why this model fits and where it will still have blind spots. If data maturity is low, recommend a phased approach starting with a simpler model and graduating to data-driven as tracking matures. 5. **Define credit distribution rules**: Specify exactly how conversion credit is allocated — percentage per touchpoint position, time-decay half-life window, position-based weight splits (e.g., 40% first, 40% last, 20% distributed across middle), and rules for single-touch conversions vs. multi-touch journeys. 6. **Design lookback window**: Set the attribution lookback window based on sales cycle data — typically 1.5-2x the average sales cycle length. Define separate windows for click-through and view-through attribution. Justify the window length with sales cycle analysis and explain the tradeoffs of shorter vs. longer windows. 7. **Map implementation steps per analytics platform**: Create platform-specific configuration guides — GA4 attribution settings and conversion path reports, HubSpot multi-touch revenue attribution setup, Salesforce campaign influence configuration, and custom data warehouse query logic. Include step-by-step setup instructions for each tool in the stack. **GA4 truth (state this to the user):** GA4 exposes only **data-driven** and **last-click** as configurable models (the linear / time-decay / position-based / first-click menu was removed in 2023) — any other credit rule must be modelled in the warehouse/BI layer, not GA4. Also account for GA4's new **"AI Assistant"** default channel (referrals from ChatGPT, Gemini, Copilot, Perplexity, etc.) in the channel breakdown so AI-sourced conversions aren't misfiled under Referral/Direct. 8. **Identify data gaps and tracking requirements**: Audit current tracking against the recommended model's requirements — missing UTM parameters, untagged campaigns, broken cross-domain tracking, absent offline touchpoint capture, incomplete CRM integration, and consent management gaps. Prioritize fixes by impact on attribution accuracy. 9. **Create attribution reporting framework**: Design the reporting structure — attribution dashboard layout, key metrics (attributed revenue per c
Read more
name: attribution-model description: "Set up attribution models. Use when: multi-touch attribution, credit distribution rules, GA4 config, channel contribution."
/digital-marketing-pro:attribution-model
Purpose
Design and recommend a multi-touch attribution model with implementation guidance, credit distribution rules, and platform-specific configuration. Produces a complete attribution strategy tailored to the business's data maturity, sales cycle, and analytics infrastructure.
Input Required
The user must provide (or will be prompted for):
- **Sales cycle length**: Average number of days from first touchpoint to conversion (e.g., 7 days for e-commerce, 90+ days for B2B enterprise)
- **Active marketing channels**: All channels currently running — paid search, paid social, organic search, email, display, video, affiliate, direct mail, events, referral, content marketing, etc.
- **Conversion types**: The key conversion events being tracked — lead form, MQL, SQL, opportunity, customer, revenue, or e-commerce purchase
- **Data maturity level**: Current analytics sophistication — beginner (basic GA4, limited tagging), intermediate (UTM tracking, CRM integration, multi-platform), or advanced (data warehouse, CDI, unified user IDs)
- **Current analytics tools**: Platforms in use — GA4, HubSpot, Salesforce, Adobe Analytics, Mixpanel, custom data warehouse, or third-party attribution tools
- **Touchpoint volume**: Approximate monthly interactions across all channels (thousands, tens of thousands, hundreds of thousands)
- **Offline touchpoints**: Whether offline channels (trade shows, phone calls, direct mail, in-store visits, sales meetings) play a role in the customer journey
- **Budget allocation philosophy**: How budget decisions are currently made — gut feel, last-click data, blended ROAS, executive direction, or existing attribution data
- **Previous attribution approach**: Any existing attribution model in use and its known shortcomings or limitations
- **Key business questions**: What specific decisions attribution data needs to inform — budget allocation, channel investment, campaign optimization, executive reporting, or vendor evaluation
Process
1. **Load brand context**: Read `~/.claude-marketing/brands/_active-brand.json` for the active slug, then load `~/.claude-marketing/brands/{slug}/profile.json`. Apply brand voice, compliance rules for target markets (`skills/context-engine/compliance-rules.md`), and industry context. **Also check for guidelines** at `~/.claude-marketing/brands/{slug}/guidelines/_manifest.json` — if present, load restrictions and relevant category files. Check for custom templates at `~/.claude-marketing/brands/{slug}/templates/`. Check for agency SOPs at `~/.claude-marketing/sops/`. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults. 2. **Assess data maturity and touchpoint landscape**: Map all active touchpoints across channels, evaluate tracking coverage (what percentage of interactions are captured), identify user identity resolution capabilities (logged-in vs. anonymous, cross-device stitching), and score overall data readiness on a 1-5 scale. 3. **Evaluate attribution model options**: Score each model in the canonical taxonomy — see `skills/funnel-architect/attribution-models.md` (the single source for model definitions, the selection decision tree, and platform implementation notes) — against the business context on data requirements, accuracy, actionability, and implementation complexity. Do not re-derive the model list here; consume it from that reference. 4. **Recommend primary model with rationale**: Select the best-fit model based on sales cycle length, data maturity, touchpoint volume, and business questions. Provide a clear explanation of why this model fits and where it will still have blind spots. If data maturity is low, recommend a phased approach starting with a simpler model and graduating to data-driven as tracking matures. 5. **Define credit distribution rules**: Specify exactly how conversion credit is allocated — percentage per touchpoint position, time-decay half-life window, position-based weight splits (e.g., 40% first, 40% last, 20% distributed across middle), and rules for single-touch conversions vs. multi-touch journeys. 6. **Design lookback window**: Set the attribution lookback window based on sales cycle data — typically 1.5-2x the average sales cycle length. Define separate windows for click-through and view-through attribution. Justify the window length with sales cycle analysis and explain the tradeoffs of shorter vs. longer windows. 7. **Map implementation steps per analytics platform**: Create platform-specific configuration guides — GA4 attribution settings and conversion path reports, HubSpot multi-touch revenue attribution setup, Salesforce campaign influence configuration, and custom data warehouse query logic. Include step-by-step setup instructions for each tool in the stack. **GA4 truth (state this to the user):** GA4 exposes only **data-driven** and **last-click** as configurable models (the linear / time-decay / position-based / first-click menu was removed in 2023) — any other credit rule must be modelled in the warehouse/BI layer, not GA4. Also account for GA4's new **"AI Assistant"** default channel (referrals from ChatGPT, Gemini, Copilot, Perplexity, etc.) in the channel breakdown so AI-sourced conversions aren't misfiled under Referral/Direct. 8. **Identify data gaps and tracking requirements**: Audit current tracking against the recommended model's requirements — missing UTM parameters, untagged campaigns, broken cross-domain tracking, absent offline touchpoint capture, incomplete CRM integration, and consent management gaps. Prioritize fixes by impact on attribution accuracy. 9. **Create attribution reporting framework**: Design the reporting structure — attribution dashboard layout, key metrics (attributed revenue per c
Your agency just signed a 50-brand client. The previous agency left no playbook. Three brands are bleeding budget, two have stale positioning, one is launching in a regulated jurisdiction next month. Where do you start?
Other skills on digital-marketing-pro.
- /ab-test-plan
Design A/B and multivariate tests. Use when: sample size calculation, testing hypothesis, CRO experimentation.
Open skill - /ad-creative
Generate platform-specific ad copy. Use when: Google RSA, Meta, LinkedIn, TikTok ad variations with quality scoring.
Open skill - /add-integration
Add MCP server integrations. Use when: connecting a custom tool, API, or service to the plugin via .mcp.json.
Open skill - /aeo-audit
Audit AI search visibility. Use when: checking brand presence in ChatGPT, Perplexity, AI Overviews, Gemini.
Open skill - /aeo-geo
Optimize AI engine visibility. Use when: AEO/GEO strategy, citation optimization, entity consistency across AI platforms.
Open skill - /agency-dashboard
Portfolio-level agency dashboard aggregating health metrics across all client brands — campaign status, budget pacing, KPI attainment, team utilization. Use when reviewing cross-brand portfolio health, preparing for agency leadership standups, or getting a single-view snapshot
Open skill

