> 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/activate/event-streaming/destinations/advertising.md).

# Advertising

Advertising destinations use your events to measure conversions and to build audiences. Many have a browser version and a server version. Use both where you can.

* [**Amazon Conversions API**](/activate/event-streaming/destinations/advertising/amazon-conversions-api.md): send conversions to Amazon Ads.
* [**AppLovin Axon**](/activate/event-streaming/destinations/advertising/applovin-axon.md): send events to AppLovin for mobile and connected TV ads.
* [**Google Ads**](/activate/event-streaming/destinations/advertising/google-ads.md): track conversions and feed Google Ads campaigns.
* [**Meta**](/activate/event-streaming/destinations/advertising/meta.md): send events to Meta (formerly Facebook) for Facebook and Instagram ads.
* [**Microsoft**](/activate/event-streaming/destinations/advertising/microsoft.md): track conversions for Microsoft Advertising, formerly Bing Ads.
* [**MNTN**](/activate/event-streaming/destinations/advertising/mntn.md): measure connected TV campaigns.
* [**OpenAI Ads**](/activate/event-streaming/destinations/advertising/openai-ads.md): measure conversions for OpenAI ads.
* [**Pinterest**](/activate/event-streaming/destinations/advertising/pinterest.md): track conversions for Pinterest ads.
* [**Reddit**](/activate/event-streaming/destinations/advertising/reddit.md): track conversions for Reddit ads.
* [**Rokt**](/activate/event-streaming/destinations/advertising/rokt.md): send events to Rokt for post-purchase offers.
* [**Snap**](/activate/event-streaming/destinations/advertising/snap.md): track conversions for Snapchat ads.
* [**Spotify Ad Analytics**](/activate/event-streaming/destinations/advertising/spotify-ad-analytics.md): measure Spotify ad campaigns.
* [**StackAdapt**](/activate/event-streaming/destinations/advertising/stackadapt.md): measure programmatic ad campaigns.
* [**The Trade Desk**](/activate/event-streaming/destinations/advertising/the-trade-desk.md): measure campaigns on The Trade Desk.
* [**TikTok**](/activate/event-streaming/destinations/advertising/tiktok.md): track conversions for TikTok ads.
* [**X**](/activate/event-streaming/destinations/advertising/x.md): track conversions for X ads, formerly Twitter Ads.
* [**Yahoo DPA Pixel**](/activate/event-streaming/destinations/advertising/yahoo-dpa-pixel.md): power Yahoo dynamic product ads.


---

# 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/activate/event-streaming/destinations/advertising.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.