abstract agent · marketing · 26 processes · plugin 1.0.0

Conversion tracker

conversion-tracker v1

Puts the measurement on a page before anyone sends traffic to it. It places the analytics tags, writes down which actions count as a conversion, builds the tracking parameters the paid channels need, and connects the page's form to the CRM so that a submission arrives as a record someone can follow up. It then puts a real submission through the whole path and reports whether every step of it fired.

The abstract agent

What it is granted, and what it hands to a person

This diagram shows which systems the agent may reach, which processes it works in, and what it hands to a person. Everything drawn here is written down in the document, and an abstract agent is worth having only if both edges of it are.

Holds a specialist slice in build-by-talent. What this agent installs depends on the page it measures, so it works from the same layout the web-producer assembles and asks for the form fields the CRM needs while the page can still be changed. Sits in the briefing to hear what the page is supposed to make people do, and answers the roll-call before launch with whether the tracking actually fires.

The plugin

What is in the package

11 skills and the systems they need, written to version 1.1.0 of the Agent Plugins standard. Nothing in these files names a product. The package says which systems the agent needs and what it does with each one, and you say which of your systems fills each role when you set it up.

Download the package View on GitHub

conversion-tracker · 16 files · 1.0.0

com.agentcatalog.agent/NOT.mdWhat the agent does not do, and when it asks a person.

# Where this abstract agent stops

Does not build the page and does not put it live. The web-producer
assembles the page and the owner says go. Does not decide what the page
is for; the process names the action that matters and this agent makes
it countable. The analytics agent reports the numbers afterward, reading
what this agent wired up, and the accessibility-check agent scores the
page against the accessibility and technical standards. Does not set
targeting or bids, and does not decide what happens to a lead once the
CRM has it.

## What always goes to a person

- a conversion it cannot verify end to end before launch
- personal data the page collects that the consent setup does not cover
- a change to a conversion definition once results are being reported
  against it, because the numbers before and after the change stop being
  comparable

com.agentcatalog.agent/RECORDS.mdThe records the agent must leave behind.

# The records this abstract agent must leave

This is the contract. An agent implementing `conversion-tracker` leaves
the following behind, on every run.

A measurement plan at a version, naming every conversion, what counts as
one, and where it fires. For each conversion, a dated test record
showing a real submission arriving in the CRM. The tracking parameters
it handed to each paid channel, recorded against the page they belong
to. Anything it could not verify is recorded as unverified rather than
left out.

An agent that leaves less than this does not implement
`conversion-tracker`, whatever else it does well.

com.agentcatalog.agent/SERVERS.mdThe systems the agent needs, by role rather than by product.

# The systems this abstract agent needs

Four systems, named by role rather than by product. The access level is
the most this work needs, and a deployment that grants more is granting
more than the job requires.

| Role | Access | What the access is for |
|---|---|---|
| analytics platforms | write | Tags and conversion definitions land at versions. |
| the CRM | write | Cap: which objects and fields it may create, set by the adopting organization. |
| ad platform conversion settings | write | The definitions the buy optimizes toward, with no access to bids or budgets. |
| the site's pages | write | Limited to measurement code. |

Whoever builds an agent from this plugin writes the `mcp.json` that
points these roles at their own systems. Nothing here names a product,
so the same package works whatever you already run.

plugin.jsonThe manifest. It lists the skills and the systems the agent needs.

