> ## 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.

# AI Campaign Remix

> How partners connect their own AI assistant to your campaign kits, what the assistant can read and submit, and what stays in the portal.

export const Rail = ({children}) => <div className="not-prose" data-overview="rail">
    {children}
  </div>;

**Open in Introw:** [Assets](https://app.introw.io/assets/library)

## Where it lives

AI Campaign Remix has no screen of its own.
On your side it runs on the campaign kits you publish in [Assets](https://app.introw.io/assets/library) and show on an Asset Hub in the portal.
On the partner's side it runs in their own AI assistant, connected to Introw from **Settings**, **Integrations**, **MCP** in their account at [partners.introw.io](https://partners.introw.io).

<Frame>
  <img src="https://assets.introw.io/docs/tcma/remix-01-find-the-kit.png" alt="A partner asks their AI assistant for the Q4 campaign kit, and the assistant finds it through Introw Partner Connect and lists all six assets: the brief, emails, LinkedIn posts, banner, co-branded one-pager and call talk track." />
</Frame>

## Before you start

| You need | Why | Fix it |
| - | - | - |
| A campaign kit on an Asset Hub | The assistant only searches what the partner's portal shows | [Enable partners with a campaign kit](/features/tcma/campaign-kits/guides/enable-partners-with-a-campaign-kit) |
| Kit documents with real text | The assistant reads text, not pictures of text | [Prepare a campaign kit for AI](/features/tcma/ai-remix/guides/prepare-a-campaign-kit-for-ai) |
| A partner with portal access | The connector acts as that partner and sees what they see | [Partner AI](/features/partner-connect/partner-ai/technical) |
| A form to register or fund a campaign | So the assistant can register the campaign it built | [Campaign Registration & ROI](/features/tcma/campaign-roi) |

The partner connector needs no toggle and no module on your plan.
Any user on the partner side can connect their own assistant.

## How it works

A partner connects their assistant once, and the connection covers every vendor portal their account can reach.
From then on the assistant uses the same tools for your program as for any other: it searches portal content, reads marketing fund details, and opens and submits portal forms, all scoped to that partner's access.

Content search is the part that makes a kit remixable.
When the partner asks for a campaign, the assistant searches the text of the assets their portal shows, ranks the best matches, and gets back the relevant passages with a link to each asset.
Long passages are condensed around the question first, so a focused ask ("the full text of email 2") gets the closest answer.

The assistant writes the partner's version in the conversation.
Introw does not store the rewrite: the partner copies it into their own email tool, social scheduler or CRM.

```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
  partner["Partner's AI assistant"] -->|"Partner MCP connector"| introw["Introw"]
  introw --> hub["Assets on the partner's Asset Hubs"]
  introw --> forms["Portal forms"]
  hub --> partner
  partner --> tools["Partner's own email and social tools"]
```

## What the assistant can and cannot do

| Job | Can the assistant do it? | How |
| - | - | - |
| Find the campaign kit | Yes | Searches the assets the partner's portal shows and returns a link to each |
| Read the brief, emails and posts | Yes | Reads the text of the documents, condensed around the question when long |
| Rewrite the kit for the partner | Yes | Writes the new version in the conversation, from the partner's own instructions |
| Download the original files | No | The partner opens the link the assistant gives and downloads from the portal |
| Produce the co-branded one-pager | No | The partner opens it in the portal, where their logo and name are merged in |
| Fetch the partner's affiliate link | No | The partner copies it from the portal and pastes it into the draft |
| Check marketing fund budget | Yes | Reads the partner's funds, requests and claims |
| Register or fund the campaign | Yes | Opens the campaign or MDF request form, asks for missing fields, then submits it |
| Send the campaign | No | The partner sends from their own tool |

<Frame>
  <img src="https://assets.introw.io/docs/tcma/remix-03-register-the-campaign.png" alt="The assistant registers the campaign with the vendor by submitting the Request Fund form through Introw Partner Connect, with the activity, date, budget and expected outcomes filled in." />
</Frame>

## Settings & configuration

AI Campaign Remix has no settings of its own.
What the assistant can reach is controlled by settings you already use.

**Asset Hub visibility** decides what is searchable.
An asset is only in the partner's search if it is visible on an Asset Hub in that partner's experience, so switch on the eye next to the campaign folder in the hub's **Configure asset visibility** list.

**Asset access** narrows it further.
An asset on **Restricted access** is only found for the partners, segments or contacts allowed to see it, the same rule the portal applies.

**Tab access** applies too.
If a tab is hidden from a partner contact, the assets on that tab are not searched for that contact.

**Forms** decide what the assistant can submit.
Any partner form the partner can open in the portal, including an MDF request, can be discovered and submitted from the assistant.

## How-to guides

<Rail>
  * ![A kit asset open in the asset library, with the short description an AI assistant reads when it searches your content, here on the co-branded one-pager.](https://assets.introw.io/docs/features/tcma/campaign-kits/guides/enable-partners-with-a-campaign-kit/steps/05.png)

    [**Prepare a campaign kit for AI**](/features/tcma/ai-remix/guides/prepare-a-campaign-kit-for-ai)

    Structure and write a campaign kit so a partner's AI assistant can find it, read it and rewrite it on message, then test it the way a partner will use it.

  * [**Remix a campaign kit with your AI assistant**](/features/tcma/ai-remix/guides/remix-a-campaign-kit-with-your-ai-assistant)

    As a partner, have your own AI assistant pull a vendor's campaign kit, rewrite it with your services and voice, and register the campaign, then send it from your own tools.
</Rail>

## Troubleshooting

<AccordionGroup>
  <Accordion title="The assistant cannot find the campaign kit">
    Open the experience the partner is on and check that the kit sits on an Asset Hub with the folder's eye switched on in **Configure asset visibility**.
    Then check the asset's access: on **Restricted access**, the partner must be in the allowed list.
    New uploads take a short while before their text is searchable.
  </Accordion>

  <Accordion title="The assistant returns a summary instead of the full email">
    Long documents are condensed around the question.
    Ask for one item at a time, for example "the full text of email 2 in the Q4 email sequence".
  </Accordion>

  <Accordion title="The assistant cannot read the banner or a slide">
    Images carry no searchable text.
    Put the copy in a text-based PDF or document next to the image.
  </Accordion>

  <Accordion title="The one-pager the partner downloaded has no logo">
    Co-branding happens when the PDF is opened in the portal, not from the assistant.
    Ask the partner to open the link the assistant returned, and check that a logo is set on the partner.
  </Accordion>

  <Accordion title="The assistant says it cannot register the campaign">
    The partner needs access to the form, for example the MDF request form on their portal.
    Check that the form is published in their experience and that the fund is open to their segment.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.