ActiveCampaign for SaaS: Custom Events at Plus, Your Own Objects at Enterprise

A software company evaluating ActiveCampaign is usually asking one question: can it hold product data, not just email addresses. The answer is yes, from a specific tier, and the detail is worth knowing before you commit.

OUR TAKE: The pieces a SaaS lifecycle needs — custom events, custom objects, database sync, API on every tier and site tracking — are all here, but they arrive on three different tiers. Map your data model against the tier list before you price anything.

What a SaaS lifecycle actually needs

Four things, and ActiveCampaign carries all four under named entitlements in its vendor catalogue^[3], which is why this can be stated exactly rather than approximately.

Event ingestion, so a trial action can trigger a sequence. The custom events entitlement begins at Plus.

Object modelling, so a workspace or a subscription is a record rather than a contact field. Custom object records exist from Starter; custom object schemas, which is the ability to define new object types, are Enterprise only.

Two-way data movement, so your product database and your marketing database do not drift. The database sync entitlement begins at Plus. The API and webhooks are on every tier including Starter.

And behavioural signal, so you can tell a trialist who logged in twice from one who logged in twenty times. Site tracking and link tracking are in the base product; contact scoring begins at Plus.

## The tier map, in one place

Capability	First tier that has it
API and webhooks	Starter
Site tracking, link tracking	Starter
Custom object records	Starter
Custom events	Plus
Contact scoring	Plus
Database sync	Plus
Custom user permissions	Plus
Conditional content	Professional
Revenue attribution, conversions	Professional
Predictive sending	Professional
Custom object schemas	Enterprise
Single sign-on	Enterprise
Account activity logs	Enterprise
Salesforce, Microsoft Dynamics integrations	Enterprise

Read from the vendor's billing catalogue, where each row is a named entitlement^[3].

The honest reading of that table: a SaaS company doing anything beyond newsletters starts at Plus, and a SaaS company that wants its own object model starts at Enterprise.

The contact meter against a freemium product

This is the structural problem for software companies specifically.

Every signup is a contact. Every free user is a contact. Every churned trial is a contact, because "All contacts, regardless of their list status, count towards your contact limit"^[11].

A product-led company with a generous free tier accumulates contacts at a rate that has nothing to do with revenue, and this pricing model charges for all of them.

Contacts	Plus, $/mo	Professional, $/mo	Enterprise, $/mo
1,000	49	79	145
10,000	189	375	589
25,000	389	629	879
50,000	609	969	1,169
250,000	2,399	2,399	2,759

All annual rates, from the catalogue^[3]. Note the last row: at two hundred and fifty thousand contacts Plus and Professional cost exactly the same, so the capability difference becomes free at that scale.

If your free tier is large, model the band against signups rather than against customers. That is the number that moves the invoice.

## What happens at the limit, and why it matters more here

Sending stops; billing does not move. "Once you reach your contact limit, you will not be able to send any email campaigns until you upgrade your account"^[9], with automations continuing to run while their send steps are skipped.

For a SaaS product that is a specific failure mode: your onboarding sequence appears to be running and new signups receive nothing. The automation log shows activity. The emails do not arrive.

Auto-upgrade is the opt-in that changes this^[10], and for a product-led company it is close to mandatory, because signup volume is not something you control week to week.

The pipeline question for a sales-assisted motion

If your motion is product-led only, skip this section. If you have an inside sales team, read it twice.

Pipeline management, deal records, account records and lead scoring are each marked "Included in add-on" on every tier that offers them^[2], and the price of those add-ons is published neither on the pricing page nor in the vendor's own billing catalogue, where the relevant entitlements carry empty price ladders^[3].

So the common SaaS plan — marketing automation and a lightweight pipeline in one system, avoiding a second CRM subscription — is available here at a price you cannot find out in advance.

Our suggestion is to price that add-on before you compare tiers, because it may change the comparison entirely.

## Transactional email and the product itself

Most SaaS products send two streams. Lifecycle mail, which belongs in a marketing tool, and product mail, which belongs somewhere reliable and fast.

ActiveCampaign's catalogue carries Postmark as a separate product at fifteen dollars a month for ten thousand emails^[3], which is the vendor's answer for the second stream. The send allowance on your plan explicitly excludes transactional mail: "This does not include 1:1 or transactional emails"^[8].

That is a clean separation and it is one more line that is not on the pricing page.

Security and compliance, which gate at the top

Single sign-on is an Enterprise entitlement. So are account activity logs, which is the audit trail most security reviews ask for. HIPAA support appears in the platform section of the feature matrix^[2].

If your buyers run vendor security reviews, those three items probably decide your tier before any feature does, and the Enterprise tier at your contact band is the real price of the product.