{
  "$schema": "https://agent-plugins.org/schemas/1.1.0/plugin.schema.json",
  "name": "conversion-tracker",
  "version": "1.0.0",
  "description": "The conversion-tracker abstract agent. Puts the measurement on a page before anyone sends traffic to it.",
  "author": {
    "name": "AgentCatalog",
    "url": "https://agentcatalog.com"
  },
  "homepage": "https://agentcatalog.com/abstract-agents/conversion-tracker",
  "repository": "https://github.com/jeffrschneider/agentcatalog",
  "license": "CC-BY-4.0",
  "keywords": [
    "abstract-agent",
    "reference",
    "marketing",
    "conversion-experiment",
    "landing-page",
    "nurture-sequence",
    "abstract"
  ],
  "extensions": {
    "com.agentcatalog.agent": {
      "agent": "conversion-tracker",
      "agentVersion": 1,
      "department": "marketing",
      "abstract": true,
      "works": "Holds a specialist slice in build-by-talent. What this agent installs depends on the page it measures, so it works from the same layout the web-producer assembles and asks for the form fields the CRM needs while the page can still be changed. Sits in the briefing to hear what the page is supposed to make people do, and answers the roll-call before launch with whether the tracking actually fires.",
      "servers": [
        {
          "name": "analytics platforms",
          "role": "analytics-platforms",
          "access": "write",
          "needs": "Tags and conversion definitions land at versions."
        },
        {
          "name": "the CRM",
          "role": "crm",
          "access": "write",
          "needs": "Cap: which objects and fields it may create, set by the adopting organization."
        },
        {
          "name": "ad platform conversion settings",
          "role": "ad-platform-conversion-settings",
          "access": "write",
          "needs": "The definitions the buy optimizes toward, with no access to bids or budgets."
        },
        {
          "name": "the site's pages",
          "role": "sites-pages",
          "access": "write",
          "needs": "Limited to measurement code."
        }
      ],
      "records": [
        "A measurement plan at a version, naming every conversion, what counts as one, and where it fires.",
        "For each conversion, a dated test record showing a real submission arriving in the CRM.",
        "The tracking parameters it handed to each paid channel, recorded against the page they belong to.",
        "Anything it could not verify is recorded as unverified rather than left out."
      ],
      "escalates": [
        "a conversion it cannot verify end to end before launch",
        "personal data the page collects that the consent setup does not cover",
        "a change to a conversion definition once results are being reported against it, because the numbers before and after the change stop being comparable"
      ],
      "not": [
        "Does not build the page and does not put it live.",
        "The web-producer assembles the page and the owner says go.",
        "Does not decide what the page is for; the process names the action that matters and this agent makes it countable.",
        "The analytics agent reports the numbers afterward, reading what this agent wired up, and the accessibility-check agent scores the page against the accessibility and technical standards.",
        "Does not set targeting or bids, and does not decide what happens to a lead once the CRM has it."
      ],
      "processes": [
        {
          "process": "ref/mkt/account-based-play",
          "activities": [
            "Build the Pages and the Notice"
          ]
        },
        {
          "process": "ref/mkt/attribution-model",
          "activities": [
            "Check the Tracking"
          ]
        },
        {
          "process": "ref/mkt/channel-program",
          "activities": [
            "Set up the Partner Systems"
          ]
        },
        {
          "process": "ref/mkt/co-marketing-campaign",
          "activities": [
            "Wire up the Split"
          ]
        },
        {
          "process": "ref/mkt/conversion-experiment",
          "activities": [
            "Set the Terms of the Test",
            "Brief the Makers",
            "Wire the Measurement",
            "Check the Setup",
            "Watch the Test Run",
            "Carry out the Decision"
          ]
        },
        {
          "process": "ref/mkt/customer-newsletter",
          "activities": [
            "Wire up the Measurement"
          ]
        },
        {
          "process": "ref/mkt/customer-reviews",
          "activities": [
            "Set up the Practical Side"
          ]
        },
        {
          "process": "ref/mkt/display-retargeting",
          "activities": [
            "Tag the Site"
          ]
        },
        {
          "process": "ref/mkt/field-event",
          "activities": [
            "Open Registration"
          ]
        },
        {
          "process": "ref/mkt/influencer-campaign",
          "activities": [
            "Set up the Tracking"
          ]
        },
        {
          "process": "ref/mkt/landing-page",
          "activities": [
            "Brief the Makers",
            "Wire the Tracking",
            "Hand It to the Campaign"
          ]
        },
        {
          "process": "ref/mkt/long-form-content",
          "activities": [
            "Wire up the Measurement"
          ]
        },
        {
          "process": "ref/mkt/marketing-performance-report",
          "activities": [
            "Check the Tracking"
          ]
        },
        {
          "process": "ref/mkt/media-plan",
          "activities": [
            "Settle What Counts as a Result"
          ]
        },
        {
          "process": "ref/mkt/nurture-sequence",
          "activities": [
            "Brief the Makers",
            "Wire up the Measurement",
            "Run Test Contacts Through It"
          ]
        },
        {
          "process": "ref/mkt/paid-search-campaign",
          "activities": [
            "Wire up Conversion Tracking"
          ]
        },
        {
          "process": "ref/mkt/pricing-change",
          "activities": [
            "Restate the Price Everywhere It Is Published"
          ]
        },
        {
          "process": "ref/mkt/reallocate-media-spend",
          "activities": [
            "Confirm the Numbers Hold"
          ]
        },
        {
          "process": "ref/mkt/refresh-content",
          "activities": [
            "Check the Changed Pages"
          ]
        },
        {
          "process": "ref/mkt/test-ad-creative",
          "activities": [
            "Wire up the Measurement"
          ]
        },
        {
          "process": "ref/mkt/trade-show",
          "activities": [
            "Set up Lead Capture"
          ]
        },
        {
          "process": "ref/mkt/traffic-ad-creative",
          "activities": [
            "Build the Tracking Parameters",
            "Check Every Destination",
            "Check the Live Ads"
          ]
        },
        {
          "process": "ref/mkt/user-conference",
          "activities": [
            "Open Registration"
          ]
        },
        {
          "process": "ref/mkt/webinar",
          "activities": [
            "Build the Registration Page",
            "Hand off the Leads"
          ]
        },
        {
          "process": "ref/mkt/website-content-update",
          "activities": [
            "Check the Changed Page"
          ]
        },
        {
          "process": "ref/mkt/win-back-campaign",
          "activities": [
            "Brief the Makers",
            "Wire up the Measurement"
          ]
        }
      ]
    }
  }
}

