--- title: "Architect Use Case: Install" slug: "architect-install" description: "You can get to know who installed your app and trigger journeys to engage your users more with your brand." tags: ["architect use case", "install journey"] updated: 2026-01-22T13:14:51Z published: 2026-01-22T13:14:51Z canonical: "academy.insiderone.com/architect-install" --- > ## Documentation Index > Fetch the complete documentation index at: https://academy.insiderone.com/llms.txt > Use this file to discover all available pages before exploring further. # Architect Use Case: Install Each user who installs and uses your app is important and valuable. Brands create marketing strategies to acquire users not to lose them in a short time. You can get to know who installed your app and trigger journeys to engage your users more with your brand. Apart from running app push notifications or in-apps to thank your users for installing your app, you can target them over email or any other channel as well. Users give you a display of interest by installing your app. This valuable moment is your opportunity to introduce your brand, offer the most popular products, provide how-to guides to deliver a smoother experience for your users. You can build your brand loyalty by making an excellent first impression on users. This guide explains the following: - [Goals](/docs/architect-install#goals) - [Requirements](/docs/architect-install#requirements) - [Create an install journey](/docs/architect-install#create-an-install-journey) - [Advanced install journeys](/docs/architect-install#advanced-install-journeys) ## Goals While engaging your users who install your app with install journeys helps you increase user retention, each targeted and converted user will help you: - Activate users, - Increase customer loyalty, - Increase retention, - Drive first purchase, - Educate and onboard users. ## Requirements - You must have the [SDK](https://academy.useinsider.com/docs/developer-guide-mobile-sdks) integration completed. - Before starting to use any channel in your journeys, integrations for the respective channels should be completed. Depending on the channels you want to use in your journeys, additional integrations might be required. - To reach out to users across platforms, the respective user data should be unified before starting to use this use case. - If you want to engage users on the website as well for the install app case, you need to complete [Insider Tag](/docs/integration-guides-web-insider-tag-integration) and [Web SDK](https://academy.insiderone.com/docs/insider-web-sdk-integration-guide) integrations. - In case you need to have some custom events, you need to create them and pass them to Insider. Read more on the [implementation guide](/docs/advanced-implementation-guide). ## Create an install journey You can create an install journey to show a warm welcome, guide your users for easy use of the app, drive them to their first purchase. Let's say you have a clothing app. Jack has installed your app but has not signed up or has not made a purchase yet. You **wait** for a while for him to use the app and check if he has completed the desired action. If not, you check his **reachability** on **app** **push** and send an **app push notification** that encourages him to take a look inside! ### 1. Select a starter **On Past Behavior** has a predefined App Lifecycle segment. You can select the "have installed" option ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/08352d93-c27e-4f42-b433-1948f6f08059.png) your title goes hereSelect the 1-day working period as the install attribute is updated once a day. Read more about [On Past Behavior](/docs/what-is-on-past-behavior). ### 2. Add flow logic We recommend you use the install-onboarding journey in the first 7 days after users install your app to engage them more. You can arrange space-outs between interactions accordingly with the wait elements. your title goes hereRead more about the [wait elements](/docs/what-is-wait-element). If you are planning to send a message to lead users to the desired action, you can give users some time to complete your desired goal before the interaction. For example, once the user installs the app, you may want to drive them to sign up. Users may sign up right after installing the app until you send a message. You can check if they already signed up or not with [Check Conditions](/docs/what-is-check-conditions). The default **sign-up** event is **only** for the website. To send a sign-up event from the app, you can add it to your SDK. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/8ebac2f2-f618-4ea0-b692-b94a3c70ef75.png) Before sending a welcome message, you can [check if users are **reachable**](/docs/what-is-check-reachability) on that channel. If not, you can try another channel on another path. You can add a **Wait** element after the messaging step with at least a 1-hour duration to wait for users to perform the desired action. Afterwards, you can check if they reach your goal (e.g. purchase, sign up, book a room, etc.). Accordingly, you can branch your journey flow to the different paths to send more relevant, contextual messages. Once a user signs up on your app, you can take them on a welcome journey to evaluate different parts of the customer journey easily. You can select one of the predefined segments in the Check Conditions. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/30e7695a-68ad-444c-bf47-3eb2908b9258.png) For example, you select the **purchase** segment to see whether a user has not made a purchase based on the waiting duration (1 hour). ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/a5bd77ce-e5c3-4d8b-a267-26094a3cc855.png) You can also select **standard** **segments** to filter users.![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/9aec185e-1736-434d-8c53-9fbbb9ce1381.png) your title goes hereRead more about [Check Conditions](/docs/what-is-check-conditions). ### 3. Create content For the first interaction, we recommend the app push notification or in-app as you may not have the user’s email or any other information if they do not sign up for the app. If they sign up, you can also create interaction via email, SMS, Facebook, web push, and on-site channels. your title goes hereTargeting users across different platforms such as websites and apps requires unification. Make sure you have the same unification identifier on both web and app. Unification enables you to provide a consistent experience across channels and platforms. Install messages are your brand’s first impression. It is quite a valuable moment to show your warm welcoming with outstanding content. - You can personalize messages based on user properties. - You can give some special offers or discounts to new users to engage them. - You can add your how-to guides to educate users. - You can share the most popular products in your emails. - You can include features that are valuable for users. your title goes hereWe strongly recommend that the content design be consistent with the design on your website and mobile app, and the images & GIFs have high resolution. Include deep links in emails that automatically open a relevant page on the mobile app, rather than driving your customers to the website. This ensures a seamless experience between the email and the app, ensuring customers are directed to the exact content rather than having to look for details themselves, which increases drop-off rates. #### App Push ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/80143610-6138-4e20-9c9a-f135f2a8517b.png) ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/42848211-23c3-485a-aa47-d142385319dc.png) #### In-App ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/e57de83a-19b9-485b-9350-6552b2daf03e.png) ## Advanced install journeys You can move your journey to an advanced level by checking user behavior and interactions. You can have the second interaction step with non-engaged users who did not perform your desired action after the first install message. You can set special goals besides **purchase** for the users who enter the welcome journey (e.g. ride booking, redeeming coupons, adding items to cart, etc.). You can have a custom event to set goals or you can use default events as well as their event parameters. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/b14139e5-8eeb-46ea-b605-7b940e7d4f33.png) ## Related - [Architect Use Case: Cart Abandonment](/architect-cart-abandonment.md) - [Architect Use Case: Browse Abandonment](/architect-browse-abandonment.md) - [Architect Use Case: Welcome/Onboarding](/architect-welcome-onboarding.md) - [Architect Use Case: Cross-Selling](/architect-cross-selling.md) - [Architect Use Case: Post-Purchase](/architect-post-purchase.md) - [Architect Use Case: Lead Generation](/architect-lead-generation.md) - [Architect Use Case: Birthday](/architect-birthday.md)