How to read automation logs

Every action an automation takes is recorded in the Automation logs. Logs let you verify what an automation did, understand why an action was skipped, and identify what went wrong when an error occurs.

Where to find logs

You can access logs in two ways:

From the Automations table - Click the Logs icon in an automation's row to open the log history for that specific automation. If you want to view logs for multiple automations at once, select them and use the View Logs option in the bulk actions bar.
From the Automation logs tab - Open the Automation Logs tab directly to view log entries across your automations.

Default view and Full Logs

By default, the Logs view shows only the entries where an automation's conditions were met and an action was triggered.

The system also records every condition check - including checks where the conditions were not met and no action was taken. To see these entries, enable the Full Logs toggle.

Use Full Logs when:

Your automation has not triggered and you want to confirm whether it has been evaluated at all.
You want to see the full history of condition checks, not just triggered actions.

Note: If Full Logs shows that an automation was checked but all entity columns display 0, it means there are currently no entities that the action can be applied to.

Log statuses

Each log entry shows one of three statuses.

- Successful

The automation's conditions were met and the action was executed.

When you click on a Successful entry, you can see:

The entity the action was applied to (including its ad group, campaign, app, and campaign group details).
The old value before the automation ran.
The new value after the action was applied.

For example, if a keyword bid change was triggered, the log will show the keyword, the bid value before the automation ran, and the new bid value after the action.

- Warning

The automation evaluated the rule but could not take action, even though conditions may have been met.

When you click on a Warning entry, you can see the reason why the action was not taken.

For example, if an automation is applied to a multistorefront keyword using an Apple SOV condition, the action cannot trigger because SOV is only available at the storefront level. In this case, the automation skips the action and records it as a Warning.

If you see Warning entries, review your condition configuration and check that the metric you are using is compatible with the automation level and entity.

- Error

The action failed due to an operational or API-related issue.

When you click on an Error entry, the system displays the specific error message so you can understand what went wrong.

If you see Error entries, see How to fix issues with Automations for next steps.

Need more help?

If you have further questions on the process, contact your dedicated Customer Success Manager or contact the support team via live chat!