> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/how-to/verify-event-transforms.md).

# Verify Event Transforms

### What are keyword conversions?

Keyword conversions is a feature where you can **map keywords** to custom conversions. In a Purchase event, if we see any mapped keyword present in the fields of the event payload (see below) after we transform them, we fire the mapped custom conversion. E.g. if keyword "shirt" is present in `contents.title`, we fire the mapped custom conversion of that keyword.

### Transform payload fields

When looking for keywords, we are considering the following fields in the payload:

* `contents.title`
* `contents.brand`
* `contents.description`
* `keywords`

When transforming, we will remove punctuations, replace word split characters with spaces, changes text to lower case etc.&#x20;

**Examples**&#x20;

"White\_shirt" would be "whiteshirt"&#x20;

"Red\_Cap.Embroidered" would be "redcap embroidered"

### How to create a keyword conversion mapping?

Once you know the keyword that can be used, please go to the plugins page, select the plugin that you want to add keyword conversion mapping, add keyword in the left dropdown and the custom conversion name in the right dropdown and save the form.

<figure><img src="https://1474399258-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZJWZKbUk0hRISkCIj2p4%2Fuploads%2FfWB8TscjE2A7RrBtK4U1%2FScreenshot%202026-02-02%20at%209.12.09%E2%80%AFPM.png?alt=media&amp;token=d1a25b63-3eb6-400e-b146-f472b7a1929a" alt=""><figcaption></figcaption></figure>

For understanding how you can use this feature as a marketer, Please refer to our guide here.

{% embed url="<https://docs.edgetag.io/onboarding/e-commerce/scaling-playbook/product-category-and-margin-optimization#three-ways-to-transform-events>" %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.edgetag.io/how-to/verify-event-transforms.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
