홈 / Skills / 브랜드·마케팅 / 마케팅 어트리뷰션 (Marketing Attribution)
브랜드·마케팅

마케팅 어트리뷰션 (Marketing Attribution)

Corey HainesMITSkill 언어: 영어
라이선스 확인됨스크립트 없음낮은 위험
데모실행 기록 · claude-sonnet-5-5 · 2026년 10월
Using the attribution skill, help me reconcile conflicting numbers for a fictional B2B SaaS with a 90-day sales cycle. Last month Google Ads reports 50 conversions, Meta reports 40, GA4 reports 60 and our CRM shows 35 closed deals. Direct traffic is 45% of sessions. What should we trust, which model should we use, and what should we do with the budget?
Skill: attribution

Attribution Readout — 2026-10-05

The question

Four tools report 35 to 60 conversions for the same month. Which number do we trust, which model do we use, and where should the budget go? This is a fictional B2B SaaS with a 90-day sales cycle.

Source of truth

The CRM, at 35 closed deals, defines how many conversions happened. It's the only system where revenue is real. The other sources only explain where those deals came from.

There is a timing problem to fix first. With a 90-day cycle, the 35 deals closed last month were mostly sourced from touches 2–4 months ago. The ad platforms' 50 and 40 are probably mostly leads, demos, or form fills in the last 30 days. So the numbers are likely not measuring the same event in the same period. Before comparing anything, confirm what each tool counts as a "conversion":

Source Probably counting Window
Google Ads (50) Lead or demo-request events, including view-through Its own attribution window
Meta (40) Same, with a generous view-through window Its own attribution window
GA4 (60) Any key event, including repeat or non-deal events Last non-direct click
CRM (35) Closed-won deals Closed last month, sourced from months earlier

What each source says

Source Reports Bias Our read
Google Ads 50 Over-claims itself, with view-through and a self-serving window Claims are inflated
Meta 40 Same bias, and likely strongest on view-through Claims are inflated
GA4 60 Counts more than deals, so likely lead-level or double-fired events, and sends unknowns to direct Not a deal count
CRM 35 Depends on what reps and forms recorded Trust for the count, not the source field

Google and Meta together claim 90 conversions against 35 real deals. Never sum them. Overlap is certain, and some of what they claim are leads that never closed. GA4's 60 above the CRM's 35 is a sign it's counting something other than closed deals. Don't try to make these tie out. Explain the gap instead.

Model comparison

Use first-touch and position-based (U-shaped) side by side, computed from CRM or warehouse data. Do not use the GA4 or Google Ads last-click or data-driven views as the decision model.

  • Last-touch will over-credit branded search and direct. Those are the final steps of a 90-day journey, not its cause.
  • Data-driven attribution needs roughly 200 conversions and 2,000 interactions a month. At 35 deals, it would likely collapse toward last-click.
  • First-touch shows what creates demand. Position-based (40/40/20) shows what created the opportunity and what closed it, which fits the B2B "created" and "closed" moments.
  • The gap between first-touch and last-touch is itself the insight. Channels that rank much higher in first-touch are your demand creators.

Confidence and gaps

  • Direct at 45% of sessions is a measurement problem, not a channel. It's probably a mix of stripped referrers, dark social, dropped UTMs, app-to-web handoffs, and people who found you elsewhere and typed your name. It most likely hides real top-of-funnel work. High confidence on this diagnosis, low confidence on the split.
  • Branded search probably harvests demand that other channels, such as Meta, content, and word of mouth, created. Segment it from non-branded before judging any search spend.
  • Offline touches, like sales conversations, events, and referrals, are invisible to MTA. This is where B2B tracking is weakest.
  • AI search is a likely contributor to the direct and branded-search inflation. See the ai-seo skill for that.
  • Sample size: 35 deals is small. One month of data can swing a lot, so look at trends over several months rather than this month's split.

Recommendation

What to trust

  1. The CRM for the deal count (35).
  2. Platform numbers only as directional trends, not as counts. If every source shows a channel rising or falling, believe the direction.
  3. Self-reported attribution as the tiebreaker where platforms fight over the same deals.

Which model
First-touch and position-based, side by side, on CRM data. Report the first-touch vs. last-touch gap every month.