README.mdWhat the package is, and why it carries no mcp.json.

# conversion-tracker

This is an abstract agent, published as an Agent Plugin. An abstract
agent is a job description rather than an implementation. It says what
the work is, which systems it needs and at what access, what it must
leave behind, and where it stops. Any agent that leaves the records can
implement it.

The plugin carries eleven skills, no `mcp.json`, and everything the
abstract agent owes under `com.agentcatalog.agent/`.

## Why there is no mcp.json

A conformant server entry in `mcp.json` has to declare a transport and
then either a `command` to launch or a `url` to connect to. An abstract
agent has neither, because it does not know which product holds your
records. Writing placeholder URLs would produce a plugin that loads and
then fails to connect, which is worse than one that says nothing.

Section 6.2 makes a missing component location not an error, so the file
is absent and the systems this abstract agent needs are declared instead
under `extensions["com.agentcatalog.agent"].servers`, as a role, an
access level and what the access is for. Whoever builds an agent from
this plugin writes the `mcp.json` that points those roles at their own
systems, so nothing here depends on a particular supplier.

## Why the obligations are in an extension

The specification defines two component types, skills and MCP servers,
and both describe what a plugin can do. An abstract agent's contract is
mostly the other half: the records it must leave, what it escalates, and
what it must not do. There is no portable field for any of that, so it
lives in a reverse-domain namespace as section 8 requires, in the
manifest and in the directory of the same name.

## Where this abstract agent is used

`ref/mkt/account-based-play`, `ref/mkt/attribution-model`,
`ref/mkt/channel-program`, `ref/mkt/co-marketing-campaign`,
`ref/mkt/conversion-experiment`, `ref/mkt/customer-newsletter`, and 20
more. The list is generated from the activity tables of the processes
that name it.

https://agentcatalog.com/abstract-agents/conversion-tracker

skills/campaign-handover/SKILL.mdHands the finished page to the run that will send traffic to it, with its address and the tracking that goes with it, so the campaign points at the right place and reads the right numbers. Use it when running `ref/mkt/landing-page`.

---
name: campaign-handover
description: Hands the finished page to the run that will send traffic to it, with its address and the tracking that goes with it, so the campaign points at the right place and reads the right numbers. Use it when running `ref/mkt/landing-page`.
license: CC-BY-4.0
metadata:
  agent: conversion-tracker
  agent-version: "1"
---

# Campaign handover

## What it does

Hands the finished page to the run that will send traffic to it, with
its address and the tracking that goes with it, so the campaign points
at the right place and reads the right numbers.

## Where it happens

The agent does this in one activity across one reference process. Each
one names the activity as that process words it.

- **Hand It to the Campaign**
  - `ref/mkt/landing-page`, activity 12 -
    [Publish Landing Page](../../../../processes/marketing/landing-page.md)

## What to record

A measurement plan at a version, naming every conversion, what counts as
one, and where it fires. For each conversion, a dated test record
showing a real submission arriving in the CRM. The tracking parameters
it handed to each paid channel, recorded against the page they belong
to. Anything it could not verify is recorded as unverified rather than
left out.

That contract covers every activity this abstract agent takes on, and it
is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract
agent does not do is in `com.agentcatalog.agent/NOT.md`.

skills/lead-capture-and-routing/SKILL.mdConnects a form or a capture device to the systems that hold the records, decides which fields are taken and where each record goes, and delivers each record to whoever has to follow it up. Use it when running `ref/mkt/channel-program` and 3 other reference processes.

---
name: lead-capture-and-routing
description: Connects a form or a capture device to the systems that hold the records, decides which fields are taken and where each record goes, and delivers each record to whoever has to follow it up. Use it when running `ref/mkt/channel-program` and 3 other reference processes.
license: CC-BY-4.0
metadata:
  agent: conversion-tracker
  agent-version: "1"
---

# Lead capture and routing

## What it does

Connects a form or a capture device to the systems that hold the
records, decides which fields are taken and where each record goes, and
delivers each record to whoever has to follow it up.

## Where it happens

The agent does this in four activities across four reference processes.
Each one names the activity as that process words it.

- **Hand off the Leads**
  - `ref/mkt/webinar`, activity 16 -
    [Produce Webinar](../../../../processes/marketing/webinar.md)
- **Set up Lead Capture**
  - `ref/mkt/trade-show`, activity 9 -
    [Exhibit at Trade Show](../../../../processes/marketing/trade-show.md)
- **Set up the Partner Systems**
  - `ref/mkt/channel-program`, activity 9 -
    [Launch Channel Program](../../../../processes/marketing/channel-program.md)
- **Wire up the Split**
  - `ref/mkt/co-marketing-campaign`, activity 10 -
    [Run Co-Marketing Campaign](../../../../processes/marketing/co-marketing-campaign.md)

## What to record

