Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(cdp): add docs for the meta ads destination #9930

Merged
merged 5 commits into from
Jan 16, 2025
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
52 changes: 52 additions & 0 deletions contents/docs/cdp/destinations/meta-ads.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,52 @@
---
title: Send PostHog conversion events to Meta Ads
templateId: template-meta-ads
---

import Requirements from "../_snippets/requirements.mdx"
import FeedbackQuestions from "../_snippets/feedback-questions.mdx"
import PostHogMaintained from "../_snippets/posthog-maintained.mdx"

<Requirements />

You'll also need access to the relevant Meta Ads account.

## Installation

1. In PostHog, click the [Data pipeline](https://us.posthog.com/pipeline/overview) tab in the left sidebar.

2. Click the **Destinations** tab.

3. Search for **Meta Ads Conversions** and select the destination.

4. Visit the [Meta Events Manager](https://business.facebook.com/events_manager2/overview).
1. Note: If you’ve already set up a Pixel for your website, we recommend that you use the same Pixel ID for your browser and server events.
1. To create a new Pixel, click **Connect data** and select **Web**.
2. For the connection method, select **Set up manually** and **Conversions API**.
2. Go to your Pixel via **Data sources**.
3. Switch to the **Settings** tab and your Pixel ID will be listed as **Dataset ID**.
4. You can create an access token by clicking **Generate access token**.

5. Back in PostHog, add the Pixel ID and Access token to the destination configuration.

6. Set up your event and property filters to remove unnecessary events. You only want to send events that are conversions. Filter out unrelated events or ones missing required data.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you want to add a bit on what these fields are and what they are useful for? Maybe these fields are step 6 and setting up events and properties are step 7?

CleanShot 2024-11-25 at 11 10 47@2x

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like the description links are pretty good at explaining these values. We will update the default values to match our e-commerce spec at some point, so only power users will have to edit these fields.


7. Press **Create & enable**, test your destination, and then watch your conversions get sent to Meta Ads.

<HideOnCDPIndex>

## Configuration

<TemplateParameters />

## FAQ

### Is the source code for this destination available?

PostHog is open-source and so are all the destination on the platform. The [source code](https://github.com/PostHog/posthog/blob/master/posthog/cdp/templates/meta_ads/template_meta_ads.py) is available on GitHub.

<PostHogMaintained />

<FeedbackQuestions />

</HideOnCDPIndex>
5 changes: 4 additions & 1 deletion src/navs/index.js
Original file line number Diff line number Diff line change
Expand Up @@ -2310,7 +2310,6 @@ export const docsMenu = {
color: 'purple',
},
{

name: 'Web vs product analytics',
url: '/docs/web-analytics/web-vs-product-analytics',
icon: 'IconGraph',
Expand Down Expand Up @@ -2820,6 +2819,10 @@ export const docsMenu = {
name: 'Mailjet',
url: '/docs/cdp/destinations/mailjet',
},
{
name: 'Meta Ads',
url: '/docs/cdp/destinations/meta-ads',
},
{
name: 'RudderStack',
url: '/docs/cdp/destinations/rudderstack',
Expand Down
Loading