> This page is for Docs.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://zuora.ferndocs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://zuora.ferndocs.com/_mcp/server.

# AI Source and AI SubSource in the Audit Trail

> Use the AI Source and AI SubSource fields in Audit Trail logs to determine whether a change was initiated through AI and trace it to the originating interaction.

Use the AI Source and AI SubSource fields in Audit Trail logs to determine whether a change was initiated through AI and trace it to the originating interaction.

Use the AI Source and AI SubSource fields to determine whether a change was initiated through AI and trace the change to the originating AI interaction.

## AI Source

The AI Source field identifies the channel that initiated the change. The field can contain the following values:

* Empty: The change was not initiated through AI.
* Zuora AI: The change was made from the in-product Zuora AI experience.

## AI SubSource

The AI SubSource field provides more specific information about the origin indicated by AI Source:

* For changes with an AI Source value of Zuora AI, AI SubSource contains the Zuora AI chat or session ID.
* For changes with no AI Source, AI SubSource is empty.

## Where AI Source and AI SubSource appear

The AI Source and AI SubSource fields appear as columns in the following Audit Trail logs:

* Object Change Log
* Setting Change Log

Where supported, you can filter or search on these fields and include them in CSV exports.

## Trace AI-initiated changes

Use these fields to distinguish AI-initiated changes from non-AI changes and to identify the channel that initiated each change.

For changes made through Zuora AI, use the AI SubSource chat or session ID to locate the originating conversation.