> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/contracts/modify-contract-field-names-and-descriptions.md).
# Modify Contract Field Names & Descriptions
Customize and remap event type parameters in your template terms to make item-level data more descriptive for partners. For example, you can rename a generic parameter like `text3` to "Festive Conversions" so partners immediately understand what the data represents.
## Before you begin
{% hint style="danger" %}
**The schema you configure replaces the default schema entirely—only the attributes you explicitly define will be available.**
When you add your first custom attribute to an event type, the default schema is replaced by your configured one. Any attribute you don't explicitly add is left out, including `Text`, `Numeric`, `Money`, `Order`, `Item`, and `Customer` fields. If your payout group or payout modifier rules reference those missing attributes, they will stop matching.
Only `Derived`, `Path`, and `Referral` fields will be available regardless of your schema configuration.
{% endhint %}
1. Audit all [payout group](/brand/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/payout-adjustments/set-payout-rules-using-payout-groups.md) and [payout restriction](/brand/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/payout-adjustments/add-payout-restrictions-to-template-terms.md) rules that reference this event type.
2. List every field on which those rules depend.
3. Plan to manually re-add those fields as custom attributes in the new schema.
## Access event type mapping
1. From the top navigation bar, select  **\[User profile] → Settings**.
2. On the right, under *Tracking*, select [**Event Types**](https://app.impact.com/secure/advertiser/tracking-settings/actiontracker/view-actiontracker-flow.ihtml).
3. Hover over the applicable event type and select  **\[More]** → **Schema**.
* Here, you will see the details related to each event-type schema. Refer to the reference table below.
Event type schema reference table
| Schema item | Description |
| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Attribute | The actual event type parameter passed through to impact.com with each conversion. E.g., CustomerId or CustomerRegion. |
| Display Name | The name of the event type parameter. You can customize the parameter's name. |
| Description | The description of the event-type parameter. |
| Privacy level | Controls whether this field's value is included in Event Notification Postbacks sent to partners.
- Share with all partners: included in all partner postback payloads.
- Share with no partners: excluded from all postback payloads.
- Share with some partners: included only in postback payloads for selected partners. This does not affect brand-side reporting or stored data.
Example: Text10 stores Caller ID. By setting the privacy mode to Hide, the Caller ID data point will be excluded from the postback notification sent to a partner, even if the field is populated in the system.
|
## Edit an event type parameter
1. From the top navigation bar, select  **\[User profile] → Settings**.
2. On the right, under *Tracking*, select [**Event Types**](https://app.impact.com/secure/advertiser/tracking-settings/actiontracker/view-actiontracker-flow.ihtml).
3. Hover over the applicable event type and select  **\[More]** → **Schema**.
4. Hover over the parameter you want to edit and select  **\[More]** → **Edit**.
5. Make your changes and select **Save**.
## Add an event type parameter
1. From the top navigation bar, select  **\[User profile] → Settings**.
2. On the right, under *Tracking*, select [**Event Types**](https://app.impact.com/secure/advertiser/tracking-settings/actiontracker/view-actiontracker-flow.ihtml).
3. Hover over the applicable event type and select  **\[More]** → **Schema**.
4. On the *Event Type Schema* screen, in the upper-right corner, select **Add**.
5. Complete the mapping information.
6. Select **Save**.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/contracts/modify-contract-field-names-and-descriptions.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.