Where settings live
Open Auditor > Settings from the Auditor sidebar. Settings are scoped to the currently selected property, so different properties can have different defaults. The values here apply to every audit run on the property until you change them.
Final Wait Delay
Final Wait Delay (in seconds) controls how long Auditor's browser stays open after a page is considered loaded. Default is 5. The delay matters because some pixels fire late: a CMP that loads its own scripts asynchronously, a tag that waits for an idle callback, a vendor SDK that initializes after a few seconds.
If audits frequently miss late-firing pixels, increase this number before you start adding script-level wait steps to each audit. Settings is the cheaper place to fix it.
Execution Mode
Pick Simple for the default fast path. Audits run a single navigate-and-wait against each URL and check pixels. This is the right choice for most sites.
Pick Advanced for sites that need richer scripted flows: multi-page checkouts that need form fills, audits that have to dismiss a popup before pixels fire, or any audit that uses script steps beyond a single navigate. Advanced mode is required for those scripts to execute.
HAR Capture Options
Capture Request Bodies controls whether HAR files include POST request payloads. Off (default) keeps HAR files small and is fine for most validation: query-string parameters and event names are captured either way.
Turn it on if any of your audit rules validate the body of a POST request: GA4 Measurement Protocol, Meta CAPI server-side, anything that sends data inside the request body rather than the URL. The HAR files grow noticeably larger with this on, which is the trade-off.
If a rule fails with empty or missing payload data when you'd expect content, Capture Request Bodies is the first thing to check. It's a silent setting: rules don't tell you the payload was discarded, they just don't match.
When changes take effect
Settings apply on the next audit run. In-flight runs continue with the previous settings. If you change Execution Mode to Advanced and want to re-run yesterday's failed audit, save the setting first, then click Run.
Troubleshooting
Pixels still missing despite a 30-second Final Wait Delay
That's usually a sign the pixel actually depends on user interaction (a click, a scroll, a checkout step) rather than just time. A longer wait won't help; the audit needs script steps that simulate the interaction. Switch to Advanced mode and add the steps to the audit itself.
RequestPayload validations all show "no data"
Capture Request Bodies is off. Turn it on and re-run.
Settings page is empty or won't save
You may not have edit permissions on this property. Check with the workspace owner if so.