A measurement plan at a version, naming every conversion, what counts as
one, and where it fires. For each conversion, a dated test record
showing a real submission arriving in the CRM. The tracking parameters
it handed to each paid channel, recorded against the page they belong
to. Anything it could not verify is recorded as unverified rather than
left out.

That contract covers every activity this abstract agent takes on, and it
is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract
agent does not do is in `com.agentcatalog.agent/NOT.md`.

skills/live-path-verification/SKILL.mdPuts a real click, contact or session through the whole path once it is live and reports whether every step fired, from the advertisement rendering to the record arriving in the system that has to receive it. Use it when running `ref/mkt/conversion-experiment`, `ref/mkt/nurture-sequence` and `ref/mkt/traffic-ad-creative`.

---
name: live-path-verification
description: Puts a real click, contact or session through the whole path once it is live and reports whether every step fired, from the advertisement rendering to the record arriving in the system that has to receive it. Use it when running `ref/mkt/conversion-experiment`, `ref/mkt/nurture-sequence` and `ref/mkt/traffic-ad-creative`.
license: CC-BY-4.0
metadata:
  agent: conversion-tracker
  agent-version: "1"
---

# Live path verification

## What it does

Puts a real click, contact or session through the whole path once it is
live and reports whether every step fired, from the advertisement
rendering to the record arriving in the system that has to receive it.

## Where it happens

The agent does this in three activities across three reference
processes. Each one names the activity as that process words it.

- **Check the Live Ads**
  - `ref/mkt/traffic-ad-creative`, activity 16 -
    [Traffic Ad Creative](../../../../processes/marketing/traffic-ad-creative.md)
- **Check the Setup**
  - `ref/mkt/conversion-experiment`, activity 10 -
    [Run Conversion Experiment](../../../../processes/marketing/conversion-experiment.md)
- **Run Test Contacts Through It**
  - `ref/mkt/nurture-sequence`, activity 12 -
    [Build Nurture Sequence](../../../../processes/marketing/nurture-sequence.md)

## What to record

A measurement plan at a version, naming every conversion, what counts as
one, and where it fires. For each conversion, a dated test record
showing a real submission arriving in the CRM. The tracking parameters
it handed to each paid channel, recorded against the page they belong
to. Anything it could not verify is recorded as unverified rather than
left out.

That contract covers every activity this abstract agent takes on, and it
is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract
agent does not do is in `com.agentcatalog.agent/NOT.md`.

skills/maker-brief/SKILL.mdPuts the same request in front of everyone who has to build a piece of the measurement at the same time, so nobody works from an older version of it. Use it when running `ref/mkt/conversion-experiment` and 3 other reference processes.

---
name: maker-brief
description: Puts the same request in front of everyone who has to build a piece of the measurement at the same time, so nobody works from an older version of it. Use it when running `ref/mkt/conversion-experiment` and 3 other reference processes.
license: CC-BY-4.0
metadata:
  agent: conversion-tracker
  agent-version: "1"
---

# Maker brief

## What it does

Puts the same request in front of everyone who has to build a piece of
the measurement at the same time, so nobody works from an older version
of it.

## Where it happens

The agent does this in one activity across four reference processes.
Each one names the activity as that process words it.

- **Brief the Makers**
  - `ref/mkt/conversion-experiment`, activity 5 -
    [Run Conversion Experiment](../../../../processes/marketing/conversion-experiment.md)
  - `ref/mkt/landing-page`, activity 4 -
    [Publish Landing Page](../../../../processes/marketing/landing-page.md)
  - `ref/mkt/nurture-sequence`, activity 6 -
    [Build Nurture Sequence](../../../../processes/marketing/nurture-sequence.md)
  - `ref/mkt/win-back-campaign`, activity 7 -
    [Run Win-Back Campaign](../../../../processes/marketing/win-back-campaign.md)

## What to record

A measurement plan at a version, naming every conversion, what counts as
one, and where it fires. For each conversion, a dated test record
showing a real submission arriving in the CRM. The tracking parameters
it handed to each paid channel, recorded against the page they belong
to. Anything it could not verify is recorded as unverified rather than
left out.

That contract covers every activity this abstract agent takes on, and it
is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract
agent does not do is in `com.agentcatalog.agent/NOT.md`.

skills/measurement-audit/SKILL.mdReads the measurement data itself and says how far it can be trusted, which means where touches went uncounted and for how long, and whether the figures behind a signal are real and current. Use it when running `ref/mkt/attribution-model`, `ref/mkt/marketing-performance-report` and `ref/mkt/reallocate-media-spend`.

---
name: measurement-audit
description: Reads the measurement data itself and says how far it can be trusted, which means where touches went uncounted and for how long, and whether the figures behind a signal are real and current. Use it when running `ref/mkt/attribution-model`, `ref/mkt/marketing-performance-report` and `ref/mkt/reallocate-media-spend`.
license: CC-BY-4.0
metadata:
  agent: conversion-tracker
  agent-version: "1"
---

# Measurement audit

## What it does

