Ingesting Data for Cross-Platform Personalizations with Architect Journeys

Your users may be on multiple platforms and perform the same action on each. Once you have more than one platform, you can personalize your message and interactions based on user behavior and activities regardless of the platform. Also, you may want to pass the user events from your end by ingesting them to Insider.

Fundamentally, Architect provides two solutions to have cross-platform personalizations:

Event Parameter Personalization

You can use the Add Dynamic Content option to add event parameters and use their values in your content.

You can use event parameters in the following channels in your journey:

Insider collects events from the web, mobile app, and offline platforms. The system takes a user's last activity into account to show dynamic content. This enables you to display the most relevant content to your users regardless of their data source.

Some strategies may not require the details of their last action (i.e., event parameter) or the latest updated value of an attribute. Instead, they may require an event parameter of the event that was used when a user entered a journey for the first time. Read more on constant event parameters in journeys.

Insider provides the mainly used (default) events out of the box only for your website. Read more on default events and attributes.

Your title goes here

To use default or custom event parameters in your content, make sure to have the respective event integration completed for each platform:

Mobile app: You should send the default events and their parameters to Insider
Upsert User Data API: You should upsert/ingest the default event and their parameters to Insider as applicable
Custom: You should send any custom event and its parameters to Insider

Your title goes here

You can send any custom event via a website and mobile app via either. You can also use our Upsert User Data API to pass your online or offline events as applicable.

Cart, Browsed, and Purchased Items

Fundamentally, the system uses event parameters to collect user behavior and product-related information on both the website and mobile app. This system gets the value of cart items, browsed items, and purchased items, allowing you to build hyper-personalization for your users across the platforms and create a data-driven engagement experience.

Take, for example, a cart abandonment journey. Users add items to their cart but do not buy them on mobile apps or websites. If they complete the "item_added_to_cart" event, they will enter the cart abandonment journey and proceed to the messaging step if they still do not buy the item.
Let's say you are sending a web push or an email. You can use the Add Dynamic Content to add "abandoned product information keys" or "last_abandoned_product_name" attribute on the respective design page. The system takes the parameters of the "item_added_to_cart" and “cart_page_view” events, such as product name, URL, image, price, etc., and displays their value in the message.

Your title goes here

To have cross-platform personalizations for cart abandonment, browse abandonment, or post-purchase use cases, Insider One team should enable “Cart/Browsed/Purchased Items from Event Parameters” for your account.

your title goes here

"Cart/Browsed/Purchased Items from Event Parameters" is based on default events and their parameters. It does not take value from the custom events. Insider collects the following events and their parameters by default while you need to pass them to Insider on your mobile app through SDK Integration:
- item_added_to_cart
- item_removed_from_cart
- cart_cleared
- cart_page_view
- product_detail_page_view
- purchase (confirmation_page_view)

your title goes here

Although "item_removed_from_cart" and "cart_cleared" events are not for dynamic content personalization, they are used to calculate the last eight abandoned items. In this calculation, the items removed from the cart are excluded.

The tables below show the relation between event parameters and dynamic contents.

Cart Abandonment

Your title goes here

Insider One team should enable the Cart Page View event for your account.

Your title goes here

You should pass the required parameters for the cart page view, item added to cart, item removed from cart, and cart cleared events from your mobile app to Insider. By default, Insider passes the parameters for the respective events from the web.

