linkedin-revenue-attribution

linkedin-revenue-attribution is a skill for Claude Code from Ad-Superpowers/ad-superpowers-plugin. It costs 111 tokens per session (5,519 once invoked), scanned A, original, MIT.

A guide to connecting LinkedIn advertising activity with customer relationship management (CRM) data and revenue. It explains how to measure LinkedIn's contribution across a B2B sales journey, where several people and interactions may influence one sale.

In plain words
What is it for?
Use it to plan revenue attribution, connect campaign data with CRM records, measure pipeline impact, and prepare reports for business leaders.
Why use it?
It helps businesses move beyond counting clicks or leads and report whether advertising contributes to sales pipeline and revenue. This makes long, multi-step B2B buying journeys easier to analyse.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the ad-superpowers plugin — 120 skills, 35 commands, 5 agents, 1 MCP server shipped together

Good fit Use it to plan revenue attribution, connect campaign data with CRM records, measure pipeline impact, and prepare reports for business leaders.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ad-superpowers/ad-superpowers-plugin/linkedin-revenue-attribution
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Ad-Superpowers/ad-superpowers-plugin --skill linkedin-revenue-attribution
Clone the repo
git clone --depth 1 https://github.com/Ad-Superpowers/ad-superpowers-plugin

Made for: Claude Code.

Or install ad-superpowers, the plugin that ships this one along with the rest of its 120 skills, 35 commands, 5 agents, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for linkedin-revenue-attribution

README.md
[![agentmods](https://agentmods.dev/badge/skills/ad-superpowers/ad-superpowers-plugin/linkedin-revenue-attribution/github.svg)](https://agentmods.dev/skills/ad-superpowers/ad-superpowers-plugin/linkedin-revenue-attribution)
Your own site
<a href="https://agentmods.dev/skills/ad-superpowers/ad-superpowers-plugin/linkedin-revenue-attribution"><img src="https://agentmods.dev/badge/skills/ad-superpowers/ad-superpowers-plugin/linkedin-revenue-attribution/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for linkedin-revenue-attribution

Your own site · 80×15
<a href="https://agentmods.dev/skills/ad-superpowers/ad-superpowers-plugin/linkedin-revenue-attribution"><img src="https://agentmods.dev/badge/skills/ad-superpowers/ad-superpowers-plugin/linkedin-revenue-attribution.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 111 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,519 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00111 $0.05519
Opus 5.5 $0.00044 $0.02208
Sonnet 5.5 $0.00022 $0.01104
Haiku 4.5 $0.00011 $0.00552

Measured 1mo ago against content hash 80502eb8f445, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

linkedin-revenue-attribution scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugin/skills/linkedin-revenue-attribution/SKILL.md · 617 lines

How it starts

The opening of the file, as written. The whole thing — 617 lines — stays where its author put it; the contents beside it link to each section on GitHub.

LinkedIn Revenue Attribution

Purpose

Connect LinkedIn Ads to actual revenue and prove B2B ROI. This skill helps advertisers navigate the complex world of B2B attribution, integrate CRM data with LinkedIn, and build executive-ready reporting that demonstrates LinkedIn's true pipeline impact.

The B2B Attribution Challenge

┌─────────────────────────────────────────────────────────────────────────────┐
│                    WHY B2B ATTRIBUTION IS HARD                               │
├─────────────────────────────────────────────────────────────────────────────┤
│                                                                              │
│  THE B2B BUYER JOURNEY (typical 90-200+ day cycle)                          │
│  ─────────────────────────────────────────────────                          │
│                                                                              │
│  Day 1: CMO sees LinkedIn ad while scrolling                                │
│  Day 7: CFO sees retargeting ad, mentions to CMO                            │
│  Day 14: CMO Googles brand, visits website                                  │
│  Day 30: Sales gets inbound inquiry                                         │
│  Day 45: First sales call                                                   │
│  Day 60: Product demo                                                       │
│  Day 90: Proposal sent                                                      │
│  Day 120: Negotiation                                                       │
│  Day 150: Closed-won                                                        │
│                                                                              │
│  WHO GETS CREDIT?                                                           │
│  ─────────────────                                                          │
│  LinkedIn: Created awareness, influenced multiple stakeholders              │
│  Google: Got the last click (brand search)                                  │
│  Sales: Closed the deal                                                     │
│                                                                              │
│  In-platform attribution (LinkedIn Insight Tag):                            │
│  └─ Captures: Day 1-14 (maybe)                                              │
│  └─ Misses: Day 15-150 (entire sales cycle!)                                │
│                                                                              │
│  KEY INSIGHT:                                                               │
│  ═══════════                                                                │
│  LinkedIn's in-platform metrics capture only 20-30% of true impact.        │
│  CRM integration is REQUIRED to see the full picture.                      │
│                                                                              │
└─────────────────────────────────────────────────────────────────────────────┘

Read the full file on GitHub · 617 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 617 lines · 111 tokens per session scan A 80502eb8f445

Subscribe to this mod's changes

linkedin-revenue-attribution is a skill published in the GitHub repository Ad-Superpowers/ad-superpowers-plugin (5 stars, last pushed 29d ago), licensed MIT. It adds 111 tokens to every session and 5,519 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-11.

Related

Other skills, from other repositories

analytics

Growth analytics authority — GA4 event tracking, conversion funnels, attribution models, cohort analysis, A/B testing, Supabase analytics queries, and revenue reporting patterns.

LuuOW/meridian-mcp · 33 tokens

creative-generate

A workflow for creating advertising images and banners from a strategy brief. It separates the main visual artwork from the accurately typeset text and produces variants for display or social formats.

logly/mureo · 131 tokens

cro-optimizer

CRO specialist that pulls live analytics data via the Humblytics MCP, analyzes conversion funnels, identifies drop-off points, and generates prioritized A/B test hypotheses. Use when analyzing conversion rates, diagnosing funnel leaks, optimizing signup flows, or creating test roadmaps. Triggers: CRO, conversion rate…

Humblytics/humblytics-marketing-skills · 76 tokens

learn

Save a marketing diagnosis insight to the pro-diagnosis knowledge base so it is applied in future operations across all platforms. Use when the user runs /learn, explicitly teaches the agent a marketing insight, corrects the agent's analysis, or asks to remember/record an operational learning for next time. Also use…

logly/mureo · 98 tokens

lead-form-create

Create a Meta Instant Form (Lead Ad form) through a one-question-at-a-time interview. Use when the user asks to create a lead form, Instant Form, CV form, or similar. The agent collects required parameters via a guided dialogue, confirms, then calls metaadsleadformscreate. Also use when the user asks in Japanese…

logly/mureo · 93 tokens

ai-hive-simulate-dn-samuel

A research and content-planning workflow that studies DN-Samuel's public material and turns its general methods into original work using your own facts and experience. It can also organise authorised documents into a source-linked reference library.

wubin1836/ai-hive-agent-skills · 334 tokens