Marketing automation: segmentation, consent and measurement

Marketing automation works when it sends the right message to someone who asked for it, at a moment that follows from something they did. It fails when it becomes a faster way to blast a list. This guide covers the parts small teams tend to skip: getting CRM data into shape, handling consent and unsubscribes properly, and running a pilot you can actually measure.

Start with CRM data you can trust

Every workflow is only as good as the fields it reads. Before building anything, check that each contact record has:

• An email address that is unique in the system, with duplicates merged.
• A consent status, the date it was given, and where it came from (form, purchase, event).
• A lifecycle stage you actually use, such as lead, customer, past customer.
• The last meaningful action: last purchase, last inquiry, last booked call.
• A country or region, because consent rules depend on where the recipient is.

If half of these fields are empty, fix data capture first. For a ten-person company, adding a consent checkbox and a source field to the contact form is usually a better first step than buying another tool.

Consent depends on where your recipients are

The rules differ by country, and this is not legal advice. Use the regulator's guidance for each market you send to, and ask a lawyer when you are unsure.

• In the United States, the FTC's CAN-SPAM guide sets an opt-out model for commercial email: identify yourself, include a valid physical postal address, give a clear way to opt out, and honor opt-outs within 10 business days. The opt-out mechanism must keep working for at least 30 days after you send.
• In the UK, the ICO's guidance on PECR says you must not send marketing email to individuals unless they have specifically consented. There is a narrower "soft opt-in" for existing customers who bought or discussed buying a similar product from you, as long as you gave them a clear chance to opt out when you collected their details and in every message. It does not cover bought-in lists or prospects. The ICO notes this guidance is under review after the Data (Use and Access) Act, so check the current page before relying on it.
• For recipients in the EU, Argentina or elsewhere, check the local data protection authority's guidance. Do not assume the US model applies.

The practical rule for a small team: store the consent basis on the contact, and make every workflow check it before sending.

Unsubscribe and suppression

Unsubscribes are where automation most often goes wrong, because the same person can be in five workflows, a sales sequence and next month's import.

Build it like this:

1. Keep one global suppression list in the CRM: everyone who unsubscribed, complained, or asked not to be contacted. The ICO recommends keeping such a "do not contact" list and screening marketing lists against it.
2. Every workflow, sales sequence and list import checks that list before sending. No exceptions for "just this one campaign".
3. Process unsubscribes automatically, not from a weekly inbox review.
4. Never re-add a suppressed address through a list upload. Make the import step check suppression first.

If you send to Gmail addresses at volume, Google's sender guidelines add technical requirements. All senders need SPF or DKIM authentication and must keep the reported spam rate below 0.3%. Senders of more than 5,000 messages a day to Gmail accounts also need SPF, DKIM and DMARC, and marketing messages must support one-click unsubscribe with a visible unsubscribe link in the body. Ask your email platform whether it sets the one-click unsubscribe headers for you, and check your domain's DNS records yourself.

Segments that lead to a decision

A segment is only useful if it changes what you send. Tie each one to a trigger and a stop condition.

Notice what is missing: a monthly newsletter to everyone. That can still exist, but it is not automation and it should go only to people with a valid consent basis.

Run a measurable pilot instead of a blast

Pick one workflow from the table, usually the new-inquiry follow-up, and treat it as an experiment.

Define the outcome first

Choose one conversion that happens in your CRM, not in the email tool: a booked call, a reply, a purchase. Write down how you will count it before launching.

Hold out a control group

Randomly leave a share of eligible contacts out of the workflow. Without a holdout, you cannot tell whether people booked because of the email or would have booked anyway. Small lists give noisy results, so run the pilot long enough to collect a meaningful number of contacts in both groups, and be honest if the difference is too small to call.

Track the costs, not just the wins

• Unsubscribes and spam complaints per send.
• Replies from people annoyed by the message.
• Time your team spends handling the workflow's output.

Be careful with opens

Apple says its Mail Privacy Protection downloads remote content in the background by default, whether or not the person engages with the email. That means open rates can count messages nobody read. Use clicks, replies and CRM conversions as your main measures.

Decide in advance

Write the decision rule before launch, for example: "If the workflow group books more calls than the holdout and complaints stay low, we keep it and build the next one. If not, we change the message or drop it." That stops a pilot from drifting into a permanent workflow nobody reviews.

Where automotif fits

This is automation builds work: we connect your forms, CRM and email platform in your own accounts, build the consent check and global suppression into every workflow, and set up the holdout so you can see what the pilot did. If you want to map one workflow with us first, book a free call for 30 to 60 minutes.

Sources

• CAN-SPAM Act: A Compliance Guide for Business
• Electronic mail marketing (ICO guide to PECR)
• Email sender guidelines (Gmail Help)
• Mail Privacy Protection & Privacy (Apple)