Release 23.35.1 #5265
Merged
Release 23.35.1 #5265
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
### Email and User Token both fields are mapped in "Send custom behavioural event" mapping and sent over the event paylaod too. But the event is failing for delivery with "Payload validation error" as the email is not in valid format, why it is not taking the User token for validation? Event payload should have the email with valid format or empty string, so that the user token will take precedence and can be validated. An invalid email will not pass mapping validation. Hence the event delivery is failing.
Hubspot Cloud Actions Destination supports Custom Behavioral Events and not Behavioral Events (Legacy). This warning box directs users to the Hubspot Classic Destination for Behavioral Events (Legacy).
Added a resolution to mitigate the error.
…e.md Co-authored-by: Niall Brennan <nbrennan@twilio.com>
…e.md Co-authored-by: Niall Brennan <nbrennan@twilio.com>
…e.md Co-authored-by: Niall Brennan <nbrennan@twilio.com>
…e.md Co-authored-by: Niall Brennan <nbrennan@twilio.com>
Added the following faq that insert function can only be connected to one destination only. "Can I connect an insert function to multiple destinations? No, a destination insert function currently can be connected to one destinations only."
After reviewed in https://segment.atlassian.net/browse/KCS-555, change statement to the following: "No, a Destination Insert Function currently can be connected to one destination only."
…Destination Filter Customer are confused that sometimes they are still seeing events flowing through after adding Destination Filter. Added the following faq to indicate that retries could account for these events not filtered by Destination Filter "Why do I see events being sent through after I just added a destination filter? If Event Delivery page shows events have been retried, the retries could account for events that did not get filtered when the Destination Filter is just added. Such scenario can occur when an event was sent to the destination and encountered timeout error, and retries for the events are attempted. While the retries are attempted, and a Destination Filter is then added, these retries will not subject to the filtering since these are from the events sent before the Destination Filter is added."
Add mailchimp marketing dependency
Add faq that insert function can only be connected to one destination
- Move the word "to" from: You can load a buffered version of analytics.js that requires you call load explicitly > to < before analytics.js initiates any network activity. You can load a buffered version of analytics.js that requires you > to < call load explicitly before analytics.js initiates any network activity.
Add faq that retries could account for events not filtered by Destination Filter
Fix sentence in Analytics.js doc
Warning about Behavior Events (Legacy)
*updated* RETRY Mixpanel legacy common error
User Token is not taken for validation as Email is not in valid format.
…ing-cloud/index.md
WebEngage Connection Mode override
Add tips regrading GTM 404 error
…destination-plugins/branch-react-native.md
feat: add branch metrics to react native dest. plugin catalog
Update doc: iOS does not support destination middleware
Add link to plugin Architecture docs
Information about the available actions of SFMC destination.
Catalog - 8.29.23
stayseesong
approved these changes
Aug 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.