Repository navigation
Docs: pages for the contact, unsubscribe, complaint and suppression.deleted webhook events - #45
Merged
Merged
Conversation
…eleted webhook events The October release added eleven webhook events, the origin of contact and suppression events and the origins filter, but the docs listed only the ten older events. Each new event gets a page, the event reference gets their rows and sections on contact events, origin and the loop warning, event order, and the changes that send no event, and the webhook API pages carry the scope and marketing rules. suppression.created said that several hard bounces make a suppression; one does. It now also names the origin and the API and transactional unsubscribe causes, and says a repeat sends nothing. The template send pages pointed to Get Template for a send's variables, which answers the draft while one exists; they now point to Get Published Template. The August changelog claimed campaign click webhooks were fixed then; they were only delivered from this release, which the October entries cover.
…bounce does not The suppression.created page and the spec copy named repeated soft bounces as a cause; one message that keeps failing until it expires is enough. Both now also say when a bounce leaves the address unsuppressed. The server spec gets the same lines.
A policy rejection, such as a blocklist or spam-filter bounce, creates no suppression, so the exceptions on the suppression.created page and the spec copy name it. The expired-message cause says it takes several delivery attempts. The server spec gets the same lines.
The spec copy and the webhook guide gave "Too many hard bounces" as a suppression reason, which AhaSend never sends. They now use "Invalid Recipient". The server spec gets the same lines.
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
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.
originand the origins filter (with the loop warning), event order, and changes that send no event.suppression.created: one hard bounce is enough to suppress (also fixed in thewebhooks.yamlcopy); the page now namesorigin, the API and transactional unsubscribe causes, and that a repeat sends nothing.