Automation

Automation rules connect something that happens on your site to one or more actions AcquisitionSuite takes automatically, without you enrolling anyone by hand. Every rule follows the same IF / THEN shape: IF a trigger fires and its conditions match, THEN run the actions attached to it. Go to Automation → Add New to build one.

Triggers

A trigger is the “when.” Choose exactly one per rule:

Form Submit — any form submission
File Download — a free file was downloaded
Paid Download — a paid file was successfully purchased
Payment Successful / Payment Failed — either outcome of a checkout attempt
Score Change — a lead’s score changed, in either direction
Tag Added — a tag was applied to a lead
Email Open / Email Click — a lead opened or clicked a link in an email you sent
Page Visit — a tracked page was visited
Repeat Visit — a previously-seen lead returned to the site
Product Interaction — a custom event, for integrations that record their own interaction data
Time-Based — runs on a schedule instead of a live event, checking each lead’s current data

Conditions (optional)

Conditions narrow down which leads a trigger actually fires the rule for, leave them empty to run for every lead that matches the trigger. Conditions are organized into groups: every condition within a group must match (AND), but only one group needs to match overall (OR). This lets you build rules like “(country is Nigeria AND score > 50) OR (tag is vip-customer)” in a single rule.

Actions

An action is the “then.” A rule can run more than one action, in order:

Send Email — a one-off email, outside of a sequence
Enroll in Sequence — start a lead on an email drip sequence
Send WhatsApp — requires a connected WhatsApp Business number, see below
Send Webhook — POST a JSON payload to any URL, the way to connect AcquisitionSuite to Zapier, Make, a CRM, or any tool with an incoming webhook
Add Tag / Remove Tag
Set Segment
Add Score Points
Move to Pipeline Stage
Update Lead Field — overwrite one of the lead’s own submission field values
Notify Admin — email a site admin address

Run once per lead

Check this box to prevent a rule from firing more than once for the same lead, useful for anything that shouldn’t repeat, like a welcome sequence or a one-time tag, on a trigger a lead could otherwise match multiple times.

Building a rule

Go to Automation → Add New. Name it, choose one trigger, optionally add conditions, add one or more actions, and save. Rules run in the order they’re listed when more than one could match the same event, drag to reorder if sequence matters for your setup.

A few real examples

Instant follow-up: trigger “Form Submit,” action “Send WhatsApp” with a quick acknowledgment, often opened faster than email. Re-engagement: trigger “Score Change,” condition “score is less than 20,” action “Enroll in Sequence” (a re-engagement drip). Sales handoff: trigger “Payment Successful,” actions “Move to Pipeline Stage: Customer” and “Notify Admin.” CRM sync: trigger “Form Submit,” action “Send Webhook” to your CRM’s incoming-lead endpoint.

WhatsApp setup

Sending WhatsApp messages requires connecting a WhatsApp Business number first, under Settings → Integrations (Meta Cloud API or Twilio). Once connected, “Send WhatsApp” becomes available as an action on any rule, the lead’s phone number is taken from whichever form field was mapped to Phone.

Automation vs. sequences

A sequence is a fixed series of timed emails. Automation is the layer that decides who gets enrolled in one, and what else happens alongside it, tagging, scoring, webhooks, and pipeline movement included. Most real setups use both together: automation rules watch for the right moment, sequences handle the follow-through. See Email sequences.