Clarify lack of LTV based audience support #7550
Merged
Conversation
This file contains hidden or 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
this destination does not support LTV based audiences as of now and the docs are not clear about this. This is creating confusion with some customers. Example of a ticket: https://segment.zendesk.com/agent/tickets/560341
sade-wusi
reviewed
Apr 4, 2025
src/connections/destinations/catalog/personas-facebook-custom-audiences/index.md
Outdated
Show resolved
Hide resolved
sade-wusi
added
the
content-update
…audiences/index.md Co-authored-by: Sharon Adewusi <[email protected]>
sade-wusi
approved these changes
Apr 4, 2025
|
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
this destination does not support LTV based audiences as of now and the docs are not clear about this. This is creating confusion with some customers. Example of a ticket: https://segment.zendesk.com/agent/tickets/560341
Proposed changes
Merge timing
Related issues (optional)