Systems Lab

Agent skill

meta-attribution-window-advisor

This skill should be used when the user asks to \"choose an attribution window\", \"compare click vs view-through attribution\", \"set up incremental attribution\", or mentions \"Meta attribution settings\", \"iOS 14 attribution\", or \"attribution window configuration\".

activeSelf-containedInstructions only1,672 words

Filed under Analytics and reporting.

From Ad-Superpowers/ad-superpowers-plugin · 120 skills · 5 · pushed 2026-09-10

What it does when it runs

This skill should be used when the user asks to \"choose an attribution window\", \"compare click vs view-through attribution\", \"set up incremental attribution\", or mentions \"Meta attribution settings\", \"iOS 14 attribution\", or \"attribution window configuration\". Do NOT use for: cross-platform attribution reconciliation (use cross-platform-attribution-reconciler), CAPI setup (use capi-implementation-guide), EMQ optimization (use emq-optimizer).

Read from the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
None found.
Hosts it reaches
No third-party host appears in the skill or its bundled files.
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about meta-attribution-window-advisor

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah
git clone --depth 1 --filter=blob:none --sparse https://github.com/Ad-Superpowers/ad-superpowers-plugin.git /tmp/ad-superpowers-plugin
git -C /tmp/ad-superpowers-plugin sparse-checkout set "plugin/skills/meta-attribution-window-advisor"
mkdir -p ~/.claude/skills/meta-attribution-window-advisor
cp -R "/tmp/ad-superpowers-plugin/plugin/skills/meta-attribution-window-advisor/." ~/.claude/skills/meta-attribution-window-advisor/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

Or take the whole library

This repo ships a .claude-plugin manifest, so Claude Code can install all 120 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.

/plugin marketplace add Ad-Superpowers/ad-superpowers-plugin
/plugin

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

Reproduced in full from Ad-Superpowers/ad-superpowers-plugin/blob/9b6385d2d2d228e4dac096a1d6bc5715c04fa736/plugin/skills/meta-attribution-window-advisor/SKILL.md, which is licensed MIT (repository). 1,672 words, 41 headings.

Attribution Window Advisor

Advisor for choosing the optimal Meta Ads attribution configuration based on product, buying cycle, and goals.

January 2026 Attribution Change: Meta removed 7-day view and 28-day view attribution windows. The new default is 7-day click + 1-day view. Unique reach counts now have a 13-month retention limit. If your reports compare to periods before January 2026, expect metric discontinuities for view-based attribution.

Attribution Basics

What Is Attribution?

Attribution determines which ads receive credit for conversions and how long after interaction a conversion is still attributed.

Attribution Types:
├── Click-Through: Conversion after clicking an ad
├── View-Through: Conversion after seeing an ad (no click)
└── Engaged-View: Conversion after 10+ sec video view

Available Windows (Current)

Window TypeOptionsDefault
Click-Through1-day, 7-day7-day
View-Through1-day, None1-day
Engaged-View1-day, None1-day (if VT=1-day)

Removed (no longer available):

  • 28-day click
  • 28-day view
  • 7-day view

Attribution Window Selection

Decision Tree

WHAT IS YOUR PRODUCT/SERVICE?
│
├─► Impulse Purchases (<€50, quick decision)
│   └─► 1-day click, 1-day view
│   └─► Examples: Fast fashion, accessories, digital products
│
├─► Standard E-commerce (€50-200)
│   └─► 7-day click, 1-day view (DEFAULT)
│   └─► Examples: Clothing, electronics, home goods
│
├─► Considered Purchases (€200+, research phase)
│   └─► 7-day click, 1-day view
│   └─► Examples: Furniture, luxury items, tech
│
├─► Lead Generation (B2B/Services)
│   └─► 7-day click, 1-day view
│   └─► Long sales cycle = 7-day click minimum
│
└─► High-Ticket / Long Sales Cycle
    └─► 7-day click, 1-day view
    └─► Supplement with external attribution tools

Recommendation Matrix

ScenarioClick WindowView WindowRationale
Default (most cases)7-day1-dayBalanced data collection
Impulse/Flash sales1-day1-dayShort decision cycle
Brand awareness7-day1-dayCapture delayed action
Retargeting7-day1-dayUsers already familiar
Strict ROAS targets7-dayNoneMinimize inflated metrics
High-consideration B2B7-day1-dayResearch-heavy buying

Click-Through vs View-Through

Understanding the Difference

CLICK-THROUGH ATTRIBUTION:
├── User clicks ad
├── User converts within window
├── Conversion credited to ad
└── Stronger causation signal

