Send like you know them.
Because you already do.
Campaigns, journeys and audiences built on what a person has already done with you. No second list to sync, no send that goes out of date.
Three parts. One list underneath all of them.
Audiences
Named groups built from a filter over everything a person has done with you, recounted every time they run.
Campaigns and journeys
One email to an audience, or a sequence over days with the rule for leaving it set alongside the rule for entering.
Analytics
Your own site measured first-party, behind a consent banner that actually blocks the trackers.
Build the audience once. It keeps itself current.
An audience is a filter over everything a person has done with you, not a list you exported. It recounts itself every time it runs, and the same audience feeds a campaign or enrols a journey.
- Dynamic audiences recount on every run
- Static lists stay available for the times you want one
- One audience feeds campaigns and journeys alike
Send the email. See exactly what happened to it.
Write the email, pick the audience, and watch the send resolve contact by contact: delivered, opened, bounced, unsubscribed, every state on the record it belongs to.
- Every send resolves per person, not per batch
- One-click unsubscribe in every send
- A hosted preference centre contacts manage themselves
Know when to stop. Not just when to start.
A journey runs over days: sends, waits and yes/no branches. Give it an exit goal and it stops chasing anyone who has already done the thing you were asking for.
- Enrolment by hand, by list or on a trigger
- An exit goal ends the sequence for whoever converts
- Every step logged, so the path is readable afterwards
The form you already have. No embed code.
The forms on your site are captured as they are. When the person filling one in is already on file, the submission lands on them rather than making a second copy of the same human.
- Your existing forms, captured without a rebuild
- Known people are matched, not duplicated
- Field mapping you control, submissions encrypted at rest
Your website, measured. In your account, with consent that means it.
Consent is the mechanism. Not a banner over the top.
Visitors see a consent banner you design, with four categories. Behind it, a cookie scanner catalogues every script on your site and keeps each one blocked until its category is approved.
- Four categories: necessary, analytics, marketing, personalization
- A cookie scanner that catalogues every script
- Tracker blocking until consent
Measurement. Cookie-free by default.
One small script tracks pageviews, funnels, goals and custom events, first-party. There is nothing to gate, because nothing leaves your site.
- One small script, cookie-free by default
- Funnels, goals and custom events
- A live visitor count for launch day
When someone consents. Their history joins the record.
A stranger reads your site for weeks before they fill anything in. When they finally do, up to 90 days of that anonymous history attaches to the new record automatically, encrypted at rest.
- Up to 90 days of history attaches on consent
- Automatic, and encrypted at rest
- The new contact lands in Audience, not in a report
Plan your content. Beside the campaigns it feeds.
A board of what is an idea, what is being written and what is scheduled, with a list and a calendar over the same items. It plans the work; your website stays where it is.
Against your ESP. And the export that feeds it.
The tool is fine. The copy of your list living inside it is the problem, and it starts drifting the day you connect it.
| An ESP beside your CRM | Mercleo Marketing | |
|---|---|---|
| Building a segment | Export, upload, and it starts ageing | A live query, right when it runs |
| Sending after someone already said yes | The ask goes out anyway | The journey has already let them go |
| Handling an unsubscribe | Two lists to reconcile | One record, everywhere |
| Adding a form | An embed code and a developer | The form you already have |
- Also in Marketing
- Drag-and-drop editor
- Saved templates
- Brand kits
- Sender domains
- Lists and segments
- A/B ready templates
- Scheduled sends
- Quiet hours
- One-click unsubscribe
- Hosted preference centre
- Bounce handling
- Journey enrolment by list, trigger or hand
- Exit goals
- Step-level logs
- Form field mapping
- Encrypted submissions
- Content board, list and calendar
- Pageviews and referrers
- Realtime view
- Funnels
- Custom events
- Goals
- Form funnels
- Paid channel reporting
- Cookie scanner
- Tracker blocking
One record. And your Marketing built on it.
Questions we get asked.
Journeys act on people over time: send, wait, branch. Workflows act on records the moment something changes. The short test: sending something to a person is a journey, changing something on a record is a workflow.
Give the journey an exit goal. Anyone who converts on it stops receiving the rest, so a renewal sequence never nags a member who already renewed. Unsubscribes, bounces and complaints exit an enrolment too.
No. The forms you already have are captured automatically: no embed codes, no rebuilds. A submission from someone already on file lands on the person you have, rather than making a second copy of them.
A dynamic audience is a filter, so it is recounted every time it runs and is right on the day you send. A static audience is a fixed list of people you chose. Most audiences should be dynamic; an uploaded list is only ever the static case.
No. Your website is measured the same way, and what it learns lands on your actual contact records rather than in a report.
No. The banner, the cookie scanner and the tracker blocking are part of Marketing, not a second subscription.
Up to 90 days of their anonymous history attaches to the new record automatically, encrypted at rest.
Yes. Sender domains are verified in settings.
One-click unsubscribe and a hosted preference centre are part of every send. Contacts choose what they get; the list stays clean on its own.
No. It plans what goes out and when, beside the sends and the records it is about. Your website stays where it is.
It works on its own. The people campaigns write to come with your account, so sends, journeys and forms have somewhere to land from day one.