Commerce & Catalog Item Events
How to set up activity tracking and commerce interactions via the SDK.
This guide explains how to send commerce and catalog-related user interactions to Pushly using the Android SDK. These events power features like abandoned cart notifications, saved item reminders, revenue attribution, and catalog-driven recommendation campaigns.
The Pushly Android SDK must be loaded and initialized before sending any of the events described below.
The following steps assume that you are providing an item catalog/feed to our team. Please contact your account manager for more information on this process.
Supported Interaction Types
Pushly supports the following commerce and catalog interactions:
view_item – A user views an item detail page
save_item – A user saves or favorites an item
unsave_item – A user removes saved or unfavorites an item
complete_item – A user completes an item
uncomplete_item – A user removes completed item
rate_item – A user rates an item
unrate_item – A user removes rating from an item
add_to_cart – A user adds an item to their cart
update_cart – A user modifies cart contents or quantities
purchase – A user completes a transaction
Each interaction can reference items using one of three identifier types, depending on your catalog configuration.
Each item requires an id. Quantity and rating are optional unless otherwise noted.
All of the following code snippets must be ran after the SDK has been initialized.
View Item
Send this event when a user views an item detail page.
Save Item
Use this event when a user saves, favorites, or bookmarks an item. This enables saved‑item reminder campaigns.
Unsave Item
Use this event when a user removes an item from the saved list, favorites, or bookmarks.
Complete Item
A user marks an item as completed after finishing its intended experience.
Uncomplete Item
Use this event to revert the completion of an item.
Rate Item
The rate_item event includes an optional rating property. If provided, rating must be a numeric value between 0 and 100 inclusive, with up to 1 decimal place. Integer values are valid.
Unrate Item
Use this event when a user removes the rating from an item.
Add To Cart
Send this event whenever a user adds an item to their cart. Pushly will accumulate cart state across multiple calls.
You may call add_to_cart as many times as necessary to keep track of all items in a visitor's cart. Abandoned Cart notifications may be sent for any item in a customer's cart that has not been purchased.
After a purchase is made the visitor's cart will be emptied and no notifications for a purchased item will be sent to the visitor.
Update Cart
Use this event when a user changes their cart without completing a purchase, such as adjusting quantities or removing items.
To remove an item from the cart call the update_cart method with the full current cart information (omitting the removed item):
Or if the cart has been completely emptied provide an empty array:
Purchase
Send this event after a successful checkout. This clears abandoned cart state and enables revenue attribution.
Purchase Fields
priceValue – Total purchase amount, in the currency configured for the domain
purchaseId – Unique order identifier
If a purchase event is sent without item data, Pushly will still clear the user’s cart state.
Currency handling
price_value must be provided in the currency configured for the domain in the platform’s domain settings.
Use a period (.) as the decimal separator for all currencies, regardless of locale. Do not use commas.
Examples:
USD:
"344.33"JPY:
"5000"
Required Fields Summary
idis required for all itemsquantityis required only when tracking cart or purchase quantitiesratingis required only when rating an item
Implementation Best Practices
Initialize the SDK early in the page lifecycle to avoid missed events.
Use consistent item IDs across all interaction types so Pushly can correctly associate behavior.
Trigger purchase events from a reliable confirmation step whenever possible to avoid false abandoned cart notifications.
Last updated