From 02bd4097d290d1b1a969123e7520a3d467a37aad Mon Sep 17 00:00:00 2001 From: MarconLP <13001502+MarconLP@users.noreply.github.com> Date: Wed, 20 Nov 2024 14:17:26 +0100 Subject: [PATCH 1/4] add docs for the meta ads destination --- contents/docs/cdp/destinations/meta-ads.md | 52 ++++++++++++++++++++++ 1 file changed, 52 insertions(+) create mode 100644 contents/docs/cdp/destinations/meta-ads.md diff --git a/contents/docs/cdp/destinations/meta-ads.md b/contents/docs/cdp/destinations/meta-ads.md new file mode 100644 index 000000000000..ff284f7407e1 --- /dev/null +++ b/contents/docs/cdp/destinations/meta-ads.md @@ -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" + + + +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. + +7. Press **Create & enable**, test your destination, and then watch your conversions get sent to Meta Ads. + + + +## Configuration + + + +## 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. + + + + + + From 9a8c30e308e16cb566cba46e3cedb76ebc0c54f2 Mon Sep 17 00:00:00 2001 From: Ian Vanagas <34755028+ivanagas@users.noreply.github.com> Date: Mon, 25 Nov 2024 11:08:51 -0800 Subject: [PATCH 2/4] add to nav --- src/navs/index.js | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/navs/index.js b/src/navs/index.js index 14941ed7a6ac..db9401bad7b9 100644 --- a/src/navs/index.js +++ b/src/navs/index.js @@ -2310,7 +2310,6 @@ export const docsMenu = { color: 'purple', }, { - name: 'Web vs product analytics', url: '/docs/web-analytics/web-vs-product-analytics', icon: 'IconGraph', @@ -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', From ba7cd5492af9d17bdaee2d5f345860515c9dd76e Mon Sep 17 00:00:00 2001 From: Marcus Hof <13001502+MarconLP@users.noreply.github.com> Date: Fri, 13 Dec 2024 12:08:57 +0100 Subject: [PATCH 3/4] Update contents/docs/cdp/destinations/meta-ads.md Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com> --- contents/docs/cdp/destinations/meta-ads.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contents/docs/cdp/destinations/meta-ads.md b/contents/docs/cdp/destinations/meta-ads.md index ff284f7407e1..ce3f41007aed 100644 --- a/contents/docs/cdp/destinations/meta-ads.md +++ b/contents/docs/cdp/destinations/meta-ads.md @@ -20,7 +20,7 @@ You'll also need access to the relevant Meta Ads account. 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. 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**. From f04a5c814b81b1c9149ccab3d22067a1cd0e54d5 Mon Sep 17 00:00:00 2001 From: Marcus Hof <13001502+MarconLP@users.noreply.github.com> Date: Fri, 13 Dec 2024 12:09:05 +0100 Subject: [PATCH 4/4] Update contents/docs/cdp/destinations/meta-ads.md Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com> --- contents/docs/cdp/destinations/meta-ads.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contents/docs/cdp/destinations/meta-ads.md b/contents/docs/cdp/destinations/meta-ads.md index ce3f41007aed..d39c79bde16c 100644 --- a/contents/docs/cdp/destinations/meta-ads.md +++ b/contents/docs/cdp/destinations/meta-ads.md @@ -27,7 +27,7 @@ You'll also need access to the relevant Meta Ads account. 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. +5. Back in PostHog, add the access token and Pixel ID 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.