Event	Event Parameter	Description	Dynamic Content Name
item_added_to_cart item_removed_from_cart cart_page_view	na	Name	Abandoned Cart Item Name (1,2,..,8) Last Abandoned Product Name
item_added_to_cart item_removed_from_cart cart_page_view	pid	Product ID	Abandoned Cart Item ID (1,2,..,8)
item_added_to_cart item_removed_from_cart cart_page_view	url	URL	Abandoned Cart Item URL (1,2,..,8) Last Abandoned Product URL
item_added_to_cart item_removed_from_cart cart_page_view	piu	Product image URL	Abandoned Cart Item Image (1,2,..,8) Last Abandoned Product Image
item_added_to_cart item_removed_from_cart cart_page_view	up	Unit price	Abandoned Cart Item Original Price (1,2,..,8) Abandoned Cart Item Original Formatted Price (1,2,..,8)
item_added_to_cart item_removed_from_cart cart_page_view	usp	Unit sale price	Abandoned Cart Item Price (1,2,..,8) Abandoned Cart Item Formatted Price (1,2,..,8)
item_added_to_cart item_removed_from_cart cart_page_view	qu	Quantity	Abandoned Cart Item Quantity (1,2,..,8) Total Cart Item Count
item_added_to_cart item_removed_from_cart cart_page_view	usp	Unit sale price	Last Abandoned Cart Amount Total Cart Amount
item_added_to_cart item_removed_from_cart cart_page_view	pid	Product ID	Total Cart Item Kind
item_added_to_cart item_removed_from_cart cart_page_view	cu	Currency	Cart Item's Currency
cart_cleared	-	-	-

Browse Abandonment

Your title goes here

Insider One team should enable the Product Detail Page View event for your account.

Your title goes here

You should pass the required parameters for the product detail page view event from your mobile app to Insider. Insider passes the parameters for this event from the web by default

Event	Event Parameter	Description	Dynamic Content Name
product_detail_page_view	na	name	Browsed Item Name (1,2,..,8) Last Visited Product Name
product_detail_page_view	pid	Product ID	Browsed Item ID (1,2,..,8) Total Browsed Item Count
product_detail_page_view	url	URL	Browsed Item URL (1,2,..,8) Last Visited Product URL
product_detail_page_view	piu	Product image URL	Browsed Item Image (1,2,..,8) Last Visited Product Image
product_detail_page_view	up	Unit price	Browsed Item Original Price (1,2,..,8) Browsed Item Original Formatted Price (1,2,..,8)
product_detail_page_view	usp	Unit sale price	Browsed Item Price (1,2,..,8) Browsed Item Formatted Price (1,2,..,8)
product_detail_page_view	cu	Currency	Browsed Items' Currency

Post-Purchase

Your title goes here

To use purchased items in your content, Insider One team should enable the Cart/Browsed/Purchased Items from Event Parameters for your account

Your title goes here

Insider One team should enable the Purchase event for your website

Your title goes here

You should pass the required parameters for the purchase event from your mobile app to Insider. Insider passes the parameters for this event from the web by default.

Event	Event Parameter	Description	Dynamic Content Name
purchase	crea	Create date	Last purchase date
purchase	usp	unit_sale_price	Purchased Item Price (1,2,..,8) Purchased Item Formatted Price (1,2,..,8) Last Purchase Amount Total Purchased Amount
purchase	na	Name	Purchased Item Name (1,2,..,8) Last Purchased Product Name
purchase	url	URL	Purchased Item URL (1,2,..,8) Last Purchased Product URL
purchase	cu	Currency	Purchased Items' Currency
purchase	qu	quantity	Purchased Item Quantity (1,2,..,8) Total Purchased Item Count
purchase	up	unit_price	Purchased Item Original Price (1,2,..,8) Purchased Item Original Formatted Price (1,2,..,8)
purchase	piu	product_image_url	Purchased Item Image (1,2,..,8)
purchase	pid	product id	Purchased Item ID (1,2,..,8) Total Purchased Item Kind

Your title goes here

Purchased items are automatically grouped based on user's same last purchase transaction.

Category/Listing Page Abandonment

Your title goes here

Insider One team should enable the Category Page View event for your website

Your title goes here

You should pass the required parameters for the category page view event from your mobile app to Insider. Insider passes the parameters for this event from the web by default.

Event	Event Parameter	Description	Dynamic Content Name
listing_page_view	na	Name	last_visited_category
listing_page_view	url	URL	last_visited_category_url