For the complete documentation index, see llms.txt. For the full corpus, see llms-full.txt. For raw markdown, append .md to this URL or send Accept: text/markdown.

Running Campaigns

Campaigns are the wrapper that runs and ties your workflows to outcomes.

Last updated: May 19, 2026

You’ve chosen or created workflows that do your marketing tasks. Now you need to run them.

Campaigns are the wrappers that run your workflows, and track everything back to them so that you can see your efforts across your app tied to your marketing efforts.

What happens under the hood

A campaign groups one or more workflows together under a name, a status, and whatever inputs each workflow needs.

The moment you start running the campaign, multiple things happen under the hood:

1. URLs get auto-tagged. Any URL to your property’s domain in a workflow node gets a short attribution token appended as ?sscid=TOKEN. You don’t add it, the campaign does that automatically.
2. Sessions stamp their origin at ingest. When a visitor clicks a tagged URL and lands on your site, our SDK reads the sscid token and writes campaignId onto the session. The session you replay later knows which campaign drove it.
3. Goals, split tests, and feedback roll up per campaign. Sessions with a campaignId attached allows you to see which of these are driven by your marketing efforts, allowing you to attribute efforts directly to results.
4. Automatic coloring. Any AI node that generates content for you is fed your company’s strategy (company details, competitors, personas, etc). This makes it so that the content is generates is specific to you, even if you installed a workflow from the marketplace.