> 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/meta-ads.md).

# Meta Ads

### Overview

This article shows you how to connect your Meta (Facebook and Instagram) advertising account to PodPlay, so Customer data captured by your Meta campaigns flows into your PodPlay environment via Segment.

<details open>

<summary>What is Meta?</summary>

Meta is a social media platform that connects billions of people across Facebook and Instagram. Meta lets your Club run ads to potential Customers on those platforms and draw them into the Club through your PodPlay app.

</details>

#### Prerequisites

* A Meta Business account with an active Pixel
* Your PodPlay Customer Success Manager (CSM) contact

#### Steps

**1. Locate Your Meta Pixel ID**

Sign in to Meta and open the [Meta Pixel page in Events Manager](https://www.facebook.com/ads/manager/pixel/facebook_pixel/). Your Pixel ID is the numeric identifier shown on this page.

**2. Send the Pixel ID to Your CSM**

Email or message your PodPlay CSM with the Pixel ID. Include your Club name so they can match it to the correct environment.

**3. PodPlay Connects the Pixel via Segment**

The PodPlay team adds your Pixel ID to your environment through Segment. No further setup is required on your side — once connected, your Meta ads will begin collecting Customer data and sending it back into PodPlay.

#### Verify It Worked

1. Run a small test campaign, or send test traffic to your PodPlay app.
2. In Meta Events Manager, confirm events are arriving against your Pixel.
3. Confirm with your CSM that PodPlay is receiving the corresponding Segment events.

#### Common Issues

* **No events showing in Meta:** Confirm the Pixel ID you sent matches the one in Events Manager. A copy-paste error is the most common cause.
* **Events arrive in Meta but not in PodPlay:** Reach out to your CSM — Segment routing may need to be re-checked.
* **Wrong environment receiving traffic:** Confirm the Website Domain on your Meta campaign points to your Production URL.

#### Mobile App Tracking

Google Ads typically pushes new Customers to the PodPlay Web App. To track installs and conversions in the iOS or Android app, your Club will need to partner with a 3rd party for [attribution](https://docs.podplay.app/marketing/ads-integrations/attribution-with-ads-data).

{% hint style="info" %}
PodPlay and PingPod are not affiliated with Meta. The Club may purchase Meta advertising 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 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://docs.podplay.app/marketing/ads-integrations/meta-ads.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.