Budget (moderate confidence, no big reallocations yet)

  1. Don't cut anything based on this month's last-touch view. Cutting Meta or other upper-funnel spend because it "converts less" is the classic mistake. Its effect shows up months later, as direct or branded search.
  2. Don't scale based on platform-reported conversions. Google and Meta claim 2.5× the real deals between them.
  3. Hold the total budget flat for 1–2 quarters while you fix measurement. Shift only small amounts, around 10%, toward channels that look good in both first-touch and position-based views.
  4. Judge channels on pipeline and revenue per dollar from the CRM, not on platform conversions. Use cohorts that match the 90-day lag, for example deals closed this month against spend from 90 days ago.
  5. Split branded from non-branded search. Cap branded spend if it's mostly capturing demand that already existed.

Fixes to make in the next 30 days

  1. Add "How did you first hear about us?" to the demo-request form. Use a pick-list plus free text, and write the answer to the CRM. This is the most direct way to see inside the 45% direct. Discount the shares you get, since recall favors memorable touches.
  2. Audit what each platform counts as a conversion. Align everything to a CRM-validated event such as a qualified opportunity or closed-won, and import offline conversions back to Google and Meta.
  3. Check UTM discipline and the referrer exclusions (OAuth, checkout, self-referrals) so direct shrinks to what it truly is.
  4. Write the first-touch source and a full touch path into the CRM, rolled up to the account, since one B2B deal involves several people.
  5. Fix the identify gap so that anonymous browsing is joined to the demo request. The analytics skill and first-party-tracking.md cover this.

Tiebreaker test worth running: a geo holdout or an on/off test on Meta or non-branded paid search. Because the cycle is 90 days, measure lift on pipeline created (qualified opportunities) rather than closed deals. Closed deals would take too long to read. This is what settles whether Meta and Google are both truly driving deals or just claiming them.

Bottom line: 35 is the real number. The other three are different measurements of different things, and the inflated platform counts are normal. Keep the budget stable, run first-touch and position-based together, add a self-reported question, and test incrementality before moving real money.

Real run in an isolated folder with only this skill installed. Only the Skill and Read tools were enabled, so nothing was fetched from the web and no file was written. The example is fictional. The conversion numbers are invented.

하는 일

두 갈래입니다. 해석 트랙: 어트리뷰션이 알려 줄 수 있는 것과 없는 것("모든 모델은 하나의 의견")을 설명하고, 첫 접점, 마지막 접점, 마지막 비직접, 선형, 시간 감쇠, 위치 기반, 데이터 기반 모델이 각각 어떻게 '거짓말'을 하는지 비교하며, 세 가지 측정 방식(멀티터치, 마케팅 믹스 모델링, 증분 실험)과 예산·주기에 따른 선택법을 제시합니다. "어떻게 알게 되셨나요" 같은 자기 보고 데이터, Google·Meta·GA·CRM 수치를 대조하는 방법(기준 데이터 하나 정하기, 플랫폼 수치를 합산하지 않기, 정확한 일치가 아니라 방향 보기), 사각지대(직접 유입, 브랜드 검색, 다크 소셜, AI 트래픽), 사업 유형별 기본 접근도 다룹니다. 구축 트랙: 아이덴티티 그래프를 쓴 퍼스트파티 어트리뷰션, identify() 호출, 웹훅으로 제3자 도메인의 전환 잇기, 가드레일, CRM에 유입 출처 기록하기. 참고 문서 4개가 더 깊이 다룹니다.

동작 방식

수치가 어떤 결정에 쓰이는지 묻고, 기준 데이터를 정하고, 모델을 나란히 비교한 뒤 신뢰도와 빈틈을 담은 짧은 '어트리뷰션 리포트'를 돌려줍니다.

이런 때 좋습니다

대시보드 수치가 서로 안 맞고, 예산 배분의 설득력 있는 근거가 필요한 마케터.

참고 및 위험

낮은 위험:스크립트가 없는 지침 패키지로, 네트워크 접속이나 파일 쓰기가 없습니다. 구축 트랙에는 사이트 간 개인 추적과 이메일을 이용한 ID 병합이 나오고, 도구 목록에는 익명의 B2B 웹사이트 방문자를 식별하는 서비스도 있습니다. 이런 관행은 법규(GDPR, ePrivacy, CCPA 등)의 대상이며 보통 동의와 개인정보 고지가 필요합니다. 스킬은 개인 ID가 제3자 URL로 넘어가지 않도록 익명성 가드레일을 추가했지만 법률 자문은 아닙니다. 인용된 벤더 기준값(예: Google 데이터 기반 어트리뷰션의 최소 요건)은 시간이 지나며 바뀝니다. 일부 링크는 이 패키지에 없는 도구 가이드를 가리킵니다. 가상의 수치로 한 번 시험 실행했습니다.