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

# Ads Integrations

### Overview

PodPlay supports ad-platform integrations through Segment, letting your Club capture Customer information from your ad campaigns and route it back into PodPlay. This page is the starting point, pick the platform you want to connect, then follow the linked guide.

#### Supported Ad Platforms

* **Meta Ads** — Reach Customers on Facebook and Instagram. See Meta Ads Integration.
* **Google Ads (via Google Tag Manager)** — Reach Customers through Google Search. See Google Tag Manager Integration.

#### How These Integrations Work

Every ad-platform integration follows the same shape:

1. Set up an account on the ad platform (Meta or Google).
2. Locate the integration ID for that platform — a **Pixel ID** for Meta, a **Container ID** for GTM.
3. Send the ID to your PodPlay Customer Success Manager (CSM).
4. The PodPlay team connects that ID to your environment via Segment.
5. The ad platform starts collecting Customer data from your campaigns and feeding events back into PodPlay.

#### What You'll Need

* An active account on the ad platform you're connecting (Meta Business or Google Ads + GTM)
* The relevant ID from that platform (steps in each article)
* Your CSM contact

#### Tracking Notes

* Web App tracking is supported out-of-the-box for both integrations.
* iOS / Android App tracking requires Firebase — reach out to your CSM if mobile attribution matters to you.
* The Website Domain field in any ad platform configuration must be your **Production environment URL**, not a staging or preview URL.

{% hint style="info" %}
PodPlay and PingPod are not affiliated with Meta or Google. These platforms are third-party tools your Club may purchase at its discretion.
{% endhint %}


---

# 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.podplay.app/marketing/ads-integrations.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.