> 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.

# Configure an Enrichment processor (Product or Account data)

> Learn how to configure an Enrichment processor to enhance events with product or account data.

Learn how to configure an Enrichment processor to enhance events with product or account data.

You can use this method for enrichment based on standard Zuora metadata such as product catalog, accounts, subscriptions, and charges.

Navigate to **Mediation** > **Meters**

Create a **Custom** meter.

Select and drag the **Enrichment** processor type on to the meter stream page. The enrichment settings page is displayed.

![Enrichment processor settings](/_fern-img/ca5ca8df045ecc7d69d8d124c72eca46cde18464ef730687550244c364541a83.webp)

On the **Enrichment** settings page, enter a name for the processor.

Under **Enrichment Options**, select **Enrich events using Product or Account data**.

Under **Reference Object**, select either **Account** or **Product** as the source for enrichment.

The fields from the selected reference object are used to match and fetch additional data into the event.

Specify the **Field Mapping**.

Field mappings define the join logic, how event records should be matched to reference data.

* **Event Field**: The field from the event stream. Examples: accountNumber, productSKU.
* **Reference Field**: The corresponding field from the reference object to be matched.

This is equivalent to a SQL join ON event.accountNumber = account.accountNumber. You can add multiple field mappings to create composite joins, such as accountNumber and region.

Specify the **Fields To Append**.

Defines which fields from the reference data should be appended to the event.

* **Reference Field**: The Account or Product field that you want to fetch.
* **Event Field Name**: The name of the field in the enriched event.

Append accountType from Account object as enriched_account_type.

You can select `RatePlanCharge.PricingAttributes` as the **Reference Field**. In **Event Field Name**, enter the name of the event field that should contain the appended value. For example, enter `PricingAttributes`.

The appended value can be a JSON object. Use an Advanced Transformer to extract individual pricing attribute values before you configure the Rating processor.

Select an **Output Option** to specify the events that are returned after enrichment.

* **Include all events**: Allows events to pass through even if no match is found in the reference data.
* **Include usage charges only**: Filters results to include only usage charges. This is useful when enrichment is intended solely for usage-based billing scenarios.
* **Use event time to match charge segment**: Ensures a charge segment is selected based on the event’s timestamp, which is important when rate plan charges have multiple time-based segments. If you leave it unchecked, the system uses the latest timestamp while processing these records.

Charge Segment

| Start Date   | End Date     | Price per Unit |
| ------------ | ------------ | -------------- |
| Jan 01, 2024 | Dec 31, 2024 | \$1            |
| Jan 01, 2025 | ongoing      | \$2            |

If the Use event time to match charge segment checkbox is enabled and availableTime is chosen as, say November 2024, the system picks \$1. If the checkbox is disabled, the system picks \$2.

Click **Save**.