Auditor

Schedules

Schedules let you run audits automatically on a recurring basis. Set it and forget it. You will be alerted immediately when a pixel breaks.

Overview

Schedules turn a manual audit into a 24/7 regression test. Configure the frequency once, pick who gets the email alerts, and Auditor takes care of the rest. You don't have to remember to click Run, and you don't have to wait for a client complaint to discover tracking broke two weeks ago.

Each schedule runs exactly one audit. If you want to cover different parts of the site on different cadences, for example the homepage every 4 hours and the full checkout funnel daily, create a separate schedule for each combination.

Go to Auditor > Schedules from the left sidebar to see every schedule configured on the property. Click Add Schedule in the top right to create a new automated schedule.

The list shows next-run time and last-run status per schedule, so at a glance you can see everything that's about to fire and whether the last execution passed.

Select the audit

Pick the audit this schedule should run from the dropdown. Every schedule runs exactly one audit, so if you want multiple audits on the same cadence, create separate schedules pointing at each.

The audit must already exist before you can attach a schedule to it. If the dropdown is empty, head back to the Audits page and create one first.

Set the frequency

Choose how often the audit runs: Every 4 hours, Every 6 hours, Every 12 hours, Daily, Weekly, Monthly, or Manual. Select the timezone your schedule should interpret run times in, typically your property's local timezone so daily runs happen at a predictable local clock time.

Pick a frequency that matches the site's deploy cadence. High-traffic e-commerce sites that deploy multiple times a day benefit from 4-hour intervals. Static marketing sites with weekly content updates are fine on Daily or even Weekly.

Enable notifications

Configure email alerts so you're notified the instant an audit fails. You can set up notification groups with multiple recipients, which is useful when you want the whole marketing ops team plus the client to get the heads-up simultaneously.

The alert email links directly to the failed audit run so the recipient can click through to screenshots and logs without hunting. If no one is on the email list, failures still record in the dashboard but no one finds out until someone checks, which defeats the purpose of scheduling.

Activate the schedule

Save the schedule and toggle it to enabled. Auditor will start running the audit at the configured interval. The first run happens at the next matching time slot, not immediately on save, so use Run Now if you want to validate the setup right away.

Tips

Use the Run Now button to trigger a scheduled audit immediately without waiting for the next interval, which is useful when you've just shipped a fix and want to confirm the issue is resolved. Schedules respect your property's timezone setting, failed audits send an email alert with a link to detailed results, and Manual mode means the audit only runs when you explicitly trigger it.

Troubleshooting

Schedule is enabled but never runs

Check the timezone. If the schedule was configured in a different timezone from the one you're reading the dashboard in, the next-run time might appear correct but the job was actually skipped because the clock never matched. Re-save the schedule with the right timezone and confirm the next-run time looks correct.

Email alerts aren't arriving

Check the recipient's spam folder first, then verify the address is correct in the notification group. If both look fine, confirm your organization's mail system accepts mail from Auditor's sending domain. Some corporate filters silently quarantine transactional mail from unfamiliar senders.

Audit runs but doesn't email on failure

Notifications are configured separately from the schedule itself. Open the schedule, confirm a notification group is selected, and confirm the group has at least one recipient with a verified email. If the group is empty, failures are logged but no email is dispatched.