Reads the measurement data itself and says how far it can be trusted,
which means where touches went uncounted and for how long, and whether
the figures behind a signal are real and current.

## Where it happens

The agent does this in two activities across three reference processes.
Each one names the activity as that process words it.

- **Check the Tracking**
  - `ref/mkt/attribution-model`, activity 5 -
    [Maintain Attribution Model](../../../../processes/marketing/attribution-model.md)
  - `ref/mkt/marketing-performance-report`, activity 8 -
    [Report Marketing Performance](../../../../processes/marketing/marketing-performance-report.md)
- **Confirm the Numbers Hold**
  - `ref/mkt/reallocate-media-spend`, activity 2 -
    [Reallocate Media Spend](../../../../processes/marketing/reallocate-media-spend.md)

## What to record

A measurement plan at a version, naming every conversion, what counts as
one, and where it fires. For each conversion, a dated test record
showing a real submission arriving in the CRM. The tracking parameters
it handed to each paid channel, recorded against the page they belong
to. Anything it could not verify is recorded as unverified rather than
left out.

That contract covers every activity this abstract agent takes on, and it
is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract
agent does not do is in `com.agentcatalog.agent/NOT.md`.

skills/measurement-instrumentation/SKILL.mdPlaces the analytics tags on a page or a site and writes down which actions count as a result, so that traffic and what people do with it arrive in the reporting. Use it when running `ref/mkt/conversion-experiment` and 9 other reference processes.

---
name: measurement-instrumentation
description: Places the analytics tags on a page or a site and writes down which actions count as a result, so that traffic and what people do with it arrive in the reporting. Use it when running `ref/mkt/conversion-experiment` and 9 other reference processes.
license: CC-BY-4.0
metadata:
  agent: conversion-tracker
  agent-version: "1"
---

# Measurement instrumentation

## What it does

Places the analytics tags on a page or a site and writes down which
actions count as a result, so that traffic and what people do with it
arrive in the reporting. It respects the consent rules, so a tag fires
only where consent covers it.

## Where it happens

The agent does this in six activities across ten reference processes.
Each one names the activity as that process words it.

- **Settle What Counts as a Result**
  - `ref/mkt/media-plan`, activity 11 -
    [Develop Media Plan](../../../../processes/marketing/media-plan.md)
- **Tag the Site**
  - `ref/mkt/display-retargeting`, activity 6 -
    [Run Display Retargeting Campaign](../../../../processes/marketing/display-retargeting.md)
- **Wire the Measurement**
  - `ref/mkt/conversion-experiment`, activity 8 -
    [Run Conversion Experiment](../../../../processes/marketing/conversion-experiment.md)
- **Wire the Tracking**
  - `ref/mkt/landing-page`, activity 8 -
    [Publish Landing Page](../../../../processes/marketing/landing-page.md)
- **Wire up Conversion Tracking**
  - `ref/mkt/paid-search-campaign`, activity 6 -
    [Run Paid Search Campaign](../../../../processes/marketing/paid-search-campaign.md)
- **Wire up the Measurement**
  - `ref/mkt/customer-newsletter`, activity 10 -
    [Publish Customer Newsletter](../../../../processes/marketing/customer-newsletter.md)
  - `ref/mkt/long-form-content`, activity 12 -
    [Produce Long-Form Content](../../../../processes/marketing/long-form-content.md)
  - `ref/mkt/nurture-sequence`, activity 8 -
    [Build Nurture Sequence](../../../../processes/marketing/nurture-sequence.md)
  - `ref/mkt/test-ad-creative`, activity 11 -
    [Test Ad Creative](../../../../processes/marketing/test-ad-creative.md)
  - `ref/mkt/win-back-campaign`, activity 9 -
    [Run Win-Back Campaign](../../../../processes/marketing/win-back-campaign.md)

## What to record

A measurement plan at a version, naming every conversion, what counts as
one, and where it fires. For each conversion, a dated test record
showing a real submission arriving in the CRM. The tracking parameters
it handed to each paid channel, recorded against the page they belong
to. Anything it could not verify is recorded as unverified rather than
left out.

That contract covers every activity this abstract agent takes on, and it
is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract
agent does not do is in `com.agentcatalog.agent/NOT.md`.

skills/page-and-form-build/SKILL.mdBuilds the page a run points people at, together with the form on it, and puts the measurement on both before anyone is sent there. Use it when running `ref/mkt/account-based-play` and 3 other reference processes.

---
name: page-and-form-build
description: Builds the page a run points people at, together with the form on it, and puts the measurement on both before anyone is sent there. Use it when running `ref/mkt/account-based-play` and 3 other reference processes.
license: CC-BY-4.0
metadata:
  agent: conversion-tracker
  agent-version: "1"
---

# Page and form build

## What it does

Builds the page a run points people at, together with the form on it,
and puts the measurement on both before anyone is sent there.

## Where it happens

The agent does this in three activities across four reference processes.
Each one names the activity as that process words it.

