Announcing enhanced access logs with expanded event details and internal operation filter

Announced on | Rollout on
April 8, 2026 | April 8, 2026

Zendesk is enhancing access logs by adding detailed event information, new filtering options, and noise-reduction control to help admins investigate issues faster and more efficiently without losing critical insights.

These improvements are available to all customers with the Advanced Data Privacy and Protection (ADPP) add-on and access logs turned on.

This announcement includes the following topics:

What's changing?

Why is Zendesk making this change?

What do I need to do?

What's changing?

This update is a continuation of Zendesk's audit log enhancements, delivered in direct response to customer feedback.

Updates include:

Access Log Event ID (UI and API): Each record now includes an Access Log Event ID, making it easier to reference and correlate specific events across investigations, exports, and API queries.

Browser URL (UI) / Referer (API): A new Browser URL column is added to the UI table view and is also available as a filter. This value is populated only when access occurs via a browser; otherwise, it is empty. In the Access Logs API, this field is available as Referer.

Accessed API rename (UI and API): Previously labeled Accessed URL, this field has been renamed to Accessed API to clarify that it refers to the API endpoint involved.

HTTP response byte size (UI and API): Access logs now include this metric, providing technical context for troubleshooting, auditing, and incident analysis.

Optional GraphQL (internal operations) log filter (Admin Center UI): Admins can now filter out GraphQL logs in the Admin Center Access Log UI. These records track Zendesk internal component interactions and can add noise during day-to-day review.

Disabling GraphQL logs in the UI filters these events from the Admin Center Access Log view, reducing clutter.

This setting doesn't stop event collection or storage, nor does it affect the API Access Log endpoints.

Category rename (API): The field previously labeled tag has been renamed category for consistency with the naming used in the UI.

These improvements help reduce risk, enhance compliance, and build trust with your users - while saving admins time by making access logs easier to interpret and more efficient to use.

Why is Zendesk making this change?

Zendesk is improving access logs to provide the clarity and ease of use customers need to effectively monitor and secure their systems. These enhancements deliver immediate benefits by enabling faster investigations with richer event details, simplifying compliance with clearer log information, and reducing operational workload through improved filtering and noise reduction.

By making logs easier to understand and to work with, Zendesk allows customers to identify security threats sooner, confidently manage data privacy, and respond to evolving security and regulatory requirements - all from a single, streamlined platform.

What do I need to do?

No action is required. These enhancements will be activated automatically on the rollout date, provided you have the Advanced Data Privacy and Protection add-on and the access logs feature turned on. Once live, you can immediately use the improved categories and filtering options available in both the Access Logs API and the user interface. See Using the access log to monitor agent activity for more information.

If you have feedback or questions related to this announcement, visit our community forum where we collect and manage customer product feedback. For general assistance with your Zendesk products, contact Zendesk Customer Support.