Token导航 LogoToken导航

Agent Skill · 研究检索

attribution-modeling(归因建模)

attribution-modeling 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

attribution-modeling 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 55,410。

总安装 480周安装 20GitHub Stars 19下载 160核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:attribution-modeling(归因建模)
来源仓库:https://github.com/finsilabs/awesome-ecommerce-skills
仓库路径:skills/attribution-modeling
安装命令:
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill attribution-modeling
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill attribution-modeling

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

attribution-modeling 指导搭建第一方归因系统,解决第三方平台数据孤岛与夸大转化问题。适用于电商平台、独立站运营及自有 App 增长团队的数据资产沉淀需求。对比不同归因模型优劣,推荐适合当前数据成熟度的实施方案与工具选型建议。

强调无需自建复杂架构,可直接对接 Adjust、AppsFlyer 等专业归因服务商接口。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/attribution-modeling

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill att…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

attribution-modeling 怎么安装?

在终端执行 npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill attribution-m…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

attribution-modeling 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

attribution-modeling 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

attribution-modeling 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

attribution-modeling 用的人多吗?

公开数据是累计安装 480 次,近一周安装 20 次,下载 160 次,GitHub 19 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

attribution-modeling 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
attribution-modeling

归因建模 · 本页

48019需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Attribution Modeling

Overview

Attribution modeling determines which marketing touchpoints receive credit for a conversion, enabling informed decisions about where to allocate ad spend. Every ad platform (Meta, Google, TikTok) reports attribution using its own model — typically claiming 100% credit — which means the sum of all platform-reported revenue routinely exceeds your actual revenue.

This skill guides you through setting up first-party attribution on your platform, comparing attribution models side by side, and using dedicated attribution tools that do this automatically without building custom pipelines.

When to Use This Skill

  • When marketing channels (Google Ads, Meta, email) each claim different shares of the same revenue
  • When needing to make budget allocation decisions across acquisition channels
  • When moving beyond last-click attribution to understand the full customer journey
  • When building a marketing analytics report that compares channel performance under multiple attribution models
  • When implementing first-party attribution to replace data lost from iOS tracking changes
  • When affiliate, influencer, and paid search all contributed to the same order and each claims 100% credit

Core Instructions

Step 1: Determine your platform and choose the right attribution tool

PlatformRecommended ToolWhy
ShopifyTriple Whale or NorthbeamBoth built specifically for Shopify DTC brands; pull order data via API, de-duplicate cross-platform attribution, and show first-party blended ROAS
Shopify (budget)Shopify Analytics built-in attribution + UTM trackingFree; shows last-click attribution by UTM source for all orders
WooCommerceMetorik + GA4 attributionMetorik adds UTM tracking to WooCommerce orders; GA4 provides data-driven attribution model
BigCommerceRockerbox or NorthbeamBoth support BigCommerce via API integration; provide multi-touch attribution dashboards
All platforms (mid-market)Rockerbox or AffluentPlatform-agnostic; pull ad spend from all channels and match to first-party order data
Custom / HeadlessBuild on Segment + dbt or use Triple Whale's pixel APICapture touchpoints with Segment, store in warehouse, model attribution in dbt

Step 2: Set up UTM tracking correctly across all channels

Good attribution starts with consistent UTM parameters. Without them, 40–60% of traffic appears as "direct" (dark traffic).

UTM naming conventions to enforce across your team:

ParameterExampleRule
utm_sourcegoogle, meta, klaviyoAlways lowercase; never Google or GOOGLE
utm_mediumcpc, email, socialStandardized list; no custom variants
utm_campaignspring-sale-2026Consistent format across platforms

Platform-specific setup:

  • Google Ads: Enable auto-tagging (adds gclid automatically); also add UTM parameters under Campaign → Settings → Additional settings → Campaign URL options
  • Meta Ads: Add UTM parameters under Ad Set → Website URL, or use Meta's URL parameters feature at the account level
  • Klaviyo: Go to Account → Settings → UTM Tracking — enable automatic UTM appending for all email and SMS campaigns
  • Affiliates/influencers: Generate unique UTM links per creator using a URL builder; track in a spreadsheet

Step 3: Configure attribution in your chosen tool


Shopify

Option A: Built-in Shopify Analytics (last-click, free)

  1. Go to Analytics → Reports → Sessions over time
  2. Filter by Referral source to see which UTM sources drove sessions
  3. Go to Analytics → Reports → Sales by traffic source for revenue by channel (last-click attribution)
  4. Limitation: Shopify's built-in attribution is last-click only with a 30-day window; it cannot show multi-touch paths

Option B: Triple Whale (recommended for DTC brands spending $50K+/mo on ads)

  1. Install Triple Whale from the Shopify App Store
  2. Triple Whale's pixel fires on every page load, capturing the full click path before purchase
  3. Go to Triple Whale → Attribution to see revenue under four models side by side: first-click, last-click, linear, and Triple Whale's own blended model
  4. Connect your ad accounts (Meta, Google, TikTok) under Integrations — Triple Whale then compares your platform-reported ROAS against first-party-attributed ROAS
  5. Use the Summary Dashboard for a daily view of true ROAS by channel

Option C: Polar Analytics (mid-market, more affordable)

  1. Install Polar Analytics from the Shopify App Store
  2. Connect ad accounts under Integrations
  3. Polar provides first-party attribution with multiple models and a "blended ROAS" metric that accounts for all channels

WooCommerce

