Deploy - June 18, 2024 #7548
Merged
Deploy - June 18, 2024 #7548
Conversation
This file contains 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
Contributor
internetisaiah
commented
Jun 18, 2024
internetisaiah
commented
- #7518 - WhatsApp supports more than one subscription group per workspace
- #7520 - Add translation note to AI copywriting assistant and exclusio…
- #7524 - Updated /campaigns/trigger/send docs to include newly supported attachments feature
- #7523 - Help article for tracking push unsubscribes
- #7525 - Minor Liquid highlight edits
- #7526 - Update triggered_delivery.md
- #7522 - [DLK-1793] Updating troubleshooting tips for test connection
- #7532 - Update header for consistency
- #7533 - Canvas target audience clarifications
- #7534 - Add alert for subscription status
- #7535 - Add detail on deleting Canvas step and Engagement Reports
- #7513 - Brand refresh tweaks
- #7540 - Update offerfit.md
- #7541 - Remove extraneous line
- #7542 - Update user_update.md
- #7543 - Update mparticle_for_currents.md
- #7544 - Add Segments troubleshooting article
- #7537 - Update sdk_primer.md
- #7539 - Update personalized_paths.md
- #7529 - Update revenue_report.md
- #7545 - Update email settings warning
- #7528 - Update purchase_events.md
- #7515 - Track user sync beta - MERGE 6/18
- #7527 - Update reeligibility.md
- #7547 - Update images.md
- #7546 - Request page changes
BD-3176 WhatsApp supports more than one subscription group per workspace
BD-3175 Add translation note to AI copywriting assistant and exclusio…
…hments feature /campaigns/trigger/send support attachments in the same way as /messages/send for emails. The support was rolled out today, we are ready to update public docs.
Updated /campaigns/trigger/send docs to include newly supported attachments feature
BD-2968: Help article for tracking push unsubscribes
We believe 1 core scenario has been missed here. The new line we think definitely needs to be included (please correct me if I'm wrong). I have included a redirect to the abort message docs, please make sure I have coded that correctly.
We feel the explanation for re-eligibility here is very very confusing based on a few recent support cases from our customers. We've had 4 CSMs also read through the docs for a good 30mins and we were confused so we're hoping you can help us tweak the wording to be much more descriptive in is re-eligibility tied to campaign ENTRY vs campaign message RECEIPT.
We are very worried about the calculation here:
$$\text{Lifetime revenue} = \frac{\text{Total spend in dollars}}{\text{Total number of purchase events}}$$
For us, this should be Lifetime Revenue PER USER as the 2nd bullet point below this calculation is directly relating to this calculation and nothing else.
I've had 3 Snr CSMs reviewing this for an hour to try and understand this and we've just realised the above needs to be resolved.
We think there is a huge flaw in our docs here where we don't explain at all the calculations for the top 3 graphs on the Revenue Report page. We've had 3 x Snr CSMs spend 1hr scouring the docs and trying to figure out where on earth all these metrics are coming from and if they are unique and de-duplicated outside of the campaigns and Canvases. We think the docs has to be updated to have this information we've inserted as it's now crystal clear (happy for you to fix our proposal copy up) what each of those metrics is.
…s/delivery_types/triggered_delivery.md
Co-authored-by: Bre Fitzgerald <82903296+bre-fitzgerald@users.noreply.github.com>
Update personalized_paths.md
Update revenue_report.md
BD-3183 Update email settings warning
Update purchase_events.md
BD-3167: Track user sync beta - MERGE 6/18
…s/delivery_types/reeligibility.md
Update reeligibility.md
Update images.md
Request page changes
internetisaiah
requested review from
rachel-feinberg
and removed request for
rachel-feinberg
josh-mccrowell-braze
approved these changes
Jun 18, 2024
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.