--- title: "Architect Journey: Wait for Attribute" slug: "wait-for-attribute" tags: ["architect wait", "wait for attribute", "wait element"] updated: 2026-03-12T14:01:08Z published: 2026-03-12T14:01:08Z canonical: "academy.insiderone.com/wait-for-attribute" --- > ## 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 Journey: Wait for Attribute **Wait for Attribute** element allows you to proceed the users in the journey with an on-time option that works whenever an attribute is updated.![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1695712700838.png) ## How does it work? Wait for Attribute element functions based on real-time actions. When a user arrives at the element, they wait until their specified attribute value gets a new specified value or the old value is replaced with a new value. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1695713441645.png) Users proceed from the wait element to the next element once the attribute for that user is created with 'X' value. - If the user is created **with** the 'X' attribute, they will proceed to the next element. - If the user is created **without** the 'X' attribute but later inserts it, they will proceed to the next element. - If the user is created **with** the 'X' attribute but later **updates** it, they will proceed to the next element. - If the X attribute is **deleted**, no change will be detected to move the user to the next element. You can select different operators to set up the Wait for Attribute element: - **The ‘changes’** operator enables users to proceed from the element when the user attribute gets a value for the first time, or the value changes. - **The ‘changes to’** operator enables users to proceed from the element when the user attribute gets a new specific value. - **The ‘changes from’** operator enables users to proceed from the element when the current specific user attribute value gets a new specific value. Your title goes hereYou can set up **a maximum of 3 attributes** with the *or* operator in this element. You can specify the maximum duration for which you want to keep users on this element and select one of the following actions that you want to take for these users if the attribute value does not change. - **Proceed to the next step**: If a user's attribute doesn’t change in the specified duration, they will proceed to the next element. - **Drop from the journey**: If a user's attribute doesn’t change in the specified duration, they will drop from the journey and be counted as dropped. Your title goes hereThis duration can be **at least 30 minutes** and **a maximum of 4 weeks/31 days**. #### Actions - **Proceed to the next step:** If users' attributes don’t change in the specified duration, they will proceed to the next element. - **Drop from the journey:** If users' attributes don’t change in the specified duration, they will drop from the journey and be counted as dropped. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1695713682520.png) Your title goes hereIt is not allowed to add the same type of wait element consecutively, or the Wait Until a Time Slot and Wait for Some Time elements consecutively. ## Use Cases You can use the Wait for Attribute element in many use cases. Some are as follows: - Send a coupon code or special offer when a user reaches a specific cart amount. - Wait for the opt-in change to send a message immediately. ### Opt-in Encouragement You are an ecommerce company that sends frequent app pushes, and your main goal this year is to decrease your opt-outs. Select the starter as “On Attribute Change” and let users into the journey when their app push opt-in attribute changes from True to False. Send a message to your user through a reachable channel to encourage them to opt in again. Also, add in the message that if they opt in, they will receive fewer messages. Then, wait for the users to **opt in again within the given period** (you can set the period as 14 days, for example). If they change their **opt-in status to True within the given time**, immediately send them a ‘thank you’ message and add them to a static segment for “users that want to get fewer messages”. If they don’t opt in after the wait period ends, let them drop from the journey. ![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1695714542168.png) ### Survey upon Application Approval You are a loan company, and you define users entering your funnel by their loan status. Users enter the journey when their loan status becomes “Applied”. After that, using Call an API, send the user data to your servers along with user attributes. Then, wait for the users' loan status to change to “Application Approved,” where you approve it. As soon as the application is approved, you want to send customers a survey so they can review your services.![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/image-1695714712749.png) ## Related - [Architect Journey: Using Wait for Some Time](/using-wait-for-some-time.md) - [Architect Journey: Wait for Some Time](/what-is-wait-for-some-time.md) - [Architect Journey: Use Wait until a Time Slot](/architect-journey-use-wait-until-a-time-slot.md) - [Architect Journey: Wait Until a Time Slot](/architect-journey-wait-until-a-time-slot.md) - [Architect Journey: Use Wait for Attribute](/architect-journey-use-wait-for-attribute.md)