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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

MarconLP
Copy link
Member

Changes

  • adds meta ads docs

Checklist

  • Words are spelled using American English
  • Titles are in sentence case
  • Feature names are in sentence case too
  • Use relative URLs for internal links
  • If I moved a page, I added a redirect in vercel.json
  • Remove this template if you're not going to fill it out!

Article checklist

  • I've added (at least) 3-5 internal links to this new article
  • I've added keywords for this page to the rank tracker in Ahrefs
  • I've checked the preview build of the article
  • The date on the article is today's date
  • I've added this to the relevant "Tutorials and guides" docs page (if applicable)

Useful resources

Copy link

vercel bot commented Nov 20, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
posthog ✅ Ready (Inspect) Visit Preview Nov 25, 2024 7:23pm

@MarconLP MarconLP changed the title feat(cdp): add docs for the meta ads destination docs(cdp): add docs for the meta ads destination Nov 20, 2024
Copy link
Contributor

@ivanagas ivanagas left a 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.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
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.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
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.
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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants