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

[Content]: Add Information for FB Conversions API Destination #7247

Open
courtneyga opened this issue Nov 21, 2024 · 2 comments
Open

[Content]: Add Information for FB Conversions API Destination #7247

courtneyga opened this issue Nov 21, 2024 · 2 comments
Assignees
Labels
content When the bug is about content that needs to get fixed triaged

Comments

@courtneyga
Copy link
Contributor

What article on segment.com/docs is affected?

https://segment.com/docs/connections/destinations/catalog/actions-facebook-conversions-api/#custom-event

What part(s) of the article would you like to see updated?

Add Colorado and Connecticut to this section under, "Custom Event"
image-20240126-200304

Additional information

No response

@courtneyga courtneyga added content When the bug is about content that needs to get fixed triage KCS labels Nov 21, 2024
@forstisabella forstisabella self-assigned this Nov 21, 2024
@forstisabella
Copy link
Contributor

Hi @courtneyga - the docs team can't override these values, as they're pulled directly from the Public API. I can open a pull request in the action-destinations repo, but I need additional context on this:

It looks like Facebook's documentation includes a longer list than California/Colorado/Connecticut - for the Data Processing State. Should we add all of the items that are currently supported to the Data Processing State description?

@courtneyga
Copy link
Contributor Author

courtneyga commented Nov 21, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content When the bug is about content that needs to get fixed triaged
Projects
None yet
Development

No branches or pull requests

2 participants