I've spent the first quarter of 2025 inside enough ActiveCampaign accounts to spot the pattern. Features that were functional but clunky in 2024 are now legitimately useful. The platform didn't announce most of these changes with webinars or feature launch emails. They just… improved things.
Four stood out. Each one changes what's possible in your setup, and each one means there's probably something in your account worth revisiting.
Conditional Content Blocks: Now Actually Reliable Enough to Use in Revenue Sequences
Conditional content in ActiveCampaign has existed for years. The problem was never the concept — show block A to segment X, block B to everyone else — the problem was the rendering. In 2024, I stopped recommending conditional content blocks in any automation that touched revenue because the failure mode was silent. A contact would hit the email, the conditional logic would evaluate incorrectly or not at all, and they'd either see a blank section or the wrong offer. You wouldn't know unless someone replied to complain.
Sometime in late 2024 and into early 2025, the rendering engine got better. The conditional logic now evaluates consistently, and more importantly, the preview mode inside the email builder now reflects what different segments will actually see. That last part matters more than it sounds like it should — being able to QA conditional emails without sending live tests to yourself means you can actually trust the feature in a sequence where the wrong block showing up costs you money.
What to revisit: any email sequence where you're currently splitting the automation with a conditional branch just to send two slightly different versions of the same email. The cleaner pattern now is one email with conditional content blocks keyed to tag presence, custom field values, or deal stage. You collapse two or three automation paths into one, the contact record stays cleaner, and you don't have to maintain parallel versions of what is functionally the same message.
The setup: inside the email builder, add a conditional content block. Set the display rule to something concrete — tag is "purchased-before" or custom-field-tier equals "premium" — and configure a fallback block for everyone who doesn't match. Send yourself a test as a contact who matches and one who doesn't. If both render correctly in your inbox, you're good to use it in production.
Predictive Sending: Coverage Expanded Beyond the Top 20%
Predictive Sending has been in ActiveCampaign since 2022, buried under the send options in campaign settings and automation emails. The idea is sound: the platform looks at each contact's past engagement times and sends the email when they're statistically most likely to open it, rather than sending everyone the same email at the same time.
The limitation in 2024 was coverage. Predictive Sending only worked for contacts who had enough engagement history for the algorithm to calculate a send-time window. In most accounts I worked in, that meant it applied to maybe the top fifth of the list — your most engaged contacts — and everyone else got the email at the default send time you configured as a fallback.
In 2025, the coverage threshold dropped. The feature now applies to a wider swath of your list because the machine learning model requires less historical data to make a prediction. I'm seeing Predictive Sending apply to 40–60% of recipients in accounts where it used to cover 15–25%. The fallback still exists for brand-new contacts or those with almost no opens, but the feature is now useful enough to turn on by default instead of treating it as an edge-case optimization.
What to revisit: any broadcast campaign or evergreen automation email where timing matters and you're not running a coordinated launch with a hard send time. Go into the email send settings, enable Predictive Sending, and set your fallback time to whatever you'd normally send the email. You're not giving up control — you're letting the platform handle micro-timing for the contacts where it has signal, and defaulting to your preferred time for everyone else.
The one place I still don't use it: emails that are part of a time-sensitive promotion where the offer expires at a specific hour. If you're sending a "sale ends tonight at midnight" email, everyone needs to get it at the same time. Predictive Sending spreading that delivery across a six-hour window kills the urgency.
Site Tracking: Fewer Gaps, Better Attribution in Automation Triggers
ActiveCampaign's site tracking script has always been the foundation of behavioral automations — someone visits your pricing page, trigger sequence A; someone hits the order confirmation page, add tag B and start automation C. The problem was reliability. Contacts would visit a page, the tracking pixel would fire, and the event would show up in the contact record… maybe. Or it would log twenty minutes later. Or not at all if the visitor had certain privacy tools enabled.
The gap between "page visited" and "event logged in ActiveCampaign" caused automations to misfire or not fire. I've seen accounts where a post-purchase thank-you sequence never started because the tracking event from the confirmation page didn't reach ActiveCampaign before the contact closed the tab.
In 2025, the site tracking reliability improved. Events are logging faster and more consistently. I don't have internal access to what changed on ActiveCampaign's side, but the practical result is that automations triggered by Visits a page or Submits a form conditions are firing when they're supposed to, not three hours later or never.
What to revisit: any automation that starts with a site event trigger and has a wait step immediately after it. A common workaround in 2024 was to insert a Wait 5 minutes step right after the site tracking trigger to give the event time to fully process and any associated tags or field updates to apply before the automation continued. If you built that buffer into your automations, you can probably remove it or shorten it. The tracking is now fast enough that the extra wait just delays your message for no reason.
Test this before you change it in a live revenue sequence: trigger the automation yourself, watch the contact record in real time, and confirm the event logs and the automation starts within seconds. If it does, kill the wait step.
Automation Debugging Tools: The Run Log Actually Tells You What Happened
ActiveCampaign's automation canvas has always shown you the structure of the flow — this email, then this wait, then this conditional split, then these two parallel branches. What it didn't show you was why a specific contact took the path they took, or why they didn't enter the automation when you expected them to, or why they skipped an email you thought they'd receive.
The Automation Run Log existed, but it was surface-level. You could see that a contact entered on a certain date and exited at a certain step, but the log didn't tell you which branch they took at a conditional split, or whether they hit a goal and jumped forward, or whether they were suppressed from receiving an email because of a segment condition you forgot was in the send settings.
In 2025, the run log got granular. It now shows every decision point the contact hit inside the automation, which conditions evaluated to true or false, and whether any emails were suppressed and why. This is the difference between guessing why a contact didn't receive an email and knowing exactly which segment condition or tag absence caused them to skip it.
What to revisit: any automation where you've had contacts "fall out" or skip steps and you never figured out why. Open the automation, click into the contact list from the automation overview, find a contact who didn't behave the way you expected, and review their run log. You'll see the exact step where they diverged and the logic that caused it.
The most common thing I find when I do this in client accounts: an email in the middle of an automation has a segment condition in the send settings that nobody remembers adding. The contact doesn't match the segment, so they never receive the email, and the automation just continues past it. The run log now surfaces that suppression explicitly instead of making it look like the email sent when it didn't.
ActiveCampaign evolves without fanfare. These four changes didn't get launch events because they're improvements to existing features, not net-new capabilities. But each one makes something that was fragile or unreliable into something you can actually build on.
If you're running a seven-figure operation on ActiveCampaign and you haven't revisited your core automations since late 2024, you're leaving setup improvements on the table. The platform got better. Your automations didn't automatically inherit the benefits.
If you want a second set of eyes on what's worth changing in your setup, I offer a free ActiveCampaign audit at getner.ai/audit.