Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    lead source and attribution tracker

    1

    Marketing teams struggle to justify spend when lead sources are inconsistent or windows are poorly defined.

    $2.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    lead source and attribution tracker

    lead source and attribution tracker

    Example session with this skill installed

    Analyze attribution for our Q3 leads. Use a 30-day default window and first-touch model. Check our recorded sources against the touchpoint log. Here are the files for leads, sources, and touches.

    • Read your context and instructions
    • Compiled the lead source

    I have completed the attribution analysis for Q3 using the first-touch model. All calculations were performed via the deterministic script.

    Lead Source and Attribution — Global Marketing, 2023-10-25

    1. Scope, sources and assumptions

    • Analysis Date: 2023-10-25
    • Model: first_touch
    • Scope: all_opted_in
    • Access Scope: Demand Gen Team
    • Assumptions: 30-day default window applied to E3, E4 (default).

    2. Windows and funnel

    SourceChannelApprovedWindow (days)Window origin
    E1Paid SearchTrue30user_supplied
    E2WebinarTrue45user_supplied

    Lead Funnel:

    • Supplied: 1,200
    • Excluded (Consent/Scope): 150
    • Analysed: 1,050
    • Attributed: 980
    • Unattributed: 70

    3. Credit by source and channel

    SourceLeads creditedCreditShare of attributed
    E1540540.000.5510
    E2320320.000.3265
    E3suppressedsuppressedsuppressed

    4. Model comparison

    ModelE1E2E3
    first_touch540.00320.00120.00
    last_touch410.00450.00120.00

    5. Recorded source check and proposed actions

    • Discrepancies found: 42
    • Actions:
      • ACT-001: Change Lead L-882 from 'Organic' to 'Paid Search' (Draft, requires human approval).
      • ACT-002: Change Lead L-901 from 'Unknown' to 'Webinar' (Draft, requires human approval).

    6. Warnings and exclusions

    • W-CON-001: 45 leads excluded due to missing consent flags.
    • W-SUP-002: Source E3 results suppressed in channel view due to small cell size.

    7. Interpretation and items for human review

    • Paid Search (E1) shows higher efficiency under first-touch than last-touch (computed result).
    • 7.14% of opted-in leads remain unattributed within the defined windows (computed result).
    • Management decision required: Review 42 recorded-source discrepancies before CRM sync.

    This analysis supports, and does not replace, professional judgment and management's decision.

    Next steps

    • Review the proposed_actions list to verify source changes for the 42 flagged leads.
    • Adjust the window_days in your source catalog if the 70 unattributed leads fall just outside the 30-day limit.
    • Run a linear model comparison to see how credit distributes across middle-funnel touchpoints.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Marketing teams struggle to justify spend when lead sources are inconsistent or windows are poorly defined. This skill connects leads to touchpoints using verifiable attribution models while enforcing data governance. It calculates credit distribution across first-touch, last-touch, linear, and position-based rules without modifying your live data.

    What it does

    • Multi-model attribution credits sources using first-touch, last-touch, linear, or position-based logic.
    • Window enforcement filters touchpoints against documented attribution windows per source.
    • Governance filtering automatically excludes leads based on missing consent, out-of-scope access, or provenance gaps.
    • Integrity checking compares recorded lead sources in the CRM against actual touchpoint evidence.
    • Draft generation produces proposed CRM updates as drafts for human review rather than executing live writes.

    How it works

    1. Cataloging maps your acquisition sources to specific channels, status levels, and attribution windows.
    2. Schema mapping organizes leads and touchpoints into the required JSON format using pseudonymous IDs.
    3. Execution triggers the deterministic Python script to calculate credits and apply suppression rules.
    4. Validation identifies warnings, small-cell suppressions, and discrepancies in recorded sources.

    Frameworks & tools

    The skill relies on a self-contained Python execution environment. It interfaces with CRM data via JSON schemas for leads, touchpoints, and source catalogs.

    Why this beats prompting it yourself

    Manual prompting often fails at complex fraction math across thousands of touchpoints and ignores small-cell suppression for privacy. This skill uses a deterministic script to ensure calculations remain consistent, auditable, and compliant with your defined attribution windows.

    Use cases

    • Compare how different attribution models shift credit across paid and organic channels.
    • Audit CRM data to find leads where the recorded source contradicts touchpoint logs.
    • Calculate marketing impact while strictly excluding non-consented lead data.
    • Generate batch update drafts for lead source fields based on evidence.

    Known limitations

    Does not perform lead scoring, pipeline velocity forecasting, or duplicate merging. It cannot provide legal opinions on consent validity or calculate financial ROI/CPA.

    Requires Python 3 environment for script execution. No live CRM writes; all changes are drafts. Leads must be pseudonymous. Small-cell suppression applies to results under a count of 5.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 2 days ago

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Environment Variables
    Listed2 days ago

    What's inside

    Frequently Asked Questions

    This skill automates the complex math of multi-touch attribution (First, Last, Linear, Position-based) while applying strict window and consent filters to ensure your data remains compliant and accurate. It solves the problem of inconsistent source reporting and 'dirty' data that often leads to misallocated marketing budgets.

    The skill is a self-contained Python-based environment that interfaces via JSON; it is compatible with any AI agent or platform that supports structured data ingestion and script execution. It works by mapping your specific CRM exports (Leads and Touchpoints) to its internal schema for processing.

    The skill identifies leads where the recorded source does not match the actual touchpoint evidence, flags records missing consent, and applies 'small-cell suppression' to prevent re-identification of individuals in small data sets. It acts as a governance layer to ensure your attribution reports are both audit-ready and privacy-compliant.

    Setup involves three main steps: cataloging your marketing channels with their respective attribution windows, mapping your lead/touchpoint data to the skill's JSON schema, and configuring your desired attribution model. No direct database access is required as it works with data exports to maintain a 'read-only' safety profile.

    To prevent accidental data corruption, the skill generates proposed updates in a draft format; users can then review these discrepancies and batch-upload the corrected source data back to their CRM. It does not perform live writes, ensuring you maintain a human-in-the-loop validation process.

    Your purchase includes the core deterministic Python attribution script, the JSON schema templates for data mapping, and comprehensive documentation on configuring source catalogs and attribution windows. You will also receive any bug fixes and logic updates released for this specific version.

    New in Sales & Lead Gen