-
Notifications
You must be signed in to change notification settings - Fork 446
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
base: master
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
🤘
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. |
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.
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. |
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. |
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.
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. |
|
||
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. |
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.
Changes
Checklist
vercel.json
Article checklist
Useful resources