> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/astera-data-stack-v10/dataflows/transformations/ai-match-transformation.md).

# AI Match Transformation

Astera Data Stack introduces an innovative AI Matching feature which leverages the power of Artificial Intelligence to perform intelligent matching. This feature works based on semantic similarity, ensuring more accurate and comprehensive matching results.

### AI Match in Astera Data Stack

In Astera Data Stack, the *AI Match* object can be found in the Toolbox and can be used within the scope of the Dataflow.

![](/files/Li6dhwOOJU0ZmoncEGNv)

### Use Case

For our use case, we have a Customers dataset from the sales department as shown below:

<figure><img src="/files/wfq9dFfEDBVrID9bGoYf" alt=""><figcaption><p>Sales Dataset</p></figcaption></figure>

We want to replace the values in the Country column of the sales dataset by semantically matching them with Country values from the Customers dataset provided by the marketing team, ensuring both departments follow a unified naming standard.

<figure><img src="/files/dLjZ4v3eT03NrysRBqEE" alt=""><figcaption><p>Marketing Dataset</p></figcaption></figure>

1. To get started, let’s drag-and-drop an *Excel Workbook Source* object and configure it with the customers dataset provided by the sales department.

![](/files/7fhxv9ecORi53rebtBIv)

2. Next, drag-and-drop the *AI Match* object from the Toolbox onto the Dataflow and auto-map the fields from the *Excel Workbook Source* onto the *AI Match* object.

![](/files/sAybeIJNM75RAEzWRTbv)

3. Once all the fields have been mapped, right-click on the *AI Match* object and select *Properties* from the context menu.

![](/files/qTTveru0mSM4SOuSqpv5)

4. This will open the Layout Builder screen, which shows the layout of the incoming dataset. Click *Next.*

![](/files/UcQJOcOHcALmlVWRn21c)

5. The *AIMatch Transformation Properties* screen will open, let’s configure these properties.

![](/files/NAOyj1L68h1DF67FSSWr)

* *File Path:* This is where we provide the path of the file on the basis of which we want to perform our semantic matching.
* *Worksheet:* This is where we can define which Excel sheet data to use if there are multiple sheets.
* *Lookup Field:* This is the field based on which we are performing the lookup.
* *Incoming Field:* This lets us define the lookup field from the incoming dataset

For our use case, let’s select the *Country* Field for both.

![](/files/ZvPKWgpsRbnZpFJiEus4)

6. Once done, click *OK* and right-click on the *AI Match* object to preview its output.

As you can see below, the values in the *Country* field have been semantically matched and replaced from the file, using AI. We can also see that, since the country Pakistan did not have a matching field in the marketing dataset, it hasn’t been replaced.

![](/files/fRsNs5Rp9E80OyCtnOUb)

7. Now, let’s drag-and-drop a *Database Table Destination* object and map the matched data onto it.

![](/files/OhqIx0qMx2EYimcsvhRV)

Running this Dataflow will write the data to the destination table.

This concludes the working of the *AI Match* object in Astera Data Stack.


---

# 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://documentation.astera.com/astera-data-stack-v10/dataflows/transformations/ai-match-transformation.md?ask=<question>&goal=<endgoal>
```

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