- **Build the Pages and the Notice**
  - `ref/mkt/account-based-play`, activity 13 -
    [Run Account-Based Play](../../../../processes/marketing/account-based-play.md)
- **Build the Registration Page**
  - `ref/mkt/webinar`, activity 4 -
    [Produce Webinar](../../../../processes/marketing/webinar.md)
- **Open Registration**
  - `ref/mkt/field-event`, activity 8 -
    [Host Field Event](../../../../processes/marketing/field-event.md)
  - `ref/mkt/user-conference`, activity 7 -
    [Host User Conference](../../../../processes/marketing/user-conference.md)

## What to record

A measurement plan at a version, naming every conversion, what counts as
one, and where it fires. For each conversion, a dated test record
showing a real submission arriving in the CRM. The tracking parameters
it handed to each paid channel, recorded against the page they belong
to. Anything it could not verify is recorded as unverified rather than
left out.

That contract covers every activity this abstract agent takes on, and it
is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract
agent does not do is in `com.agentcatalog.agent/NOT.md`.

skills/page-experiments/SKILL.mdSets what a page test changes, who sees it and which measure decides it, watches delivery and the guardrail measures while it runs, and puts the answer into effect by rolling one version out to everyone or taking the change back out. Use it when running `ref/mkt/conversion-experiment`.

---
name: page-experiments
description: Sets what a page test changes, who sees it and which measure decides it, watches delivery and the guardrail measures while it runs, and puts the answer into effect by rolling one version out to everyone or taking the change back out. Use it when running `ref/mkt/conversion-experiment`.
license: CC-BY-4.0
metadata:
  agent: conversion-tracker
  agent-version: "1"
---

# Page experiments

## What it does

Sets what a page test changes, who sees it and which measure decides it,
watches delivery and the guardrail measures while it runs, and puts the
answer into effect by rolling one version out to everyone or taking the
change back out.

## Where it happens

The agent does this in three activities across one reference process.
Each one names the activity as that process words it.

- **Carry out the Decision**
  - `ref/mkt/conversion-experiment`, activity 15 -
    [Run Conversion Experiment](../../../../processes/marketing/conversion-experiment.md)
- **Set the Terms of the Test**
  - `ref/mkt/conversion-experiment`, activity 2 -
    [Run Conversion Experiment](../../../../processes/marketing/conversion-experiment.md)
- **Watch the Test Run**
  - `ref/mkt/conversion-experiment`, activity 12 -
    [Run Conversion Experiment](../../../../processes/marketing/conversion-experiment.md)

## What to record

A measurement plan at a version, naming every conversion, what counts as
one, and where it fires. For each conversion, a dated test record
showing a real submission arriving in the CRM. The tracking parameters
it handed to each paid channel, recorded against the page they belong
to. Anything it could not verify is recorded as unverified rather than
left out.

That contract covers every activity this abstract agent takes on, and it
is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract
agent does not do is in `com.agentcatalog.agent/NOT.md`.

skills/page-verification/SKILL.mdReads a page after it is built or changed and confirms it works for a visitor and for the reporting, which covers the links, the headings, how it loads, whether it meets the accessibility standard, and whether the visit is recorded. Use it when running `ref/mkt/refresh-content`, `ref/mkt/traffic-ad-creative` and `ref/mkt/website-content-update`.

---
name: page-verification
description: Reads a page after it is built or changed and confirms it works for a visitor and for the reporting, which covers the links, the headings, how it loads, whether it meets the accessibility standard, and whether the visit is recorded. Use it when running `ref/mkt/refresh-content`, `ref/mkt/traffic-ad-creative` and `ref/mkt/website-content-update`.
license: CC-BY-4.0
metadata:
  agent: conversion-tracker
  agent-version: "1"
---

# Page verification

## What it does

Reads a page after it is built or changed and confirms it works for a
visitor and for the reporting, which covers the links, the headings, how
it loads, whether it meets the accessibility standard, and whether the
visit is recorded.

## Where it happens

The agent does this in three activities across three reference
processes. Each one names the activity as that process words it.

- **Check Every Destination**
  - `ref/mkt/traffic-ad-creative`, activity 10 -
    [Traffic Ad Creative](../../../../processes/marketing/traffic-ad-creative.md)
- **Check the Changed Page**
  - `ref/mkt/website-content-update`, activity 10 -
    [Update Website Content](../../../../processes/marketing/website-content-update.md)
- **Check the Changed Pages**
  - `ref/mkt/refresh-content`, activity 18 -
    [Refresh Published Content](../../../../processes/marketing/refresh-content.md)

## What to record

A measurement plan at a version, naming every conversion, what counts as
one, and where it fires. For each conversion, a dated test record
showing a real submission arriving in the CRM. The tracking parameters
it handed to each paid channel, recorded against the page they belong
to. Anything it could not verify is recorded as unverified rather than
left out.

That contract covers every activity this abstract agent takes on, and it
is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract
agent does not do is in `com.agentcatalog.agent/NOT.md`.

