Automations & campaigns

Campaign log

Everything sent and its status

A log of every time an automation ran: the step, the message, the channel, the result, and whether the customer actually bought afterwards.

Open the page in the dashboard

What the log records

Each row is one run of a built-in automation for one customer: the automation, step, customer, message text, channel, time, result and its reason, and whether the customer bought afterwards and for how much.

This is where you answer “what happened to this customer?”. Press the customer's name to open their profile, or open their journey to see everything they received in order.

Run results

Result	What it means
Sent	The message went out to the provider.
Delivered	The platform confirmed it reached the customer's device.
Read	A read receipt came from the platform.
Skipped	A protection or a condition stopped it; the reason is written below. That's correct, not a fault.
Failed	The provider refused it; the reason is written below.

“Bought?” counts only for a sent message: “Yes” if the customer bought within the attribution window after it (14 days by default). With no message delivered it shows “—”, because there's nothing to attribute a purchase to.

Read the log

The filters at the top; the period and the export button in the page header.

Find out why a message didn't arrive

1
Find the customer
In “Search (name or number)” type the name or the start of the number, such as 96650, then “Filter”.
2
Filter by result
Under “Result” pick “Skipped” or “Failed”. The reason is written under the badge.
3
Fix the reason
Outside the 24-hour window with no approved template → pick a template for the step. WhatsApp not connected → connect the number. Weekly limit exceeded → the protection is working; nothing to fix.
4
Export if needed
The export button downloads the log with the current filters and period.

Common skip reasons

Weekly limit exceeded

What it is: The customer got two marketing automation messages in 7 days.
When to use it: Normal when many automations run.
How to start: Do nothing, or switch off the least important automation.

Customer never replies

What it is: They got 5 marketing messages and never replied.
When to use it: Protects your number's rating.
How to start: Do nothing.

Outside the 24-hour window, no template

What it is: The customer hasn't written in 24 hours and there's no approved template.
When to use it: A setup mistake.
How to start: Get a marketing template approved and pick it for the step.

WhatsApp daily limit

What it is: The number reached its daily Meta limit.
When to use it: A day with a big campaign.
How to start: The message is tried again at the next check once the limit frees up.

Step condition

What it is: Such as “If not purchased” when the customer bought.
When to use it: That's what you wanted.
How to start: Nothing.

Use the log well

Open it after the first day of any automation — mistakes show here before they show in sales.
If most rows are “Skipped” for one reason, fix that reason first.
The log shows built-in automations. Results for custom automations are on “Automation performance” after you pick one in the filter.

Common mistakes and how to fix them

ProblemIt says “No runs match this filter”.
FixWiden the period or clear the filters. If it stays empty, no automation is on — check “Automated campaigns”.
ProblemReading “Skipped” as a fault.
FixMost skips protect your customers. Read the reason before changing anything.

Screenshot from a demo store

Parts of the page

1
A row
Each row is one run for one customer. “Result” says whether the message was sent, skipped or failed, and why.
Example“Skipped: customer unsubscribed” means protection stopped the message — correctly.
2
Bought?
A purchase counts only if the message arrived and the customer bought afterwards. No message, nothing attributed.

Playbooks that use this page

Launch your first campaign without annoying customers

Was this helpful?

Didn't find your answer?