Clarification for Devs Inexperienced with Push

[SimeonBraze]

Pull Request/Issue Resolution

Description of Change:

Often when dealing with devs that are inexperienced with push notifications I find that they follow some guide they find online and request push permissions in the startup code. We often need to tell them not to do this. This is more of a problem when the Braze SDK will be handling this for them now.

Closes #ISSUE_NUMBER_HERE

Is this change associated with a Braze feature/product release?

• Yes (Insert Feature Release Date Here)
• [ X] No

---

✔️ Pull Request Checklist

• [X ] Check that all links work.
• [ X] Ensure you have completed our Contributors License Agreement.
• Tag @timothy-kim and @KellieHawks as a reviewer when your work is done and ready to be reviewed for merge. Are you an internal product manager? Reference the interal reviewing chart to tag the appropriate reviewer.
• Tag others as reviewers as necessary.
• [X ] If you have modified any links, be sure to add redirects to assets > js > broken_redirect_list.js

⭐ Helpful Wiki Shortcuts

• Writing Style Guide
• Image Style Guide
• Styling Test Page

❗ ATTN: For PR Reviewers

• Read our Reviewing a PR page for more on our reviewing suggestions.
• Read our Previewing Documentation page to see how to check the deployment.
  • Preview all changes in the linked Vercel environment by clicking the preview link in the vercel-bot comment in your PR.

❗ ATTN: Internal Reviewing Chart

Work at Braze and not sure who to tag for review?
Before tagging @timothy-kim or @KellieHawks for a general review, reference the following chart to see if a specific product vertical/reviewer applies to your pull request.

Reviewer	Product Vertical
@timothy-kim	Data Infrastructure Platform Infrastructure Quality Infrastructure
@KellieHawks	Internal Tools Product Partnerships SDKs SMS
@bre-fitzgerald	Channels FIX Intelligence Reporting SMB
@lydia-xie	Email (Composition and Infrastructure) Ingestion Messaging

[vercel]

@SimeonBraze is attempting to deploy a commit to the Braze Team on Vercel.

A member of the Team first needs to authorize it.

[bre-fitzgerald]

Hey @SimeonBraze, thanks for contributing to our docs! I'm unsure if putting this information in the push primer documentation makes sense. This seems like it might be better suited to push integration docs. @davidbielik can you take a look at this?

cc: @KellieHawks

[SimeonBraze]

Hey @bre-fitzgerald, I am not sure it works there either as those docs make reference to the old way of push priming without the the built in IAM functionality. It might be push priming in the development sections also needs rework/removal once the iOS 5.1.0 SDK is live.

I actually forgot to include it in this pull request but a couple extra things I think we need to include in this page. I can park these for another pull request if you want.

• The recommended filter is “Push Subscription Status is not Opted In”, however as we may know, push enabled status is at a device level, not user level. This solution doesn’t cater for the scenario where 1 user might have multiple iOS devices and multiple Android devices.
• It mentioned tracking conversions, but Braze doesn’t provide an out-of-the-box drop-down to track push-enabled events.

[SimeonBraze]

One more thing sorry. We have found that markers attempt to use this functionality and wonder why it isn't working when either the SDK isn't supported or the development team haven't properly implemented it. I think we should do more to tell potential users they may need to do more validation before attempting to use this feature.

[davidbielik]

or

Suggested change

	When implementing push notifications for the first time it is common to include the below, or simillar, in app startup code. For this push priming process to work as expected, it is important you do not implement any push registration code. The implementation is handled by the Braze SDK.
	You should remove any code that manually requests the push permission prompt to be shown to avoid showing the native prompt too early. This new Braze in-app message feature will automatically handle push permission prompts when the user clicks the button.

[davidbielik]

• The recommended filter is “Push Subscription Status is not Opted In”, however as we may know, push enabled status is at a device level, not user level. This solution doesn’t cater for the scenario where 1 user might have multiple iOS devices and multiple Android devices.

We have a "Push Enabled for App" filter. isn't that a better one to use?

• It mentioned tracking conversions, but Braze doesn’t provide an out-of-the-box drop-down to track push-enabled events.

The IAM can still track button1/button2 clicks, though not the same as tracking opt-in rates.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
braze-docs-en	✅ Ready (Inspect)	Visit Preview	Aug 24, 2022 at 5:28PM (UTC)

1 Ignored Deployment

Name	Status	Preview	Updated
braze-docs-fr	⬜️ Ignored (Inspect)		Aug 24, 2022 at 5:28PM (UTC)

[SimeonBraze]

Thanks for the changes, yours is much better.

We have a "Push Enabled for App" filter. isn't that a better one to use?
This is still at a user level not a device level. For example, a user has iPhone 12 and is push subscribed on that phone. They then buy an iPhone 13 and install the app. Because the iPhone 12 is still push subscribed in Braze they won't receive an IAM prompt because those filters are at a user level not a device level.

The IAM can still track button1/button2 clicks, though not the same as tracking opt-in rates.
Yes i think the idea is we have no idea whether the user actually opted into push on that device after pushing button 1.