After you complete the integration process, you can start creating app push notifications in your journeys by following the steps below:
1. Add app push channel on canvas
Click the + button on the path you want to add the web push channel on your journey.
Click Channel > App Push.
2. Add Message Title and Description
Go to Liquid in Architect to see how to use Liquid Tags in the App Push channel.
Add the message title and description you want to send to your users.
If you want inspiration or need assistance when creating your message content, you can always use the Generate Text option.
To use an AI-generated text:
1. Click the Generate Text button to see the side modal.
2. Enter a prompt you want to generate the text about.
3. The language option will be the default selected language of your panel.
4. Select your industry and use case to define the context for generating the text.
5. Click the Generate Copy button.
If you want to include emojis in your copy, you can check the "Include Emojis" box.
This option indicates that the AI can generate copies with emojis. However, not all options might include emojis.
.png)
The modal displays five suggestions. To see more, you can click the Generate More Suggestions button.
To use any suggestion, you can select it and click the Apply button, or copy it via the Copy button against the suggestion you want to use.
Once you click the Apply button, the copy will be added to the respective field.
You can use default and custom user attributes, event parameters, and coupon codes in the content to personalize it for your users. You can send a new coupon or previously assigned one. Read more on dynamic content.
You can add fallback text for users who do not have a value for the attributes.
Architect excludes dynamic content from the character limit calculation. When you add any dynamic content, it does not have an impact on the character count. When you assign a fallback value to the dynamic content, it will be displayed to the user if the dynamic content's value is empty for that user. In this case, the character count includes the fallback value.
The plus sign in the character count indicates that dynamic content will receive a value upon message delivery to the end user.
SDK does not pass some of the dynamic content attributes. A healthier option is to use dynamic content (default attributes) to be populated from the event parameters. You can contact the Insider team to enable this option.
Also, you can use emojis in your messages to increase the open rates.
3. Configure coupon settings
You can add coupon codes to the content by uploading a coupon list beforehand.
You can also set coupon reminders for your coupon lists. Refer to Coupon Usage Reminder for further details.
.png)
4. Set Rich Message
You can upload a rich push image to your app push notification or use the dynamic image option if you want to offer more visual content. To use the rich push option, click on the Rich Message button. 
The recommended resolution for Image Rich Push is 1024x512px.
GIF Notifications are available for Insider SDK Version 6.1 and higher.
The recommended resolution for the GIF Notifications is 1280x720px.
The supported media types are .jpg, .jpeg, .png, and .gif.
The maximum file size can be 2 MB.
The maximum resolution can be width: 2048 and height: 1080.
You can select URL type attributes or event parameters.
You can add the fallback URL for users who do not have a value for the dynamic URL.
5. Add a deep link
You can add deep links to your app push notifications to redirect users to a specific page or use it for different instructions.
Deep Links are smart URLs that allow you to send existing and potential users to any location within your iOS or Android app. Users survive the app install process, so even new users see the content they're looking for when they open the app for the first time.
Each notification can have deep links to redirect the user to a specific page or use it for different instructions, such as sending open data to analytics tools. Deep Links work as Key&Value Pairs. It’s possible to use multiple pairs as desired.
In addition, dynamic content can be inserted into the Deep Link Value. This means that the Deep Link value will change for all users who have that value, and each user will be sent to, for example, their last visited product.
If a user does not have a value for the dynamic content you set, you can enter an alternative text (fallback) by clicking on the dynamic content tag.
You can use the deep link options below:
Key-Value Pair
URL Scheme
JSON Code
External Browser URL
Internal Browser URL
6. Preview your content
You can preview how your app push looks before you send it out. The preview, placed on the right side of your screen, shows text and image elements.
Dynamic content and Liquid are shown as raw text at this step because no user is selected yet. Use Preview and Test Message to see the content with a user's real values. For details, see Test journey channels.
7. Stock Control
You can add any event parameter from an event with a product_id parameter as dynamic content to perform stock control and confirm whether the product is still in stock immediately before the message is sent.
You can also choose whether the user proceeds to the next element or is dropped from the journey if the product(s) is out of stock.
.png)
8. Enable send time optimization
You can optimize the time it takes to deliver your messages to the end-users. This helps you engage your users more effectively and draw their attention when they are most likely to interact with your messages.
Based on your use cases, you should enable send time optimization. For example, it might not be a good fit for cart or browse abandonment cases.
If you set Channel Frequency Capping before, when you enable Send Time Optimization, Bypass Channel Frequency Capping will be automatically enabled.
Read more on send time optimization.
9. Bypass Channel Frequency Capping
Insider provides app push notifications from the single app push campaigns and Architect. The risk of receiving too many push notifications is increasing, which may lead to unsubscription from your brand. With the App Push Frequency Capping, you can limit the number of app push notifications a user can receive in a specified period like sending a maximum of 5 app pushes to a user in one day.
Architect enables you to bypass the app push channel frequency capping if you have configured any.
Journeys are for real-time cases and they require users to receive notifications based on their actions. Therefore, you may want to override the channel frequency capping you set for your app push.
If a user reaches the limit of the app push notifications they can receive, they will proceed to the next step without receiving another one when they arrive at the app push channel in the journey.
10. Test your app push notification
Click the Preview and Test Message button at the bottom right corner of the page to preview your app push as a user and send it to your test devices. This shows you how the app push appears to users while your journey is live.
Select the test devices you want to send to. A device must be registered on the Test Devices page first. Read more on adding a test device on mobile app.
When you preview as a user and click Send, the app push is delivered exactly as that user would receive it, with dynamic content replaced by real values. If you do not select a user, dynamic content is filled with the test device owner's values, if they exist. For details, see Test journey channels.
11. Rename Channel Name
The Channel Name is generated by default based on the journey name and channel type. If you want to give it a different name, you can rename it at the top right corner..png)
12. Save app push element
After configuring app push settings, you can save the app push page.
Click the Save button, as this page does not have autosaving—autosaving functions only on the canvas page.
Check User Interactions
After the app push element, you can take another action by branching your flow according to user interactions (e.g., viewing app push or opening app push) on the app push notification after a while.
Read Check Interaction for further details.
Users do not take any action on the notification right after you send it. That's why you need to give users some time to take the desired action on the channels by adding a wait element before the check element.