> For the complete documentation index, see [llms.txt](https://help.daasity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.daasity.com/core-concepts/data-integrations/setup-guides/digital-integrations/amazon-advertising/where-to-find-your-data.md).

# Where to Find Your Data

## In Your Data Warehouse

If you are an Enterprise merchant, you can analyze your Amazon Ads data directly in your data warehouse.

### Raw Data

You can analyze your raw, extracted data using the tables in your [Amazon Ads Schema](/core-concepts/data-integrations/setup-guides/digital-integrations/amazon-advertising/integration-specifications.md#amazon-a-ds-schema).

### Transformed Data

You can also view your Amazon Ads data in more analysis-friendly tables if you set up the proper transformation code and wait for the next workflow to run. 

If you have set up [Amazon Ads transformation configuration](/core-concepts/data-integrations/setup-guides/digital-integrations/amazon-advertising/transformation-configuration-setup.md), then your Amazon Ads data will be transformed into the following tables:

* `ums.amazon_ads_sponsored_products_spend`
* `ums.amazon_ads_sponsored_product_display_spend`
* `ums.amazon_ads_sponsored_brands_spend`
* [`ums.vendor_performance`](/core-concepts/data-models/unified-schemas/unified-marketing-schema-ums.md#vendor-performance)

If you have configured your Marketing Data Mart Code, you will also find Amazon Ads data in the following table:

* `dm_mkt.fct_vendor_level_performance`

## In Looker

If you are using Daasity's Looker template, you can analyze your transformed Amazon Ads data alongside other marketing sources in the following explores & dashboards:

### Explores

* Marketing Attribution
* Vendor-Reported Marketing Performance

### Dashboards

* Marketing


---

# 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.daasity.com/core-concepts/data-integrations/setup-guides/digital-integrations/amazon-advertising/where-to-find-your-data.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.