Marketing automation
Signals vs Ortto
Ortto is a marketing-automation platform with a customer-data core: marketing teams use it to merge product and billing data into unified profiles, then run journeys, email, SMS, push, and in-app messaging against them. Signals is a read-only timeline for founders and small teams who want to know what actually happened with each customer and who needs attention — not to orchestrate campaigns. Both pull your Stripe data into a single profile; what they do with it could hardly be more different.
The short version
If your goal is to orchestrate marketing — build visual customer journeys, send omnichannel campaigns, and target segments from merged product and billing data — Ortto is a capable, well-designed platform and the right tool for that work. But if you are not running campaigns and simply need to see who has gone quiet, whose payment failed, and who is waiting on a reply, Ortto is a messaging suite wrapped around the profile you actually want, where Signals gives you that timeline and those answers in ten minutes for a flat $29 a month.
| Signals | Ortto | |
|---|---|---|
| Cost | ||
| Published entry price | $29/mo Starter, $99/mo Growth | Starter ~$199/mo (third-party, approximate, as of July 2026); no cheaper tier |
| Higher tier price | $99/mo Growth, flat | Professional ~$509–599/mo (third-party, approximate, as of July 2026) |
| Pricing basis | Flat plan | Tiered by contact-list size |
| Contract terms | Month-to-month | Starter monthly; Professional+ annual commitment |
| Time to value | ||
| Time to first answer | ~10 minutes after connecting | 14-day free trial; onboarding framed as days to weeks |
| Historical backfill on connect | Data upload / import phase | |
| Effort | ||
| Getting started | Read-only OAuth, connect accounts | Self-serve trial; multi-phase onboarding (upload → integrate → QA) |
| What you operate | Nothing to configure | Journeys, campaigns, scoring model |
| Features | ||
| Unified customer timeline | Unified profiles/"activities" for campaign targeting | |
| Email sync (Gmail inbox) | No Gmail inbox sync | |
| Calendar sync (Google) | Campaign-scheduling calendar only; no meeting sync | |
| Billing and payments sync | Stripe subscription ledger | Stripe → activities (real integration) |
| Churn / at-risk signals | "Scores" flags inactivity as risk | |
| Journeys and omnichannel messaging | ||
| Answers "who needs a reply?" out of the box | ||
Where Ortto shines
Ortto is built for marketing orchestration, and within that remit it is genuinely strong. Its visual journey builder lets a marketing team design multi-step, branching workflows — trigger, wait, condition, send — without engineering, and those journeys reach across channels: email, SMS, push, and in-app messages all fire from the same canvas. Around that sits a full campaign toolkit, including forms and landing pages, so acquisition and nurture live in one place. Underneath is a real customer-data layer: Ortto merges marketing, product, and billing signals into single unified profiles, and its Stripe integration is a proper one, syncing customers, subscriptions, invoices, and charges into a near-real-time activity feed rather than a shallow export. Its "Scores" feature can weight engagement and flag inactivity as a negative signal, giving marketers a usable churn-risk or engagement lens for targeting. For an e-commerce or SaaS marketing team that wants to combine who someone is, what they bought, and how they behave — then act on it with a campaign — Ortto brings the data and the messaging together in a way that is hard to assemble from separate tools. As a marketing-automation CDP, it does the orchestration job well.
Where Signals is different
Ortto assembles a rich profile in order to message it; Signals assembles a timeline in order to answer questions about it. That distinction is the whole point. Ortto's unified profile exists so a marketer can target a segment and send something; there is a journey to design, a campaign to run, a scoring model to weight. Signals has none of that machinery. It reads Stripe, Gmail, Google Calendar, and OnePageCRM and produces one chronological record per customer, then tells you plainly who needs a reply and who is drifting toward churn — no journey, no send, no configuration. The source gap is concrete, too: Ortto does not sync a Gmail inbox or Google Calendar meetings as data — its "calendar" is a campaign-scheduling calendar — so the actual back-and-forth of email and the meetings you have held never enter its picture. Those conversations are central to Signals. Where Ortto sees a contact's marketing engagement, Signals sees the whole operational relationship: the payment that failed, the email that went unanswered, the meeting that happened last week. Signals is not a messaging tool and sends nothing; it is a lens that reports what is happening, for people whose question is "what do I do about this customer?" rather than "what campaign do I send them?"
Cost in practice
Ortto does not offer an entry plan cheaper than its Starter tier, and its pricing is built around the size of your contact list rather than seats or events. Third-party sources put Starter at roughly $199 a month covering around 5,000–10,000 contacts, with Professional around $509–599 a month at 10,000 contacts and Enterprise quoted custom, all as of July 2026 — and because we could not confirm these on Ortto's own pricing page during this check, they should be read as approximate secondary figures, not a vendor quote. The structure carries a commitment wrinkle as well: Starter can run month-to-month, but Professional and above generally require an annual plan. There is a fourteen-day free trial covering up to 10,000 contacts, and onboarding is framed by Ortto's own help materials as a multi-phase effort — data upload, then integrations, then QA — measured in days to weeks. Signals is a flat, published $29 a month on Starter or $99 on Growth, month-to-month, with no contact-list meter and no annual lock-in. The gap is not marginal: Ortto's lowest tier sits near roughly twice Signals' Growth plan, because you are paying for a messaging platform and its send infrastructure, not just the customer view underneath it.
A messaging suite, or the answer underneath it
The honest question before choosing Ortto is whether you are going to send. Ortto's value is concentrated in orchestration — the journeys, the emails and SMS and push, the landing pages, the segment-and-send loop a marketing team runs continuously. If that is your job, most of the platform earns its price. If it is not — if you have no campaigns planned and simply want to understand your customers and act one-to-one — then the messaging engine, the deliverability tooling, and the contact-tiered pricing are all overhead wrapped around the one piece you wanted: a unified view that flags who is at risk. That view is what Signals sells on its own, without the campaign apparatus around it, and it adds the email and calendar history Ortto never captures. The two are not really rivals. A marketing team might run Ortto for campaigns and still open Signals to see the operational truth — the failed payment, the unanswered thread, the meeting last Tuesday — that a marketing-automation profile is not built to surface. But if you are reaching for Ortto mainly to get that customer picture, you are buying a lot of machinery to reach a screen Signals gives you directly.
Switching to Signals
Signals connects to Stripe, Gmail, Google Calendar, and OnePageCRM over read-only OAuth, and it backfills your history automatically on connect, so there is no import project and nothing to migrate out of Ortto. Because Signals only reads and never sends, it runs happily alongside an Ortto account without touching your journeys, contacts, or campaigns. If you use Ortto to run marketing — journeys, email and SMS, landing pages — keep it for exactly that; Signals is not a marketing-automation tool and does not replace one, it just answers the who-needs-attention question from data Ortto does not fully see.