Most ActiveCampaign accounts are running at maybe 40% of the platform's capability. Not because the operators are lazy, but because the features that separate a good program from a great one are one layer deeper than where tutorials stop.
Here are the six I most often find dormant when I take over an account. None of them require a higher plan tier for most of what I'll describe (I'll note where they do). All of them are the kind of thing that would take an afternoon to enable and months to build a substitute for.
1. Conditional content blocks inside emails
This one changes how you think about broadcasts. Inside AC's email designer, every content block has a "Show/Hide when…" condition. You can gate a block by tag, list, custom field, segment — anything you can describe in the normal segment builder.
What this means in practice: one monthly broadcast can contain three entirely different CTAs for three different customer tiers, and each contact only sees the block relevant to them. No duplicate broadcasts. No parallel automations. No "which version do I send to which segment" spreadsheet.
Real example: a client with three offer tiers — free subscribers, $99/month members, and $2,000 mastermind clients. The pre-audit newsletter was three separate broadcasts built in parallel, maintained by hand, and routinely out of sync. We collapsed it into one broadcast with three conditional content blocks. Each contact sees only the tier-appropriate CTA. Edit time per newsletter dropped from 90 minutes to 20.
The feature is sitting in the block settings panel. Most operators never open that panel because there's nothing obviously wrong with their current emails.
2. Site tracking (beyond ecommerce)
Site tracking is the script that ties anonymous browsing on your website to known AC contacts once they're identified (usually via a form submission or a link click from an email). Ecommerce setups turn it on because ActiveCampaign's documentation leads with ecommerce examples. Everyone else tends to skip it.
That's a mistake. Once site tracking is on, you can trigger automations on specific URL visits. Which means you can react to behavioral signals that would otherwise be invisible:
- A contact visits your pricing page twice in a week → tag them
beh-high-intentand notify your team. - A contact visits your "Careers" page → exclude from sales automations, flag as not-a-buyer.
- A contact reads three FAQ pages in a session → send a targeted "Questions I usually get" email the next day.
- A contact opens your pricing page but never clicks "Start" → enter a low-key "reasons people hesitate" sequence.
Setup is one script tag and enabling the feature in the account settings. The payoff is every automation you build from that day forward has a new dimension of triggers available.
3. Sub-automations (Start Another Automation)
Inside any automation, you can add a "Start another automation" action that kicks off a separate named automation for the same contact. This sounds boring until you see what it unlocks.
Most consultants build parallel automations that duplicate logic. Five welcome paths, each with its own "final tidy-up" sequence at the end: apply the "onboarded" tag, add to the monthly newsletter list, remove a temporary behavioral tag, fire an analytics event. When the tidy-up logic changes, they edit five automations.
The fix is one shared "end-of-onboarding-cleanup" sub-automation, called from each of the five parent flows. Change the logic once, every path inherits the change. This is the DRY principle from software engineering applied to automation design, and it scales beautifully as an account grows.
Corollary: if you find yourself copying the same four-step block between automations, it should almost certainly be a sub-automation.
4. Predictive Sending (when your plan has it)
If your plan includes Predictive Sending, AC looks at each individual contact's historical open behavior and delivers the email at that person's most-likely-to-open window. Not "Tuesday at 10am for everyone" — 10am for the 10am openers, 9pm for the night owls, Saturday morning for the weekend readers.
Two things consistently happen when I turn this on:
- Open rates on broadcasts move up 8-18%, depending on how clumped the list was before.
- The subset of your list who only open on weekends, or only at 11pm, finally start engaging — because they were never seeing your emails at an opportune moment.
The reason operators don't use it: most don't know it's there. It's a toggle in the broadcast/campaign send step, not a headline feature. Once you enable it on your primary newsletter, you'll see why broadcast-send-time A/B tests were always going to be noisy.
5. Deal pipelines for workflows that aren't sales
Deal pipelines are the "CRM" side of AC, and most operators use them only for sales: prospect → discovery → proposal → closed-won. That's half of what they can do.
A pipeline is just a named sequence of stages with automation hooks. You can build one for anything with discrete stages:
- Application review for boutique services. Received → reviewed → short-listed → interviewing → accepted → declined. Stage changes trigger applicant-facing automations (acknowledgment, next-steps email, decision letter) and internal notifications.
- Course cohort progress. Enrolled → week 1 complete → week 4 complete → graduated → alumni. Segment your email content to people actually at that stage. Offer an alumni upsell only to people who reached "graduated."
- Service onboarding. Paid → kickoff scheduled → kickoff done → milestone 1 → milestone 2 → complete. Each stage change triggers an internal checklist and a client-facing progress email.
The feature cost is zero — you already have the pipelines tool. The payoff is replacing messy tag-based stage tracking with a visual, report-friendly, automation-native representation of any multi-step process.
6. Date-based custom fields with rolling segments
Most consultants track "when did X happen" with a tag: purchased_2025_03, webinar_2025_04_12. That approach loses precision and ages badly.
The better pattern: a date-type custom field like Last Purchase Date or Signup Date, and segments that use it as a rolling anchor.
The magic is the segment conditions. AC lets you write segments like:
- "Last Purchase Date was exactly 30 days ago"
- "Signup Date is more than 180 days ago AND fewer than 365"
- "Subscription Renewal Date is in the next 14 days"
Each of those segments can trigger an automation on entry. That means you get a perfectly timed touch — 30 days after purchase, 6 months after signup, two weeks before renewal — without building a "wait 30 days" step into every flow and hoping the contact doesn't exit early.
Why it matters: timing is the most undervalued lever in retention. A "happy one-month anniversary" email that goes out exactly 30 days after purchase outperforms a generic quarterly newsletter by a factor I've stopped being surprised by. The date-field-plus-rolling-segment pattern is how you make that timing automatic and durable.
Pick one, enable it this week
If you read through that list and thought "I'm doing half of these," congratulations — you're already in the top tier of AC operators I see. If you read through and realized you're doing none of them, that's not bad news. It's a runway.
Pick one. The fastest win for most accounts is conditional content blocks, because the payoff starts on the next broadcast you ship. The longest-term compounding win is site tracking, because every automation you build from that point forward gets smarter. The highest-leverage for sales teams is deal pipelines for non-sales workflows. The one operators are most embarrassed they missed, once they see it, is sub-automations.
I'd rather you enable one of these properly than four of them half-heartedly. The platform rewards deep implementations of a few features more than shallow adoption of many.