Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove push primer prerequisites #5285

Merged
merged 1 commit into from
Apr 24, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,6 @@ If a user hasn't updated their application (that is, they're on an older SDK ver
**Additional prerequisites**<br>
- For the web SDK, the initialization option [`allowUserSuppliedJavascript`](https://js.appboycdn.com/web-sdk/latest/doc/modules/braze.html#initializationoptions) must be set to `true`. The `enableHtmlInAppMessages` option will also allow these messages to function, but is deprecated and should be updated to `allowUserSuppliedJavascript`.
- If you are using Google Tag Manager, you must enable "Allow HTML In-App Messages" in the GTM configuration.
- Users will need to be on newer SDK versions to use “Request Push Permission” as an [on-click behavior option]({{site.baseurl}}/user_guide/message_building_by_channel/push/best_practices/push_primer_messages#button-actions) for buttons.

## Step 1: Create an in-app message

Expand Down Expand Up @@ -201,7 +200,7 @@ Yes, you can segment based on button clicks for up to two buttons in your messag

No.

#### Can I save my in-app message as a template after I build it within my campaign or Canvas?**
#### Can I save my in-app message as a template after I build it within my campaign or Canvas?

No, you have to recreate the in-app message in the Drag & Drop Editor or duplicate an existing message in order to save.

Expand Down