> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/connect-sources/data-sources/ads-module.md).

# Ads module

## Ads module

## Overview

Chord's Ads Module unlocks connections for various sources of ad spend data and enables a robust Ads explore, which is a wide dataset populated with enriched data fields.

The Ads explore allows for the creation of custom reports and audiences or customer segments with granularity down to the campaign level. Ad spend data is also joined to Chord's rich marketing attribution data, enabling even more detailed performance analysis.

Sample fields available in Ads explore:

* Ad Name
* Ad Status
* Campaign Advertising Channel Type
* Campaign Name
* Source

The module enables direct connections to the following sources:

* Facebook Ads
* Google Ads
* Pinterest Ads
* TikTok Ads
* Youtube Ads
* Bing Ads (Now Available!)

The module unlocks access to the Advertising Spend model amplification (part of [Model Amplifications](/model-your-data/model-amplifications.md)), which enables brands to add manual or offline ad spend data (e.g. podcasts, newsletters, billboards) for efficient ingestion and transformation alongside their digital ads data for a complete picture of marketing ads spend.

## Use cases

* Brands create reports to track ad spend over time by channel
* Brands create reports to compare total impressions by campaign and channel

Please reach out to <help@chord.co> or your account executive for more information about or access to this feature.


---

# 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.chord.co/connect-sources/data-sources/ads-module.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.