Mojo is an AI teammate for B2B performance marketing. Connect your marketing stack (ad platforms, CRM, MAP, analytics) and talk to Mojo in plain English to pull reports, audit campaigns, launch programs, and take action across tools without switching tabs.
When you ask Mojo something, it:
Figures out which tools it needs to answer your question or complete the task
Reads the relevant data from those tools: your Salesforce pipeline, LinkedIn campaigns, Marketo programs
Does the work: analysis, reporting, drafting, or taking action
Checks before writing: depending on your write mode setting, Mojo prompts for approval before making changes to your systems
How much Mojo asks before acting is up to you. See Write modes below.
Mojo is currently in private beta. Once you've received your invite email:
Click the link in the email → complete account setup → start a conversation on Home
Click the link and Mojo signs you in automatically
Sign up or reach out to your Mojo contact directly.
After signing in, Home is the conversation-first place to ask Mojo a question, explore your work, or start a task.
Start on Home: type a question or request in plain English.
Connect when needed: go to Integrations in the left sidebar, choose a platform, and complete its OAuth or credential flow.
Choose your work: ask Mojo to analyze data, create a workflow, or take an approved action.
Connecting a provider adds that connection only; Mojo does not automatically provision or run sample workflows. Go to Integrations in the left sidebar at any time to add or manage connections.
Connect the tools you check most often. For most B2B marketing teams, that's LinkedIn Ads, Google Ads, Salesforce, and Google Analytics.
Once you've connected at least one tool, type a question or request in plain English. You don't need to learn a query language or know which API to call.
Good first asks:
Spend & Conversions
"Show me spend and conversions by campaign for the last 30 days."
Leads
"Which LinkedIn campaigns have no leads in the past two weeks?"
Opportunities
"Summarize what closed-won opportunities look like from the last quarter."
When Mojo is about to take a write action (pausing a campaign, updating a budget, creating a doc, sending a Slack message), it shows you what it's about to do before executing.
You'll see an approval card with:
What action Mojo is taking and which tool it's acting on
For example: Sensitive write
A field-by-field breakdown of what will change (expandable)
Three controls: Approve · Always approve for this session · Reject
Read-only tasks (pulling a report, answering a question, summarizing data) never trigger an approval prompt.
You control how much Mojo checks in with you via the write mode picker in the chat composer.
| Mode | Behavior |
|---|---|
| Read Only | No writes at all. Mojo answers questions and pulls data only. |
|
Guarded Default |
Low-risk writes run automatically. Higher-risk or destructive actions prompt for approval. |
| Trusted | Low and high-risk writes run automatically. Only destructive actions prompt. |
| Autonomous | All writes execute without prompts. |
Start with Guarded (the default) until you're comfortable with how Mojo handles your stack. You can change modes at any time mid-conversation.
Budget
"How is my LinkedIn spend tracking against budget this month?"
Conversions
"Which campaigns are active but have zero conversions?"
Reporting
Give me a top-line report: spend, leads, and pipeline from last month across all connected ad platforms.
Pause
"Pause any campaigns with no impressions in the last 7 days."
This one will show you the approval card in action before Mojo touches anything.
A Skill is a saved procedure that tells Mojo how to do a specific job: what steps to follow, which tools to use, and what output to produce. Skills let you and your team capture repeatable processes once and run them on demand. You don't need to know upfront whether what you want is a Skill, a Routine, or a Workflow — describe it to Mojo and it'll help you figure out the right one.
Skills are defined by files that describe a procedure — Markdown, JSON, or YAML. When you invoke a Skill, Mojo reads them and executes the steps (pulling data from your connected tools, doing the analysis, and producing output), all in a single run.
Mojo ships with a set of pre-built Skills for common B2B marketing jobs. Your org can also create custom Skills for anything specific to how your team operates.
Three ways to run a Skill:
If enabled for your org, Skills that match your connected integrations mount automatically. Just describe the job and Mojo picks up the right Skill.
Type @ or click + in the composer to attach a Skill to your message explicitly.
On the Skills page, each Skill has a "Try it" button that loads a starter prompt for you.
Checks your ad spend across connected platforms against monthly or campaign budget targets. Shows whether you're on track, ahead, or behind, with time to course-correct.
Tools it uses: Google Ads, LinkedIn Ads, Meta Ads (any combination of what you've connected)
Output: A summary table showing each campaign or account, current spend, projected end-of-period spend, and a status flag. Mojo highlights anything at risk and can suggest corrective actions for your approval.
Traces leads from first touch through your marketing funnel (ad click to form fill to CRM record to opportunity) and identifies where leads are dropping off, getting stuck, or going dark.
Tools it uses: Google Ads, LinkedIn Ads, Meta Ads, Google Analytics, Marketo, Salesforce
Output: A funnel view with volume and conversion rates at each stage. Mojo highlights the biggest drop-off points, flags sync errors between tools, and explains findings in plain language.
Pulls performance data across your full marketing stack for a defined period and produces a structured retrospective: what happened, what worked, what didn't, and what to carry forward.
Tools it uses: Google Ads, LinkedIn Ads, Meta Ads, Google Analytics, Marketo, Salesforce, Demandbase
Output: A structured report covering spend by channel, lead volume and quality, pipeline sourced and influenced, top campaigns, and Mojo's read on what drove results and what underperformed. Output can be saved to a Google Doc or Google Sheet.
See Campaigns — it covers the full campaign context (goal, audience, messaging, channels, budget, and more).
Your org can create Skills for any repeatable job: weekly reporting, campaign QA checklists, account briefs, whatever your team runs on a regular cadence. Skills are authored in a dedicated editor — write the steps directly in Markdown, JSON, or YAML, with live multi-person editing if teammates are working on the same Skill together. Import or export a Skill as a zip file to move it between orgs.
To create a Skill, go to the Skills page and select New Skill. Write it yourself, or describe what you want and use Authoring Assist to draft it. Each Skill can be published in versions — publish a new version once you've tested a change, or unpublish one that isn't ready — and you can restrict which of your org's connected integrations a Skill is allowed to use.
You don't need a Skill for every task. Mojo handles one-off questions fine, like "what's my LinkedIn CPL this week?" or "which accounts went dark in the last 30 days?"
The difference is scope and repeatability. A Skill runs a defined multi-step procedure with structured output you can run again next week. A question gets you an answer right now.
Any Skill step that writes to a connected system follows the same approval rules as regular actions, so behavior depends on your active write mode. Read-only Skills (Lead Flow Audit, Marketing Retrospective) run without interruption and show results when complete.
A Routine is scheduled or triggered work: something Mojo checks or does on its own, without you asking each time. Point it at a prompt you'd normally type yourself, or at a saved Workflow, and give it a trigger — most commonly a recurring schedule.
These three are related but not the same thing. A Skill is a saved procedure Mojo runs when you invoke it in a conversation. A Workflow is the durable, multi-step execution underneath — the thing that actually does the work, step by step, with retries and state. A Routine doesn't do new work itself; it takes a prompt or a Workflow you already have and adds a schedule or trigger, so it runs without you starting it. Not sure which one fits what you're after? Ask Mojo to help set it up — it'll pick the right shape for the job.
Go to Routines in the left sidebar. Each Routine has a type — a Prompt (ask Mojo something on a schedule, the same way you'd type it in chat) or a Workflow (run an existing saved Workflow on a schedule). Give it a trigger, most commonly a recurring schedule, and Mojo takes it from there.
The Routines page lists every Routine your org has, with its last run status. Open any Routine to see its full run history.
A Routine can trigger while nobody's in a live conversation to approve a write action. When that happens, Mojo can't show you the usual in-chat approval card — instead it pauses the run and sends a Slack notification so you can review and approve from there. The same write-mode rules from Getting started still apply; a Routine doesn't get more or less permission than you'd have asking in chat.
A Workflow is a saved, deterministic sequence of steps — nodes and edges, saved together as one file. It's the layer underneath a lot of what Mojo does: a Skill or a Routine can run one, and you can also build and run a Workflow directly.
The line between these three isn't sharp, and that's fine — you don't need to pick the right one before you start. A Skill is a saved procedure you invoke in conversation. A Routine adds a schedule or trigger on top of a prompt or a Workflow, so it runs without you asking. A Workflow is the deterministic execution underneath both — the actual sequence of steps, with retries and state. If you're not sure which of these fits what you're trying to do, just ask Mojo — describe it, and it'll build the right one with you.
Go to Workflows in the left sidebar. Workflows are built in the same editor Skills use — write the steps directly, or describe what you want and let Mojo draft it with you.
Each Workflow keeps a run history — every time it's run, with a step-by-step view of where it is or where it stopped. Approvals work the same way here as everywhere else: any step that writes to a connected system follows your active write mode.
Mojo understands plain English. You don't need to learn a query syntax or memorize field names. But there's a difference between prompts that get you exactly what you need in one shot and ones that require three rounds of back-and-forth. This guide closes that gap.
Be specific about time. Vague time ranges produce vague answers. Instead of "Show me campaign performance," try "Show me campaign performance for the last 30 days."
Name the platform when it matters. If you have multiple ad platforms connected and you're asking about one specifically, say so. If you want cross-channel results, say that too.
Tell Mojo what you want to do with the output. If you want a report saved somewhere, say so. If you want Mojo to take action rather than just report, say so.
Read-only asks: Mojo pulls data and shows it to you. No approval needed, nothing changes in your systems.
Action asks: Mojo is going to change something. It will always pause and show you what it's about to do before executing.
You can mix both in the same prompt: "Show me campaigns with no conversions, then pause any that have been running for more than 14 days." Mojo shows you the list first, then presents the pause action for your approval.
Mojo handles multi-step requests naturally. You can chain tasks in a single ask, and if a step needs clarification, Mojo will ask before proceeding rather than making assumptions.
Sometimes Mojo will ask before it starts rather than assume. This usually means you have multiple accounts or properties and Mojo wants to know which one, the task involves an irreversible action and Mojo is being careful, or the request is ambiguous. Answer in plain English and Mojo will continue.
Mojo can't access tools you haven't connected, can't read data inside files it hasn't been given (PDFs, local spreadsheets), can't push to read-only tools like Google Analytics, and doesn't remember the specific results of a past conversation — re-run the query or paste it in.
Give Mojo the context it needs — "the Q3 SaaS awareness campaign on LinkedIn" beats "that campaign we ran." Ask for the format you want. Iterate — if the first response isn't quite right, tell Mojo what to change. Ask follow-up questions without re-stating everything.
Mojo works by connecting to the tools you already run marketing on. Connect a tool once and Mojo can read from it, act in it with your approval, and carry context across your whole stack.
Each integration is an authorized connection between Mojo and one of your platforms. You authorize it once through that platform's normal login, and Mojo holds a secure, revocable connection. There are no API keys to copy and no data to export by hand.
Open Integrations in the left sidebar and find the tool you want to connect.
Click Connect. You'll be sent to that platform's login to authorize Mojo.
Review the access being granted and confirm. The tool now shows as Connected.
Ad platforms: Google Ads, LinkedIn Ads, Meta Ads — plus Campaign Manager 360 (CM360) for tracking and ad serving.
CRM & marketing automation: Salesforce, Marketo, HubSpot.
Analytics & ABM: Google Analytics (GA4), Demandbase.
Team tools: Slack.
Output & collaboration: Google Docs, Google Drive, Google Sheets, and Google Slides — connected individually rather than as one bundled Google Workspace connection.
Mojo requests the minimum access each job needs. Reading data for reporting and audits never changes anything in your tools. Writing to a connected system always follows your active write mode, so you approve changes before they happen. Connections are revocable at any time.
Any connection you own can be shared — search for a teammate by name or email, or, if you're an org admin, share it with everyone in the org at once. Sharing currently grants read-only access. Some connections can't be shared at all, if they're tied to your personal account rather than a shared login.
You can revoke access you granted at any time. Whoever owns the connection can revoke anyone's access to it; if you shared it further yourself, you can revoke only the shares you personally granted.
A Campaign is Mojo's workspace for a specific marketing effort — everything about what you're trying to prove, who it's for, and how you'll know it worked lives in one place.
Start from something you already have — a brief, a deck, notes from a call — rather than filling out a blank form. Mojo reads it and proposes the campaign's context for you to confirm or adjust.
Every campaign is built around a consistent set of fields: Hypothesis (what you believe and want to test), Goal (the outcome you're aiming for and how it's measured), Audience, Narrative & Messaging, Channels, Flight (start and end dates), Budget, and Stop if (the condition under which the campaign should pause or end).
A campaign can have Routines watching it — for example, one that tracks progress toward its goal, or one that flags budget pacing drift — and can roll up into a broader goal your org is tracking. As with everything else Mojo does, nothing about a live campaign changes without your approval first.
Solutions to common issues with connections, approvals, and data. If something isn't covered here, paste the error into Mojo chat, and it can usually diagnose issues on the spot.
My integration isn't connecting: make sure you're authorizing with the right account, check that your account has sufficient permissions (some platforms require admin-level access), try disconnecting and reconnecting, or try a different browser.
Mojo connected but says it can't find my data: usually a permission scope issue, the wrong account connected (if you manage multiple), or the data genuinely doesn't exist yet for the range you asked about.
I connected Salesforce but it's asking me for a custom domain: this is expected — on the login screen, click "Use Custom Domain" and enter demandbase.
Why Mojo prompts before acting depends on your active write mode — see the Write Modes table above. The controls on an approval card are Approve, Always approve for this session, and Reject. If you approved an action but nothing happened, check for an error message in the conversation and check your permissions on the target platform.
Small discrepancies between Mojo's numbers and what you see in a platform are normal — attribution windows, timezone differences, and reporting lag all play a part. Ask Mojo to "show me where that number is coming from" and it can trace a figure back to the query that produced it.
Does Mojo remember things between sessions? Yes. Mojo maintains memory across sessions: things like your reporting preferences, timezone, how you like data formatted, and facts about your role or team. At launch there's no dedicated settings page for reviewing this — ask Mojo directly ("What do you remember about me?") and it will tell you.
I don't want Mojo to remember something: tell Mojo in chat — "Forget that I prefer weekly rollups" — and it will remove it. There's no separate settings page for managing memories at launch, so chat is the way to review or clear what's stored.
What is Mojo's Brain? Brain is the broader system behind Mojo's memory — it's what lets Mojo learn and recall facts, preferences, and context over time, and build a shared knowledge base for your org. There's no dedicated Brain page in the product at launch, but nothing about asking Mojo what it knows depends on that page existing — just ask.
Who has access to my Mojo workspace? Your conversations and session memories are private to you. Shared resources (org Skills, shared Workflows, shared integrations) are accessible to whoever you've shared them with, or to your whole org depending on how they were set up.
How do I invite a teammate to my org? Org admins can invite people from Organization Admin in Settings — add them by email and manage roles and pending invites from there. If you don't see that option, you're not an org admin; ask one on your team to send the invite.
Does Mojo store my marketing data? For most requests, Mojo queries your connected tools live rather than syncing and storing a copy. It does keep records of the workflows and actions it runs on your behalf — including results returned by connected platforms — so you can review history and past outputs. See our Privacy Notice for details on data retention.
Can I connect the same tool twice? Not currently — one connection per tool. Disconnect and re-authorize to switch which account is connected.
Something went wrong that isn't covered here: paste the error or describe what happened into Mojo chat, and it can often diagnose issues on the spot.
Prev Doc
Get MojoNext Doc
Skills & WorkflowsJoin the beta. Connect your stack. Ask the question you've been meaning to ask.