VIEW-THROUGH ATTRIBUTION:
├── User sees ad (no click)
├── User converts within window (different path)
├── Conversion credited to ad
└── Measures awareness/influence

ENGAGED-VIEW (Video only):
├── User watches 10+ seconds (or 97% if <10 sec)
├── User converts within 1 day
├── Requires View-Through = 1-day
└── Middle ground between click and view

When to Use View-Through

ENABLE VIEW-THROUGH (1-day) WHEN:
├── Brand awareness is important
├── Want to measure full ad impact
├── Video ads prominent in mix
├── Upper-funnel campaigns
└── Budget for incremental reach

DISABLE VIEW-THROUGH (None) WHEN:
├── Strict ROAS accountability
├── Comparison with other channels
├── Minimizing attribution overlap
├── Focus on direct response only
└── Incremental measurement priority

View-Through Impact

View-Through Effect on Metrics:
├── ROAS: Typically 10-30% higher with VT enabled
├── Conversions: 15-40% more reported
└── CPA: Appears lower (more conversions attributed)

Note:
- VT conversions are NOT fake
- They measure brand influence
- But they are less "incremental"
- Always compare apples-to-apples

ATT Attribution Constraints

Current State (Since iOS 14.5)

App Tracking Transparency (ATT) — standard since 2021:
├── ~75-85% of iOS users opt out of tracking
├── Limited conversion visibility for opted-out users
├── Up to 72 hour delay for iOS conversions
├── Aggregated Event Measurement (AEM) for opted-out users
└── Meta uses modeled conversions to fill gaps

Practical Impact:
├── Reported conversions ~15-25% below actual
├── Data delay for iOS traffic
├── Cross-device attribution limited
└── View-through less reliable for iOS

Aggregated Event Measurement (AEM)

What AEM Does:
├── Aggregates iOS conversion data
├── Privacy-compliant measurement
├── Removes device identifiers
├── Applies modeling and noise

2025 Update:
├── 8-event limit REMOVED
├── Manual prioritization no longer needed
├── AEM now automatic for eligible events
└── Advanced Mobile Measurement (AMM) enabled

iOS Attribution Strategy

RECOMMENDED SETUP:

1. Event Configuration:
   ├── Focus on high-value events (Purchase)
   ├── CAPI implementation essential
   ├── Enable Aggregated Event Measurement
   └── No manual event ranking needed (2025+)

2. Attribution Expectations:
   ├── Accept 20-30% underreporting
   ├── Use modeled conversions
   ├── Supplement with post-purchase surveys
   └── Cross-reference with platform data

3. Optimization Approach:
   ├── Trust Meta's modeled data
   ├── Focus on trends, not absolute numbers
   ├── Compare period-over-period
   └── Use multiple measurement sources

Incremental Attribution (2025)

What Is Incremental Attribution?

Traditional Attribution:
├── Counts all conversions after ad exposure
├── Including conversions that would have happened anyway
└── Can cause overclaiming

Incremental Attribution:
├── Measures ONLY conversions CAUSED BY the ad
├── Excludes organic conversions
├── Holdout-based measurement
└── True ad effectiveness

Meta's Incremental Attribution Setting

How to Enable:
1. Campaign settings
2. Attribution section
3. Enable "Incremental Attribution"
4. Select conversion event

Impact:
├── Reported conversions LOWER (only incremental)
├── ROAS more accurate (true ad value)
├── Algorithm optimizes for incremental lift
└── Early adopters: 20%+ improvement in true ROI

When to Use Incremental Attribution

USE INCREMENTAL WHEN:
├── High retargeting spend
├── Strong organic conversion base
├── Need true incrementality measurement
├── Budget optimization priority
└── Advanced measurement maturity

STICK TO STANDARD WHEN:
├── Low conversion volume
├── New accounts/campaigns
├── Primarily prospecting
├── Need learning phase data
└── Simple measurement needs

Attribution Comparison Framework

Meta vs Google Attribution

COMPARISON NOTES:
├── Different attribution models
├── Different tracking methods
├── Overlap in conversions
└── Don't add together!

Meta Attribution:
├── People-based (logged-in users)
├── Cross-device by default
├── View-through included
└── Click: 7-day, View: 1-day

Google Ads:
├── Cookie/click-based
├── Last-click default (changing)
├── No view-through for search
└── Data-driven attribution available

RECONCILIATION:
├── Accept 20-40% overlap
├── Use holistic measurement (MMM)
├── Post-purchase surveys for truth
└── Don't optimize for one at expense of other