skills/published-surface-sweep/SKILL.mdFinds every live page, advertisement and asset that carries a figure that has changed, such as a price, and gets each one restated so nothing still published contradicts the new one. Use it when running `ref/mkt/pricing-change`.

---
name: published-surface-sweep
description: Finds every live page, advertisement and asset that carries a figure that has changed, such as a price, and gets each one restated so nothing still published contradicts the new one. Use it when running `ref/mkt/pricing-change`.
license: CC-BY-4.0
metadata:
  agent: conversion-tracker
  agent-version: "1"
---

# Published surface sweep

## What it does

Finds every live page, advertisement and asset that carries a figure
that has changed, such as a price, and gets each one restated so nothing
still published contradicts the new one.

## Where it happens

The agent does this in one activity across one reference process. Each
one names the activity as that process words it.

- **Restate the Price Everywhere It Is Published**
  - `ref/mkt/pricing-change`, activity 7 -
    [Launch Pricing Change](../../../../processes/marketing/pricing-change.md)

## What to record

A measurement plan at a version, naming every conversion, what counts as
one, and where it fires. For each conversion, a dated test record
showing a real submission arriving in the CRM. The tracking parameters
it handed to each paid channel, recorded against the page they belong
to. Anything it could not verify is recorded as unverified rather than
left out.

That contract covers every activity this abstract agent takes on, and it
is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract
agent does not do is in `com.agentcatalog.agent/NOT.md`.

skills/tracking-links/SKILL.mdBuilds the coded links and parameters that let a visit be attributed to where it came from, so each advertisement, each creator and each destination can be counted separately in the report that reads them. Use it when running `ref/mkt/customer-reviews`, `ref/mkt/influencer-campaign` and `ref/mkt/traffic-ad-creative`.

---
name: tracking-links
description: Builds the coded links and parameters that let a visit be attributed to where it came from, so each advertisement, each creator and each destination can be counted separately in the report that reads them. Use it when running `ref/mkt/customer-reviews`, `ref/mkt/influencer-campaign` and `ref/mkt/traffic-ad-creative`.
license: CC-BY-4.0
metadata:
  agent: conversion-tracker
  agent-version: "1"
---

# Tracking links

## What it does

Builds the coded links and parameters that let a visit be attributed to
where it came from, so each advertisement, each creator and each
destination can be counted separately in the report that reads them.

## Where it happens

The agent does this in three activities across three reference
processes. Each one names the activity as that process words it.

- **Build the Tracking Parameters**
  - `ref/mkt/traffic-ad-creative`, activity 9 -
    [Traffic Ad Creative](../../../../processes/marketing/traffic-ad-creative.md)
- **Set up the Practical Side**
  - `ref/mkt/customer-reviews`, activity 9 -
    [Solicit Customer Reviews](../../../../processes/marketing/customer-reviews.md)
- **Set up the Tracking**
  - `ref/mkt/influencer-campaign`, activity 9 -
    [Run Influencer Campaign](../../../../processes/marketing/influencer-campaign.md)

## What to record

A measurement plan at a version, naming every conversion, what counts as
one, and where it fires. For each conversion, a dated test record
showing a real submission arriving in the CRM. The tracking parameters
it handed to each paid channel, recorded against the page they belong
to. Anything it could not verify is recorded as unverified rather than
left out.

That contract covers every activity this abstract agent takes on, and it
is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract
agent does not do is in `com.agentcatalog.agent/NOT.md`.

mcp.jsonNot in the package.

Every server entry in an mcp.json needs either a command to run or a url to connect to, and the package cannot know either of those until somebody points it at their own systems. So the file is left out, the systems the agent needs are named by role in plugin.json, and you write the mcp.json when you set it up.

Setting it up

Point it at your systems

To run an agent built from this package, write an mcp.json that says which of your systems fills each role. The package names these 4 roles, and the access level beside each one is the most the work needs.

analytics-platforms · writecrm · writead-platform-conversion-settings · writesites-pages · write

mcp.json You write this file. It is not part of the package.

{
  "$schema": "https://agent-plugins.org/schemas/1.1.0/mcp.schema.json",
  "mcpServers": {
    "analytics-platforms": {
      "type": "streamable-http",
      "url": "https://mcp.yourcompany.com/analytics-platforms"
    },
    "crm": {
      "type": "streamable-http",
      "url": "https://mcp.yourcompany.com/crm"
    },
    "ad-platform-conversion-settings": {
      "type": "streamable-http",
      "url": "https://mcp.yourcompany.com/ad-platform-conversion-settings"
    },
    "sites-pages": {
      "type": "streamable-http",
      "url": "https://mcp.yourcompany.com/sites-pages"
    }
  }
}

The hostnames here are a placeholder for your own. Whichever product holds each of these systems, the agent you build is yours and nobody else has to be involved in running it.

Where it works

26 processes, 39 activities

The highlighted activities are the ones this abstract agent does. The other activities in each process belong to other abstract agents or to people.