Note that Enterprise here is still self-service: the pricing page generates an ordinary signup link with tier=enterprise, so it is a purchasable tier rather than a quote, although a separate request-pricing path exists alongside it.

## Integrations, including one unusual line

The vendor's marketplace counts 1,056 apps and integrations, rendered as a filter result rather than claimed in copy^[16], and the API and webhooks are on every tier.

Two entries matter for software companies. Salesforce and Microsoft Dynamics are Enterprise-only entitlements^[3], so a company already running Salesforce should price Enterprise from the start. And the integrations accordion names "Claude & ChatGPT (via MCP)"^[2], which no other product in our set publishes.

One oddity we report without resolving: the catalogue carries a Zapier entitlement on the Plus tier and on no other, while the pricing page lists Zapier with no tier marked at all.

The exit, which a SaaS company should model

Three published facts.

No refunds of any kind^[6]. A cancellation lands at the end of the current period, and on a commit-annually plan it requires contacting support rather than clicking^[7].

Automations have no file export. The only published route is a share link that carries none of the campaigns, lists, scores, deals, pipelines, events or whitelisted domains the automation references^[14]. For a company whose lifecycle logic is a competitive asset, that logic is not portable.

And access to contact data ends at cancellation: "Upon cancellation or termination, you will not have access to or be able to restore any Contact Data"^[5]. The terms add that the service "does not serve as a repository for Contact Data" and that independent backups are your responsibility.

The last one is easy to satisfy and easy to forget. Schedule a monthly contact export from day one.

There is a second-order version of the same problem worth naming. A software company's lifecycle logic usually encodes product knowledge: which activation event predicts retention, which trial behaviour signals intent, which sequence recovers a stalled onboarding. That knowledge lives in the automation, and the automation is the one asset here that leaves no file behind. If it matters to you, document the logic outside the tool as you build it rather than reconstructing it later from an interface you no longer have access to.

Where the entry tier fails a software company

It is worth being specific, because Starter is cheap enough to tempt an early-stage team.

Eleven entitlements in total^[3]. No custom events, so a trial action cannot trigger a sequence. No database sync, so your product database and your contact database drift from week one. No contact scoring, so every trialist looks the same. No custom user permissions, so everyone who logs in sees everything.

Then the fixed ceilings. Five lists, and five actions per automation, both recorded with maximum units equal to included units, which means money does not raise them^[3]. A standard onboarding sequence of welcome, activation nudge, a condition on whether they completed setup and two branches is already at or past five actions.

That last constraint is the one that catches technical teams, because it is invisible until you build. The five actions are not five emails. A condition is an action. A wait is an action. A webhook back to your own system is an action. So the entry tier runs linear sequences and nothing that branches, which is most of what a product-led lifecycle needs.

And two seats maximum, against nine hundred and ninety-nine on every tier above.

The honest summary is that Starter is a newsletter plan. For a software company it is not a cheaper version of the product; it is a different one.

The billing term, and what it costs you to save

The annual term is between 16.9% and 21.6% cheaper across the bands we measured^[3], which on a Plus plan at ten thousand contacts is a meaningful line in a small budget.

It also removes two options. An annual account cannot be paused: pausing is three months maximum, once every twelve months, and "The Pause option applies to monthly plans only", with commit-annually accounts explicitly excluded^[12]. And a commit-annually plan "must contact our Customer Experience team to cancel"^[7] rather than cancelling from the dashboard.

For a company whose own product is sold on monthly terms, that asymmetry is worth noticing before signing it.

There is also a third term the pricing page never names: commit annually, pay monthly, worth up to ten per cent, published only in the help-centre article about cancelling^[7].

Documentation, which is a real advantage here

Software companies evaluate vendors partly on how much they have to ask, and this one asks little.

The help centre publishes the overage rate, the shutoff threshold, the warning percentages, the reset rules for both billing terms, the export columns, the download link validity, the pause limits, the trial ceiling, and a dedicated article on how contacts are counted^[8]. Each article carries a last-updated date and most are current within weeks.

Against that, two defects worth knowing. The terms of service and the help centre give different answers about what happens when you exceed the send limit^[5][8]. And the anti-spam policy that governs automatic suspension is stamped September 2021, five years older than the terms beside it.

## The shortest useful summary

Map your data model to the tier table first. Custom events and database sync mean Plus. Your own object schemas, single sign-on and audit logs mean Enterprise.

Then model the contact band against signups rather than customers, decide auto-upgrade on purpose, and price the CRM add-on if you have a sales team.

And treat the automation logic as something you own only while you are paying, because it is the one asset in this account that does not come out in a file.