Multi-Touch Attribution Considerations

META'S APPROACH:
├── Single-touch (last-touch within window)
├── Full credit to last Meta touchpoint
├── No native multi-touch

FOR MULTI-TOUCH:
├── Use third-party tools (Triple Whale, Northbeam)
├── Implement Marketing Mix Modeling
├── Post-purchase surveys
└── Platform-agnostic measurement

Attribution Configuration Guide

Setup Checklist

BEFORE CONFIGURING:

□ Define conversion events
  └── What actions matter most?

□ Understand buying cycle
  └── How long from awareness to purchase?

□ Set measurement goals
  └── Volume vs. incrementality?

□ Establish baselines
  └── Current performance benchmarks

CONFIGURATION:

□ Campaign level settings
  └── Ads Manager → Campaign → Settings → Attribution

□ Consistent across campaigns
  └── Use same windows for comparison

□ Document choices
  └── Why this configuration?

Attribution Settings by Campaign Type

Campaign TypeRecommended WindowView-ThroughNotes
Prospecting7-day click1-dayCapture delayed conversions
Retargeting7-day click1-day or NoneConsider incrementality
Brand Awareness7-day click1-dayMeasure full impact
Advantage+ Catalog Ads7-day click1-dayStandard e-commerce (formerly DPA)
Lead Gen7-day click1-dayResearch-heavy decision
App Install7-day click1-dayStandard mobile

Attribution Analysis

Comparing Attribution Windows

HOW TO ANALYZE IMPACT:

1. Run comparison:
   ├── Export data with 1-day click
   ├── Export data with 7-day click
   └── Compare conversion difference

2. Calculate "extended window lift":
   ├── (7-day conversions - 1-day conversions) / 1-day conversions
   └── Shows delayed conversion rate

3. Interpret:
   ├── >50% lift: Long consideration, use 7-day
   ├── 20-50% lift: Normal, 7-day appropriate
   └── <20% lift: Quick decisions, 1-day sufficient

View-Through Impact Analysis

MEASURING VT CONTRIBUTION:

1. Compare periods:
   ├── Period A: VT enabled
   ├── Period B: VT disabled
   └── Measure conversion difference

2. Calculate VT percentage:
   ├── (VT conversions) / (Total conversions)
   └── Shows VT contribution to reported results

3. Evaluate:
   ├── >30% VT: Significant brand influence
   ├── 10-30% VT: Normal awareness contribution
   └── <10% VT: Minimal impact, consider disabling

Troubleshooting Attribution

Common Issues

IssueSymptomSolution
Conversion delaySales missing, appear laterNormal for iOS, wait 72hr
Over-attributionMore conversions than ordersCheck deduplication, VT impact
Under-attributionFewer conversions than expectedCheck pixel/CAPI, attribution window
Inconsistent dataDifferent numbers in reportsVerify date ranges, attribution settings
GA4 mismatchMeta shows more conversionsDifferent models, VT inclusion

Attribution Audit Template

# Attribution Audit

## Current Configuration
- Click window: [1-day / 7-day]
- View window: [None / 1-day]
- Incremental: [Yes / No]

## Conversion Analysis
- Reported conversions: [X]
- Platform transactions: [Y]
- Difference: [Z]%

## Attribution Window Analysis
| Window | Conversions | % of Total |
|--------|-------------|------------|
| 1-day click | [X] | [X]% |
| 2-7 day click | [Y] | [Y]% |
| 1-day view | [Z] | [Z]% |

## Recommendations
1. [Recommendation based on analysis]
2. [Additional recommendation]

## Action Items
□ [Action 1]
□ [Action 2]

MCP: Analyze Attribution Impact

# Pull conversions broken down by attribution window to understand click vs view contribution
meta_get_insights(account_id="act_XXXXX", level="campaign", fields=["spend","actions","website_purchase_roas"], date_preset="last_30d")

# Compare attribution at ad set level for the same period
meta_get_insights(account_id="act_XXXXX", level="adset", fields=["actions","cost_per_action_type","spend"], date_preset="last_7d")

Best Practices

DO:
├── Keep attribution consistent across campaigns
├── Document your attribution choices
├── Compare trends, not absolute numbers
├── Use multiple measurement sources
├── Accept some measurement uncertainty

DON'T:
├── Change attribution mid-campaign
├── Compare campaigns with different windows
├── Obsess over exact conversion counts
├── Ignore iOS measurement limitations
├── Add Meta + Google conversions together

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what meta-attribution-window-advisor does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.