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.
npx skills add BanibrataChatterjee/AwesomeSalesforceSkills --skill campaign-planning-and-attributiongit clone --depth 1 https://github.com/BanibrataChatterjee/AwesomeSalesforceSkillsWrote 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.
[](https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/campaign-planning-and-attribution)<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/campaign-planning-and-attribution"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/campaign-planning-and-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.
<a href="https://agentmods.dev/skills/banibratachatterjee/awesomesalesforceskills/campaign-planning-and-attribution"><img src="https://agentmods.dev/badge/skills/banibratachatterjee/awesomesalesforceskills/campaign-planning-and-attribution.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00113 | $0.02983 |
| Opus 5 | $0.00056 | $0.01491 |
| Sonnet 5 | $0.00023 | $0.00597 |
| Haiku 4.5 | $0.00011 | $0.00298 |
Grade A, and why
campaign-planning-and-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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Campaign Planning And Attribution
This skill activates when a practitioner needs to design Campaign Hierarchy structures for program-level ROI aggregation, configure Customizable Campaign Influence (CCI) attribution models in Salesforce, or interpret multi-touch revenue attribution data from MCAE B2B Marketing Analytics. It covers architecture decisions and configuration — not execution of individual campaigns or MCAE connector provisioning.
Before Starting
Gather this context before working on anything in this domain:
- Confirm whether Customizable Campaign Influence is enabled: Setup > Campaign Influence > enable "Customizable Campaign Influence". This is org-level and cannot be reversed without data impact.
- Confirm whether MCAE B2B Marketing Analytics Plus is licensed — this is required for time-decay and position-based (U-shaped) attribution models.
- Determine the maximum hierarchy depth needed. Salesforce supports up to 5 levels. Deeper planning hierarchies require restructuring.
- The most common wrong assumption: practitioners believe "Campaign Influence" and "Customizable Campaign Influence" are the same feature. They are not. Standard Campaign Influence uses auto-association rules; CCI requires explicit model configuration and cannot coexist cleanly with the standard version.
- Campaign Hierarchy revenue rollups (Expected Revenue, Actual Cost, Num Leads, etc.) are updated on a schedule — they are NOT real-time. Do not treat parent campaign totals as live during active campaigns.
Core Concepts
Campaign Hierarchy and Revenue Rollup
Campaign Hierarchy allows up to 5 levels of parent-child Campaign records. A "Program" sits at or near the top; individual "Tactics" (webinars, emails, ads) sit at lower levels. When a child Campaign has Actual Cost, Expected Revenue, or member count populated, Salesforce automatically rolls these up to every ancestor via scheduled batch processing. Rollup fields on the parent Campaign include:
NumberOfLeads/NumberOfConvertedLeadsNumberOfContacts/NumberOfResponsesAmountAllOpportunities/AmountWonOpportunitiesActualCost(summed from children)
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 203 lines · 113 tokens per session scan A d12683330c54
campaign-planning-and-attribution is a skill published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (3 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 113 tokens to every session and 2,983 once invoked, about $0.0006 per session on Opus 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-03.
Other skills, from other repositories
campaign-planning-and-attribution
Designing Campaign Hierarchy for program-level ROI tracking, configuring Customizable Campaign Influence (CCI) attribution models, and interpreting multi-touch attribution from MCAE B2B Marketing Analytics. Trigger keywords: campaign ROI, attribution model, campaign hierarchy, first-touch, last-touch, multi-touch…
influencer-tracking
Measure influencer campaign ROI by generating unique UTM links per creator, attributing sales, and reporting revenue against campaign spend.
v3-create-crud
A page generator for standard create, read, update, and delete screens, commonly called CRUD screens. It uses Element Plus, a Vue user-interface library, to build tables, searches, pagination, forms, and delete confirmations.
hunt-django
Hunt Django-specific vulnerabilities: DRF permission gaps, ORM injection, and admin exploitation.
v3-use-composables
Documentation for reusable Vue functions in a project, covering device detection, asynchronous dropdown data, loading screens, pagination, routing, themes, page titles, and watermarks.
v3-use-utils
Documentation for reusable utility functions in a project, including validation, date formatting, CSS variables, permissions, local storage, and tokens.