Skip to main content

Events You Can Create for Your E-Commerce Website

A quick guide on what customer events and key operators your platform can send to Gameball.

Ahmed El Assy avatar
Written by Ahmed El Assy
Updated over a week ago

Are you looking for the most valuable customer events to track on your e-commerce website using Gameball? Below are six essential examples of events you can track to build a highly engaging, action-based loyalty program.

To learn more about events, read:


Section 1: Standard E-Commerce Events

The following events are the foundation for tracking key customer interactions on your e-commerce website. These events will allow you to build more personalized campaigns, track conversions, and improve customer engagement.

Key Events

Event

Description

Event Properties

Product Page Viewed

Triggered each time a customer views a product details page.

product_id, product_name, category, brand, price, currency, discounted (boolean), stock_status, tags

Cart Viewed

Triggered when a customer views their cart.

cart_id, cart_items (array with product IDs, names, quantities, prices, categories), cart_total, currency

Order Reviewed

Sent when a customer reviews their order before checkout.

order_id, cart_id, items (array with product IDs, names, quantities, prices, categories), cart_total, currency, coupon_code (if applied)

Product Reviewed

Sent when a customer submits a product review.

product_id, rating, title (optional), body (optional), has_image (boolean), review_images (array of URLs if available)

Profile Completed

Triggered once a customer completes their profile (adds missing details such as name, phone, address, etc.).

customer_id, completed_fields (array of fields completed), profile_completion_percentage

Order Placed

Triggered when a customer completes a purchase.

order_id, cart_id (or session_id), items, total, currency, coupon_code (if applicable), payment_method, shipping_method

⚠️ Disclaimer: There is no need to send the Order Placed event if you are already using Gameball’s Order API, as the Order Placed event will be fired automatically by Gameball.

Important Notes:

  • The suggested keys below are examples. Feel free to modify or add new keys based on your platform's structure and needs.

  • You can add more event properties as long as you have use cases for them in segmentation, campaigns, or analytics.

  • Performance Optimization Tip: Avoid sending unnecessary events to maintain the best performance for your system.


Section 2: Abandoned Cart Checkout Events

To enable abandoned cart campaigns, implement the following events. Note that Add to Cart and Remove from Cartare not needed—instead, use the consolidated events below:

Key Events

Event

Description

Event Properties

Cart Updated

Sent every time a user adds, removes, or updates items in their cart. Keeps Gameball updated with the latest cart status.

cart_id (string, required), cart_items (array with product IDs, names, quantities, prices, categories), cart_total, currency, last_updated_at

Checkout Started

Sent when the user begins the checkout process. Helps differentiate between cart abandonment (never reached checkout) and checkout abandonment (left during checkout).

cart_id (string, required), cart_items, cart_total, currency, checkout_metadata (optional: payment_method, shipping_method, delivery_address)

Order Placed

Automatically fired once Gameball receives the Order API call. Ensure the event includes either the session_id or cart_id so that Gameball can link the order back to the cart.

order_id, cart_id or session_id, items, total, currency, payment_method, shipping_method

⚠️ Disclaimer: There is no need to send the Order Placed event if you are already using Gameball’s Order API, as the Order Placed event will be fired automatically by Gameball.

Important Notes:

  • You can add more event properties as long as you have use cases for them in segmentation, campaigns, or analytics.


Related Articles:

Did this answer your question?