Architect Journey Starter: On Back in Stock
- 05 Apr 2024
- 4 Minutes to read
Architect Journey Starter: On Back in Stock
- Updated on 05 Apr 2024
- 4 Minutes to read
Article Summary
Share feedback
Thanks for sharing your feedback!
On Back in Stock Starter takes users into the journey immediately when a particular product is back in stock, provided the user has engaged in the selected event within a specified timeframe. This starter is activated by the product's stock update across all platforms—website, mobile app, and offline environment—and subsequently segments users who have visited that product
The default event for On Back in Stock starter is set to Product Page View. If unchanged, the starter will automatically include users who visited a product in the journey immediately upon its return to stock. Opting for a different event requires users to engage in that specific event with the product to enter the journey. For instance, selecting the Item Added to Wishlist event will include users when their wishlist product is back in stock.
While the primary condition for this starter is the product's stock update, you have narrow down the user segment entering the journey with Optional Event Filters. Choose from default or custom events to create advanced conditions for journey entry.
For example, you can use On Back in Stock starter if you want to
- exclude users who already purchased the product that is back in stock.
- target users when one of their items in the cart is back in stock, and level up your cart abandonment use-case by combining it with stock alert.
- notify users when their favorite items are back in stock.
Your title goes here
In order to match the main starter condition with user events, Product ID (pid) event parameter is used. Events without a Product ID parameter can’t be used with back in stock condition.
Your title goes here
As events without Product ID (pid) event parameter can’t be used with back in stock condition, you can view and select default events that have pid event parameter.
You can view and select all custom events under Optional Event Filter, however, you will see warning messages as below when you try to save the starter element. In this case, you may add pid event parameter to the event or select an event with pid event parameter.
You can view and select all custom events under Optional Event Filter, however, you will see warning messages as below when you try to save the starter element. In this case, you may add pid event parameter to the event or select an event with pid event parameter.
You can use Product Filters in order to exclude some product categories or some particular products based on their original price. See below for some examples:
- You may consider excluding the products that are on sale from your back-in-stock journeys.
- You may consider a 20% drop in the price drop, but exclude the products whose original price is less than 10$ to not overwhelm your users with too many messages. You also may consider excluding the 5$ products that will bring little revenue.
Your title goes here
Product filters are optional. You can enable the filters based on your use case.
Your title goes here
Stock amount can not be used within the On Back in Stock starter. Starter condition considers only the “in stock” data for the products, namely whether they are in stock, or out of stock.
Additional Segmentation
You can add more segments to your starter condition to target your audience more precisely. For example, you can take users into the journey when they visit a product but do not purchase, have a high Likelihood to Purchase value, and the product is back in stock.
Users can enter the journey if they meet with main starter condition and meet the additional segment filter criteria. You can select predefined segments, standard segments, predictive segments, RFM segments, and saved segments to filter your users to take into the journey.
Tips & Tricks
- Users may come from Upsert User Data API or any other source without their language information. That’s why we suggest selecting the "All Languages" option in the launch settings.
- You can use the product filters to narrow the products that will trigger the journey for a better-targeted audience.
- You can use additional segment filters to create better segmentation for your users.
- You can use custom events for the users who add an item to their wishlist/favorites or who subscribe to a product to get notified when it is back in stock. You can use the event parameters to filter the products or categories for these events.
- On Back in Stock starter works real-time. We do not recommend using wait elements after this starter if you have a time-sensitive use case.
Use Cases
- Back in Stock: Target users who visit a specific product but do not purchase when the product is back in stock.
- Price Drop on Cart Abandonment: Target users who add an item to their cart when that item is back in stock.
- Wishlist: Target users who add an item to their wishlist or favorites when that item is back in stock.
- Product Subscription: Target users who have subscribe to a product to get notified about the discount when the item is back in stock.
Requirements
On Back in Stock starter has two types of requirements:
- Product catalog data
- User data collection
Product Catalog Data Collection
On Back in Stock utilizes the same data collection methods as the Smart Recommender product that has 3 types of product catalog database integration methods. Each method can be used singularly or combined according to your platforms and use cases.
Product Catalog Integration through Clickstream Data
Your product catalog information is processed whenever any of your customers visits your website and the product detail pages. Refer to crowd-based product feed collection.
Product Catalog Integration through XML
With this integration type, you can provide your own XML product catalog as a source for your product feed. You can implement the integration through the Inone panel, and send all the product attributes that are on the XML file to the product catalog database through the Inone panel. Read more on Product Catalog Integration through XML.
Product Catalog Integration through API
With this method, you can send your product catalog information through insertions and updates through the Catalog API. Read more on Product Catalog Integration through API.
User Data Collection
- You should complete the Insider Tag integration, and Insider Mobile SDK.
- Insider team should enable Events for your account.
- You should send the respective events from your website, mobile app, and/or offline environment via Upsert User Data API.
Was this article helpful?