> ## Documentation Index
> Fetch the complete documentation index at: https://docs.introw.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Through-Channel Marketing
> Give partners campaign kits they launch from their own tools, with their AI assistant, and see which campaigns they ran and what they produced.
export const Headless = ({children, intro = true}) => {
const [copied, setCopied] = useState(null);
const copy = event => {
const row = event.target.closest("li");
if (!row) return;
const text = row.textContent.trim();
try {
navigator.clipboard?.writeText(text);
} catch {}
setCopied(text);
setTimeout(() => setCopied(null), 1600);
};
return <>
{intro ?
Introw is headless by design: run everything here in plain language from Claude, ChatGPT,
Slack, Teams, or your own CRM through Introw's MCP server, with every
action written straight back to your CRM source of truth. The portal is one surface, never the only one.
: null}
{children ? :
The agentic motion - lifecycle deep dives and a Claude Code skill library that run your partner program from
Claude, ChatGPT, Slack, and your CRM.
}
;
};
export const Rail = ({children}) =>
{children}
;
export const Impact = ({children}) =>
{children}
;
export const Personas = ({children}) =>
{children}
;
export const Pains = ({children}) =>
{children}
;
> Through-channel marketing is how your partners market you to their own customers.
> You hand them a campaign kit, their AI assistant turns it into their campaign, they send it from their own tools, and you see what it produced.
## The problem it solves
| Without Introw | With Introw |
| - | - |
| Partners never log in to campaign | They launch from the tools they own |
| Kits sit unused in a portal | Their AI turns a kit into a campaign |
| You cannot see what partners run | Partners register every campaign |
| You cannot prove a campaign paid off | Clicks, deals and ROI per campaign |
## Impact
The partners worth marketing through already run their own email, ads and social.
Handing them a kit their assistant can rework in minutes, instead of a campaign builder they have to learn, is why your campaign is the one they send.
for your business
* **No new tool**
Partners run the campaign from HubSpot, Mailchimp or LinkedIn, the tools they already pay for, and you supply the kit and its rules
* **AI, not admin**
A partner's assistant finds the kit, rewrites it in their voice and registers the campaign, so you do not write a version per partner
* **In your CRM**
Registered campaigns, attributed clicks and the deals they produce land as CRM records, so campaign revenue reports like any other source
for your partners
* **Self-serve**
They pull the kit, open the one-pager with their own logo on it and launch without a design request or a briefing call
* **Enabled**
A brief that states the audience, the message and the proof they can quote, so the campaign is thought through before they start
* **Efficient**
Their assistant turns one kit into their own sequence in minutes, and the budget request is one form
[A day in the life of your partners](/days-in-the-life)
* **Partner Marketing** - campaigns go out without a version per partner
* **Partner Operations** - every campaign registered, every deal attributed
* **Head of Partnerships** - partner marketing that shows up as pipeline
* **Partner marketers** - a kit their AI assistant can rework in minutes
## How this area works
You publish a campaign kit once, partners and their AI assistants rework it into their own campaign, they send it from their own tools, and attribution brings the results back to you.
The kit lives in your asset library and shows up in the portal, the campaign is registered with a form, and clicks and deals come back through affiliate links and ROI.
* 
[**Campaign Kits**](./campaign-kits)
One folder per campaign, on a portal tab with a hero.
[How to · 2 guides](./campaign-kits/technical)
* 
[**AI Campaign Remix**](./ai-remix)
Their assistant reworks the kit into their campaign.
[How to · 2 guides](./ai-remix/technical)
* 
[**Campaign Registration & ROI**](./campaign-roi)
Every campaign registered, every deal counted against it.
[How to · 3 guides](./campaign-roi/technical)
* 
[**Campaign Attribution**](./attribution)
Clicks, signups and kit usage, per partner and campaign.
[How to · 2 guides](./attribution/technical)
Through-channel marketing used to mean a campaign builder inside the vendor's portal.
Partners who drive real revenue rarely use it, because they already run their own marketing stack and audience.
Introw works the other way around.
You build the campaign once as a kit: a brief with the audience, the message and the proof points, the emails, the social posts, a banner, a call talk track, and a one-pager each partner opens with their own name and logo on it.
The kit sits in one folder of your asset library and appears on a portal tab, framed with a hero and calls to action.
Partners pick it up two ways.
In the portal, they download the pieces and the co-branded one-pager.
Through their AI assistant, connected to Introw Partner Connect, they ask for the kit, have the assistant rewrite it around their own services and voice, and paste the result into the tools they already send from.
The same assistant registers the campaign with you through a form, so you know what is running, when it started and who it went to.
Results come back through mechanisms you already run.
A partner who funds the campaign through market development funds logs every deal it creates as ROI against that request, so spend and pipeline sit side by side.
Affiliate links attribute every click and signup to the partner who sent it.
Asset engagement and the Assets report show which kits partners open and download, per partner and per campaign category.
## Run it from your AI assistant
* Which campaign kits are in the asset library, and which folder holds each one?
* Which partners have registered a campaign this quarter, and which are still pending?
* Show the ROI logged against each market development fund request this quarter.
* Add this one-pager to the Q4 campaign kit folder and give it a short description.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.