Campaigns in your AI assistant

Use Campaigns from Claude, ChatGPT, Jamaa and other assistants

Connect Tyms Campaigns and ask your assistant what worked, how a campaign is doing, or to plan and draft the next one. It works on the same campaigns your team sees in the browser, as you, and a person always launches what it drafts.

The address

Add this address to your assistant as a connector (also called an MCP server). It's the same for everyone:

https://campaigns.tyms.ai/mcp

The first time your assistant connects, you sign in with your Tyms account and choose the workspace it works in. No account yet? Get started for free; an owner or admin switches Campaigns on for your organisation. In Jamaa there's nothing to add: it uses Campaigns once Campaigns is on.

Set it up

Claude

  1. In Claude (web or desktop), open Settings → Connectors and choose Add custom connector.
  2. Name it Tyms Campaigns and paste the address as the URL.
  3. Select Connect, sign in with your Tyms account and choose your workspace.
  4. In a chat, turn on Tyms Campaigns from the tools menu and ask it what worked, or to plan your next campaign.

On Claude Team or Enterprise, an owner may need to add the connector for the organisation first; then each person selects Connect.

ChatGPT

  1. In ChatGPT, open Settings → Apps & Connectors → Advanced settings and turn on Developer mode.
  2. Back in Apps & Connectors, choose Create. Name it Tyms Campaigns, paste the address and pick OAuth.
  3. Sign in with your Tyms account and choose your workspace.
  4. In a chat, add Tyms Campaigns from the tools menu.

Custom connectors need a paid ChatGPT plan; on Business plans an admin may need to allow them.

Jamaa

  1. Nothing to add. When Jamaa and Campaigns are both switched on for your workspace, Jamaa can use Campaigns as you.
  2. In Campaigns, choose Ask Jamaa. With Organization Intelligence on, it writes in your company's voice.

Claude Code

  1. Run claude mcp add --transport http tyms-campaigns https://campaigns.tyms.ai/mcp in your terminal.
  2. In Claude Code, run /mcp, choose tyms-campaigns and sign in.

Cursor

  1. Open Cursor Settings → MCP → Add new MCP server.
  2. Paste the address. Cursor asks you to sign in the first time it uses Campaigns.

Other assistants

  1. Any assistant that supports remote MCP servers over HTTP with OAuth can connect: add a server with the address and sign in when asked.

Assistant menus change from time to time; if a step doesn't match what you see, look for “connectors”, “apps” or “MCP” in its settings.

Try asking

  • “Plan a three-email campaign to get 60 registrations for the webinar.”
  • “Which campaign brought the most bookings per dollar this quarter?”
  • “How is the running campaign doing against its target?”
  • “Add Amina from the trade fair to the newsletter; she asked for it.”

Assistants that offer prompts also list a ready-made one: plan a campaign.

What it can do

  • It acts as you. It sees your workspace's campaigns, results and audience, and can do what you can do in Campaigns, nothing more.
  • It plans from what worked. It compares past campaigns by how many reached their goal and what each cost, and drafts the next one: the goal, who gets it, when, and each email.
  • A person launches. It never launches, pauses, ends or sends a campaign. Drafts wait in Campaigns for an owner or admin.
  • Consent is stated, never assumed. It adds someone only with their consent said: agreed (with a note), sent the confirmation email, or not yet. Nobody who unsubscribed is added back.
  • Your team can tell. What it drafts and adds is recorded as your assistant's, in the workspace's history.

Tools

What your assistant may call. Tools that read need permission to read Campaigns (campaigns:read); tools that change something need permission to contribute (campaigns:contribute). Read-only access offers only the tools that read.

ToolWhat it doesKind
campaigns_list_campaignsLists campaigns with each one's goal, status, people reached against the target, rate and cost per conversion.Reads
campaigns_show_campaignShows a campaign in full: goal, audience, cadence, each email, and its results by email and by day, with up to 20 of the people behind each number.Reads
campaigns_list_audienceLists lists and segments with how many agreed to marketing email, tags, and the last 30 days' growth.Reads
campaigns_what_workedCompares past campaigns, best first, with each one's best email: context for planning the next.Reads
campaigns_draft_campaignDrafts a campaign or changes a draft: goal, audience or how people enter, cadence and emails. Says who it would reach and what to fix. Never launches it.Changes
campaigns_add_subscriberAdds someone to lists with their consent stated: agreed (with a note), sent the list's confirmation email, or not yet.Changes

