-
Notifications
You must be signed in to change notification settings - Fork 489
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
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
02bd409
add docs for the meta ads destination
MarconLP 9a8c30e
add to nav
ivanagas ba7cd54
Update contents/docs/cdp/destinations/meta-ads.md
MarconLP f04a5c8
Update contents/docs/cdp/destinations/meta-ads.md
MarconLP f1f22d0
Merge branch 'master' into meta-ads-docs
ivanagas File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. 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 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. | ||
|
||
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> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.