Run Account-Based Playref/mkt/account-based-play · 19 activities

Build the Pages and the Notice

Maintain Attribution Modelref/mkt/attribution-model · 16 activities

Check the Tracking

Launch Channel Programref/mkt/channel-program · 17 activities

Set up the Partner Systems

Run Co-Marketing Campaignref/mkt/co-marketing-campaign · 16 activities

Wire up the Split

Run Conversion Experimentref/mkt/conversion-experiment · 16 activities

Set the Terms of the Test · Brief the Makers · Wire the Measurement · Check the Setup · Watch the Test Run · Carry out the Decision

Publish Customer Newsletterref/mkt/customer-newsletter · 17 activities

Wire up the Measurement

Solicit Customer Reviewsref/mkt/customer-reviews · 16 activities

Set up the Practical Side

Run Display Retargeting Campaignref/mkt/display-retargeting · 16 activities

Tag the Site

Host Field Eventref/mkt/field-event · 16 activities

Open Registration

Run Influencer Campaignref/mkt/influencer-campaign · 16 activities

Set up the Tracking

Publish Landing Pageref/mkt/landing-page · 15 activities

Brief the Makers · Wire the Tracking · Hand It to the Campaign

Produce Long-Form Contentref/mkt/long-form-content · 18 activities

Wire up the Measurement

Report Marketing Performanceref/mkt/marketing-performance-report · 13 activities

Check the Tracking

Develop Media Planref/mkt/media-plan · 14 activities

Settle What Counts as a Result

Build Nurture Sequenceref/mkt/nurture-sequence · 16 activities

Brief the Makers · Wire up the Measurement · Run Test Contacts Through It

Run Paid Search Campaignref/mkt/paid-search-campaign · 13 activities

Wire up Conversion Tracking

Launch Pricing Changeref/mkt/pricing-change · 16 activities

Restate the Price Everywhere It Is Published

Reallocate Media Spendref/mkt/reallocate-media-spend · 14 activities

Confirm the Numbers Hold

Refresh Published Contentref/mkt/refresh-content · 22 activities

Check the Changed Pages

Test Ad Creativeref/mkt/test-ad-creative · 18 activities

Wire up the Measurement

Exhibit at Trade Showref/mkt/trade-show · 16 activities

Set up Lead Capture

Traffic Ad Creativeref/mkt/traffic-ad-creative · 17 activities

Build the Tracking Parameters · Check Every Destination · Check the Live Ads

Host User Conferenceref/mkt/user-conference · 17 activities

Open Registration

Produce Webinarref/mkt/webinar · 18 activities

Build the Registration Page · Hand off the Leads

Update Website Contentref/mkt/website-content-update · 12 activities

Check the Changed Page

Run Win-Back Campaignref/mkt/win-back-campaign · 20 activities

Brief the Makers · Wire up the Measurement

The records it leaves

What it writes down

A measurement plan at a version, naming every conversion, what counts as one, and where it fires. For each conversion, a dated test record showing a real submission arriving in the CRM. The tracking parameters it handed to each paid channel, recorded against the page they belong to. Anything it could not verify is recorded as unverified rather than left out.

Where it stops

What it will not do

Does not build the page and does not put it live. The web-producer assembles the page and the owner says go. Does not decide what the page is for; the process names the action that matters and this agent makes it countable. The analytics agent reports the numbers afterward, reading what this agent wired up, and the accessibility-check agent scores the page against the accessibility and technical standards. Does not set targeting or bids, and does not decide what happens to a lead once the CRM has it.

These limits are written into the job on purpose, so that everyone adopting the process knows which decisions stay with a person.

Agents built from this plugin

Who has built one, and how far each one got

Nobody has built one yet. The catalog says so rather than leaving the section off, because an empty list is a fact about the document.

declare it implements: conversion-tracker v1 One line in your agent's manifest. The catalog checks it against the records your runs actually leave.

A guess, not a claim

The closest things in the catalog, by description

Nobody above has claimed any of these. This is the nearest match by wording between the job written above and what publishers wrote about their own listings, closest first, and wording is not evidence: some of these will be wrong, and a job with nothing suitable still gets whatever was nearest. The publishers have never heard of this abstract agent and have promised nothing about it. What a claim looks like is in the table above, and it is signed.

Might be reached for

Not workers. These are capability that whatever does the job would use, which is a different relationship and kept in its own column for that reason.

First Party Data CRO MCP server · atul0016.github.io · run it yourself · mirrored from the MCP registry First-party funnel, rage-click, checkout, A/B test, and page-speed CRO intelligence.
ConvRadar MCP server · pikaivan.github.io · hosted · mirrored from the MCP registry GA4 conversion analyst inside Claude — funnel drops, traffic anomalies, device gaps, with numbers.
eyepup MCP server · edholofy.github.io · hosted · run it yourself · mirrored from the MCP registry Agentic visitor analytics — five tools that hand the next CRO fix to your coding agent.