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

# Snapchat

Follow our setup guide to connect Snapchat to QUANTI:

<a href="https://dbdiagram.io/e/68c0383661a46d388e362747/68c03a9361a46d388e36b65a" class="button primary" data-icon="table-tree">Prebuilt reports and definition</a>

***

## <mark style="background-color:blue;">Prerequisites</mark>

To connect Snapchat to Quanti:, you need to access a [Business account](https://accounts.snapchat.com/v2/login).

***

## <mark style="background-color:blue;">Setup instructions</mark>

1. Connect your Snapchat account to permit Quanti: to access to your data
2. Connector information
   1. Connector Name : Name your connector. It must be unique.
   2. Dataset ID : Define the ID of the dataset. It must not exist yet, as it will be created and data will be sent there.
3. Select accounts : Choose accounts to sync.
4. Select queries : Choose the pre-built queries you’d like to synchronize—or skip this step if none apply.
5. Create queries: create your own custom queries queries you’d like to synchronize—or skip this step if none apply.

***

## <mark style="background-color:blue;">Prebuilt reports</mark>

* **ad\_account\_history**: Stores historical data about ad accounts and their configurations.
* **ad\_daily\_report**: Daily performance metrics at the ad level.
* **ad\_demographic\_daily\_report**: Ad performance metrics broken down by demographic segments.
* **ad\_device\_make\_daily\_report**: Ad metrics segmented by device make (e.g. Apple, Samsung).
* **ad\_device\_os\_daily\_report**: Ad metrics segmented by operating system (e.g. iOS, Android).
* **ad\_geo\_country\_daily\_report**: Ad metrics grouped by country.
* **ad\_geo\_dma\_daily\_report**: Ad metrics grouped by DMA (Designated Market Areas).
* **ad\_geo\_region\_daily\_report**: Ad metrics grouped by geographic regions.
* **ad\_history**: Contains historical records of individual ads and their statuses.
* **ad\_squad\_daily\_report**: Daily performance data aggregated at the ad squad level.
* **ad\_squad\_demographic\_daily\_report**: Ad squad performance data by demographic attributes.
* **ad\_squad\_device\_make\_daily\_report**: Ad squad metrics by device make.
* **ad\_squad\_device\_os\_daily\_report**: Ad squad metrics by operating system.
* **ad\_squad\_geo\_country\_daily\_report**: Ad squad performance by country.
* **ad\_squad\_geo\_dma\_daily\_report**: Ad squad performance by DMA region.
* **ad\_squad\_geo\_region\_daily\_report**: Ad squad performance by broader geographic regions.
* **ad\_squad\_history**: Historical configuration and status data for ad squads.
* **campaign\_daily\_report**: Daily performance metrics at the campaign level.
* **campaign\_demographic\_daily\_report**: Campaign metrics by age and gender.
* **campaign\_device\_make\_daily\_report**: Campaign metrics segmented by device make.
* **campaign\_device\_os\_daily\_report**: Campaign metrics segmented by OS.
* **campaign\_geo\_country\_daily\_report**: Campaign metrics by country.
* **campaign\_geo\_dma\_daily\_report**: Campaign metrics by DMA region.
* **campaign\_geo\_region\_daily\_report**: Campaign metrics by larger regions.
* **campaign\_history**: Historical data of campaign configurations and statuses.
* **organization\_history**: Historical data about advertiser organizations.

***

<a href="https://dbdiagram.io/e/68c0383661a46d388e362747/68c03a9361a46d388e36b65a" class="button primary" data-icon="table-tree">Prebuilt reports and definition</a>


---

# 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.quanti.io/connectors/marketing-connectors/snapchat.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.