Report conversions

A campaign whose goal is a conversion (a purchase, a signup, a booking) needs your site or server to say when one happens. Your workspace's keys and its own address are in Campaigns under Email settings → Conversion tracking; below, your-team stands for your workspace.

From your site

Add this to every page, with your workspace's public key:

The site snippet
<script>window.tyms=window.tyms||function(){(tyms.q=tyms.q||[]).push(arguments)};</script>
<script async src="https://your-team.campaigns.tyms.ai/t.js" data-key="pk_…"></script>

Then, where someone converts:

Report a conversion from the page
tyms('convert', 'purchase', { value: 120, currency: 'USD', id: 'order-1001' });

Every link in a campaign email carries a click token. The snippet keeps it in one first-party cookie (tyms_tc) for up to 90 days and reports conversions with it. A visitor who didn't come from a campaign email has no token, so nothing is reported about them. The snippet uses nothing else: no other cookies, no local storage, no fingerprinting. Mention the cookie in your site's cookie notice.

From your server

Report a conversion from a server
curl -X POST https://your-team.campaigns.tyms.ai/api/conversions \
  -H "Authorization: Bearer sk_…" \
  -H "Content-Type: application/json" \
  -d '{"event":"purchase","email":"amina@example.com","value":120,"currency":"USD","id":"order-1001"}'
  • Send event and either the person's email or the click token; value, currency and id are optional. The same id twice counts once.
  • The secret key (sk_…) is shown once when an owner or admin makes it; keep it on your server. Making a new one stops the old one at once.
  • Take a conversion back within 24 hours (a refund, a mistake) with DELETE https://your-team.campaigns.tyms.ai/api/conversions/{id} and the same key: it leaves the report and is never charged. After 24 hours it has been counted.
  • Add "test": true to check your setup: it shows under Conversion tracking and counts for nothing. The answer is 202 with what happened: attributed, holdout, unattributed, pending, duplicate or test.

A conversion counts for the campaign whose email the person most recently clicked within the goal's window, else the one they most recently received; never for two.

Privacy and control

  • See and disconnect. Every assistant you've allowed, in which workspace and when it was last used, is on Connected apps. Disconnecting ends its access within the hour.
  • Admins decide. Owners and admins can turn assistants off for the whole workspace in Tyms Admin, which disconnects every assistant there at once.
  • No conversations kept. Campaigns records which assistant called which tool and what it drafted or added, never the text of your chats.
  • Secure sign-in. Assistants sign in through auth.tyms.ai with OAuth; they never see your password, and their access expires and renews on its own.

Questions

Which workspace does my assistant use?

The one you choose when you connect. Everyone uses the same address; after you sign in, Tyms lists your workspaces that have Campaigns switched on and you pick one. To switch, disconnect it in Connected apps and connect again. To connect one workspace only, use its own address: your-team.campaigns.tyms.ai/mcp.

Can my assistant send a campaign?

No. It can plan and draft a campaign (its goal, who gets it, when, and each email) and tell you what must be fixed before launch, but only an owner or admin launches, pauses or ends a campaign, in Campaigns. No assistant can send an email to your audience.

Can my assistant add people to my lists?

Yes, with their consent stated: that they agreed (with a note saying how and when, kept as the record), that they should get the list's confirmation email (they're subscribed only once they click it, whatever the form's own setting), or that they haven't agreed yet (no campaign emails them). It can't add back anyone who unsubscribed, reported spam or bounced: only they can sign up again.

Does Campaigns track opens?

No. Mail apps open emails by themselves, so the number means little, and a tracking pixel costs your subscribers' privacy. Campaigns counts clicks (people's, not scanners'), signups and the conversions your site or server reports.

It says AI assistants are turned off for this workspace.

An owner or admin of the workspace has turned assistants off in Tyms Admin. Ask them to turn “Allow AI assistants to connect” back on. This setting is for outside assistants such as Claude and ChatGPT; Jamaa follows whether Jamaa and Campaigns are switched on.

Does my assistant cost extra?

No. A campaign costs the same whoever drafts it: launching is free, and each person who reaches a campaign's goal counts once. Reading results and drafting don't count.

What does Tyms keep about my conversations?

Nothing from your chats with your assistant. Campaigns keeps the drafts and subscribers it saves, as for anyone, and records which assistant called which tool, in which workspace.

Still stuck?

Email support@tyms.ai with the assistant you're using and what it said. We'll help you get connected.