Using Metorik + GA4

  1. Install Metorik (metorik.com) and connect to your WooCommerce store
  2. Metorik captures UTM parameters on every order automatically — no additional plugin needed once configured
  3. In Metorik, go to Reports → UTM to see orders and revenue by utm_source, utm_medium, and utm_campaign (last-click)
  4. For multi-touch attribution, pair Metorik with Google Analytics 4:

- Install GA4 via Site Kit by Google or MonsterInsights plugin - In GA4, go to Advertising → Attribution to configure the attribution model (last click, first click, linear, data-driven) - GA4's data-driven attribution requires 400+ conversions per month to activate

Alternative: WooCommerce Google Analytics plugin (free)

  • Tracks ecommerce events automatically; provides last-click channel attribution in GA4

BigCommerce
  1. In BigCommerce, go to Storefront → Script Manager and add your attribution tool's pixel
  2. Rockerbox (recommended): Installs via script; pulls BigCommerce orders via API to match to ad touchpoints; provides first-party attribution dashboard
  3. Built-in BigCommerce analytics (Analytics → Marketing) shows traffic sources by last-click session; limited to top-level source/medium
  4. For deeper analysis, connect BigCommerce to Google Analytics 4 via the official BigCommerce GA4 integration in Apps → Google

Custom / Headless

For headless storefronts, capture touchpoints server-side and store them with orders. Then model attribution in a data warehouse:

Step 1 — Capture UTM touchpoints on every visit:

// Client-side: capture and store UTM params in localStorage on every page load
function captureUTMTouchpoint() {
  const params = new URLSearchParams(window.location.search);
  if (!params.get('utm_source') && !params.get('gclid') && !params.get('fbclid')) return;

  const touchpoints = JSON.parse(localStorage.getItem('utm_touchpoints') || '[]');
  touchpoints.push({
    source: params.get('utm_source') ?? inferSource(document.referrer),
    medium: params.get('utm_medium') ?? 'organic',
    campaign: params.get('utm_campaign') ?? '(none)',
    touchedAt: new Date().toISOString(),
    landingPage: window.location.pathname,
  });
  // Keep last 10 touchpoints (30-day look-back)
  localStorage.setItem('utm_touchpoints', JSON.stringify(touchpoints.slice(-10)));
}

Step 2 — Attach touchpoints to the order at checkout:

// Send stored touchpoints with the order creation request
const touchpoints = JSON.parse(localStorage.getItem('utm_touchpoints') || '[]');
await createOrder({ ...orderData, marketingTouchpoints: touchpoints });

Step 3 — Store and model attribution in your data warehouse:

Export to BigQuery or Snowflake via Fivetran or Stitch, then build attribution models in dbt. Use a dbt package like dbt-attribution or write your own last-click, linear, and time-decay models against your orders + touchpoints tables.

Step 4: Compare attribution models and act on the data

Run these comparisons monthly to guide budget decisions:

What to compareHow to interpret
Platform ROAS vs. first-party ROASIf platform ROAS is 5x but first-party is 2x, the channel is getting over-credited from view-through attribution
Last-click vs. linear (all-touch)Channels that appear stronger under linear are likely assisting conversions that get credited elsewhere under last-click
First-touch vs. last-touchFirst-touch shows which channels drive awareness; last-touch shows which channels close sales

Rule of thumb: If Meta claims $200K in attributed revenue and Google claims $180K, but your total revenue was $250K, you have significant attribution overlap. Use a first-party tool (Triple Whale, Rockerbox) to de-duplicate and get a realistic picture.

Best Practices

  • Always compare multiple models — no single attribution model is "correct"; the comparison reveals which channels are over/under-credited in your current setup
  • Use first-party data for attribution — iOS privacy changes have made third-party pixel attribution unreliable; server-side UTM tracking is now essential
  • Standardize UTM naming conventions strictly — utm_source=google and utm_source=Google are treated as different channels; enforce lowercase and a controlled vocabulary
  • Apply a 30-day look-back window — most e-commerce conversions occur within 30 days of first touch; use this as your standard window
  • Benchmark total attributed revenue against actual revenue — the sum of first-party attributed revenue should equal total order revenue; a large gap indicates tracking gaps
  • Report blended ROAS (total revenue / total ad spend) alongside channel ROAS — blended ROAS is harder to manipulate and gives a true picture of overall marketing efficiency

Common Pitfalls

ProblemSolution
Total platform-reported revenue exceeds actual revenueThis is expected — each platform claims 100% credit; use a first-party tool (Triple Whale, Rockerbox) to de-duplicate attribution
40-60% of orders show as "direct" or "none"UTM parameters are missing from campaign links; audit your UTM setup in each ad platform; add UTMs to email footers and bio links
UTM parameters stripped by redirect domainsTest your redirect URLs; some URL shorteners strip UTM params — use Google's URL builder and verify parameters survive
Attribution shows email with very low creditEmail often appears late in conversion paths under last-click because customers come back via direct; check first-click model to see email's role in awareness
iOS privacy changes reduced Meta attribution accuracyUse Meta's Conversions API (CAPI) integration — Klaviyo and Triple Whale both support CAPI to send server-side conversion events back to Meta

Related Skills

  • @influencer-tracking
  • @affiliate-program
  • @sales-reporting-dashboard
  • @customer-analytics
  • @ab-testing-ecommerce

平台分布

Codex

32.17%
按下载量换算51

Claude

30.58%
按下载量换算49

Cursor

19.09%
按下载量换算31

Gemini CLI

8.67%
按下载量换算14

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills