The AI CMO/Docs
Sign in
Documentation overview

Connecting your data

Everything The AI CMO knows about your customers flows through the Data page – sources on the left of the journey, your event vocabulary in the middle, and the warehouse it all lands in. This manual covers each door in, and how to confirm your data arrived.

The Data page

Data in the sidebar opens three tabs:

  • Sources – how data gets in: CSV imports, the Website SDK at a glance, warehouse feeds and their freshness, and your uploads.
  • Events – the vocabulary of custom events your site and systems can send (see below).
  • Warehouse – totals, every event type as it streams in, and the meter showing how much of your plan's included volume you've used.

If you want to explore the platform before wiring anything real, Load demo data on the Sources tab fills the account with a sample business you can safely play with and remove later.

The fastest start: one CSV

The Add your data (CSV) card accepts one file and works out what it is:

  • Purchase history – a customer, a date, an amount per row. The moment it imports, the Overview tab has your revenue numbers.
  • Ad performance – a date, a platform, a spend per row. Platform names are standardized automatically (GADS, PPC, and Google Ads all become Google Ads), and ROAS and CAC go live on Overview.
  • A contact list – any file with an email column becomes an audience segment in Customer Intelligence → Audiences.
  • A combined file – one file with a record_type column can carry purchases and ad rows together. There's a sample CSV to download on the card.

You map the columns in a quick confirmation step, extra columns are always kept as customer attributes, and files up to 100,000 rows are accepted. Re-importing the same file is safe – the warehouse never double-counts an order it has already seen. Every import appears in the Uploads list, where it can also be deleted.

Connecting your apps

Integrations in the sidebar connects The AI CMO to the tools you already use. The page is organized by job:

  • Publish – Journeys and chat post here for you: LinkedIn, Facebook, X, TikTok, WordPress.
  • Measure – spend and results land in your analytics automatically: Google Analytics, Google Ads, Amazon Ads.
  • Reach & alert – talk to your customers and your team: email sending, HubSpot, Slack.

Connecting is one click: Connect opens a secure sign-in window for that platform, you approve, and you're done. Once an ad platform is connected, its spend syncs into your analytics on its own – no import needed.

Warehouse feeds

The Warehouse feeds section on the Sources tab shows every feed filling your warehouse and how fresh each one is: CSV uploads, webhooks (real-time events pushed from your own systems), Shopify orders and customers, and Google Ads and Meta Ads performance. Feed setup and webhook keys are managed by your workspace admins; everyone else sees the live status here.

Your website

The Website SDK is one script tag that brings visits, conversions, and revenue from your site into the warehouse – and it's how website messages from Journeys reach your pages. It has its own manual: Website SDK. The Sources tab shows its status at a glance, and the SDK page itself flips to "Receiving data" the first time an event arrives.

Your event vocabulary

The Events tab is where you define the business moments that matter – a deposit, a booking, a quote request. Register an event name and you get three ready-to-paste ways to capture it: a JavaScript call, an HTML attribute, or a server webhook. You can also set up no-code capture – point the event at a button, form, or URL on your site and the SDK fires it without any code change, even reading the value straight off the page.

Two details worth knowing:

  • Events your site sends that aren't registered yet show up as seen from your site, not registered – one click registers them.
  • An event can be marked as a suppression event: anyone who fires it is blacklisted from all contact. Built for self-exclusion and do-not-contact flows.

Registered events appear in the Warehouse tab as they stream in, can trigger journeys ("someone fires this event" enrolls them within about a minute), and can define audience segments.

Included events and what happens at the ceiling

Every plan includes a set volume of warehouse events – one event is one order, one deposit, one conversion, one webhook push. The meter on Data → Warehouse shows where you stand ("Included events – X of Y on your plan") and turns amber as you approach the ceiling.

The rules at the limit are deliberately one-sided:

  • CSV imports pause – an import that would pass your included volume is declined with the exact numbers, and your file is untouched. Upgrade, or trim the file, and import again.
  • Live streams never stop. Website events, webhooks, and store syncs keep flowing – rejecting live data would destroy it, so we don't.

You get a bell notification at 80% and at 100%. The CMO plan runs on a dedicated warehouse with no event ceiling.

How to know it worked

  • A CSV import confirms immediately and tells you where to look – purchases light up the Overview numbers on the spot.
  • A contact import names the segment it created in Customer Intelligence → Audiences.
  • The Website SDK page shows "Receiving data – last event" with a timestamp after your site's first event.
  • The Warehouse tab lists every event type the moment it streams in – including your registered custom events.