Testing real time events

User event history is critical for machine learning sourcing and scoring. Moloco uses this first party data to deliver relevant ads at the right time. This is accomplished by sending user event data via Event service API. Please work with your Moloco representative to test these real-time event scenarios to ensure the events are delivered correctly.

Note: This list may not cover all possibilities. Depending on your site's features and how it's implemented, additional tests may be necessary for scenarios not mentioned here.

Please see our troubleshooting guide user event API failure protocol if you encounter an unexpected result.

Test Case	Test Steps	Expected Result - Customer	Expected Result - Moloco
Home	Visit site Home page.	Event call is sent to Moloco. No validation error is triggered.	HOME* event is logged correctly.
Page View	Visit a page on the site.	Event call is sent to Moloco. No validation error is triggered.	PAGE_VIEW* event is logged with the appropriate page_id.
Item Page View	Click on an item from a product list and view the item page.	Event call is sent to Moloco when the page is actually viewed. No validation error is triggered.	ITEM_PAGE_VIEW* event is logged with the appropriate item_id.
Item Page View with referrer	Perform a web search for a product on the site. Click on an item from the site to visit the item page.	Event call is sent to Moloco when the page is actually viewed. No validation error is triggered.	ITEM_PAGE_VIEW* event is logged with the appropriate item_id and “referrer_page_id”.
Add to Cart	Click on the Add to cart button on the page.	Event call is sent to Moloco. No validation error is triggered.	ADD_TO_CART* event is logged with the appropriate item_id.
Add to Wishlist	Click on the wishlist button on the site.	Event call is sent to Moloco. No validation error is triggered.	ADD_TO_WISHLIST* event is logged with the appropriate item_id.
Search	Perform a generic search from the initial search box on the site.	Event call is sent to Moloco. No validation error is triggered.	SEARCH* event is logged with the appropriate search query.
Search with Category	Open up a category page. Perform a search from the category search box.	Event call is sent to Moloco. No validation error is triggered.	SEARCH* event is logged with the appropriate search query and the correct "category".
Purchase	Purchase an item.	Event call is sent to Moloco. No validation error is triggered.	PURCHASE* event is logged with the appropriate item_id with the revenue information.

We recommend verifying a unique user ID is sent with user events using the user_id field. Customers should use the unique device identifiers for mobile devices in the persistent_id field. Moloco requires either the user_id and the persistent_id fields to be included in the Event API request and these identifiers should be hashed before sending them to Moloco. This allows Moloco to match the user event trail of a logged-out if the user then logs into the site or app.

Please see the Event API and Generating persistent identifiers documentation for more details on these fields.

Test Case	Test Steps	Expected Result - Customer	Expected Result - Moloco
Logged-in Users	Verify that a unique platform user ID is used for logged-in users and hashed. This ID should be sent in the `user_id` field	A unique user ID is sent in the Event API call and remains the same during the period of user activity.	The hashed user ID is captured by Moloco when the user logs into the site or app and begins browsing
Logged-out Users	Verify that the unique ID is generated for logged out users and hashed. This ID should be sent in the `persistent_id` field	A unique generated ID is sent in the Event API call and remains the same during the period of user activity.	A unique hashed user ID is captured by Moloco when a logged out user accesses the site or app.