Skip to content
Segmentify React Native SDK Docs

Event Catalog (Plain Language)

For everyone

This is the business-friendly tour of every event the SDK can send. Each entry answers two questions: what does it track? and why does it matter? Each one links to the precise developer reference if you need field names.

How to read this page

Events are grouped by the kind of shopper behavior they capture. You don’t need all of them on day one — most teams start with page, product, basket, and purchase, then add the rest.

Browsing: pages and products

Page View

  • What it tracks: which screen the shopper is on, every time they navigate.
  • Why it matters: it is the backbone of analytics and lets campaigns target specific page types (home, category, product, basket).
  • Developer reference: Page and Product Events.

Product View

  • What it tracks: a shopper opened a product’s detail page.
  • Why it matters: the primary signal for “what are people interested in”, and the fuel for product recommendations.
  • Developer reference: Page and Product Events.

Buying: basket and checkout

Basket Add / Basket Remove / Basket Clear

  • What it tracks: items going into, out of, or being cleared from the cart.
  • Why it matters: reveals purchase intent and cart-abandonment opportunities; powers “you left this behind” campaigns.
  • Developer reference: Checkout and Basket Events.

Basket View

  • What it tracks: the shopper opened the cart screen.
  • Why it matters: marks the start of the checkout funnel, so you can measure drop-off.
  • Developer reference: Checkout and Basket Events.

Purchase

  • What it tracks: a completed order, with totals and the items bought.
  • Why it matters: the most important conversion signal — it ties revenue back to campaigns and recommendations. It should fire exactly once per order.
  • Developer reference: Checkout and Basket Events.

Customer & Payment Information (optional checkout steps)

  • What it tracks: the shopper reached the customer-details or payment stage.
  • Why it matters: finer funnel measurement for multi-step checkouts.
  • Developer reference: Checkout and Basket Events.

Saving for later: wishlist

Favorite Add / Favorite Remove / Favorite View

  • What it tracks: items added to, removed from, or shown in the wishlist.
  • Why it matters: strong interest signals that improve recommendations and enable “back in stock / price drop” style messaging.
  • Developer reference: User and Wishlist Events.

Register / Login / Logout

  • What it tracks: sign-up, sign-in, and sign-out moments.
  • Why it matters: links anonymous activity to a known person, enabling personalized, cross-device experiences.
  • Developer reference: User and Wishlist Events.

Identify

  • What it tracks: updates to a shopper’s profile or communication preferences.
  • Why it matters: keeps contact details and consent current so campaigns stay compliant and relevant.
  • Developer reference: User and Wishlist Events.

Customer Data Platform (User Traits, Subscribe/Unsubscribe, and more)

  • What it tracks: richer profile attributes (demographics, loyalty tier, preferences) and channel subscriptions.
  • Why it matters: powers segmentation and targeting beyond the basic lifecycle — “gold-tier members in New York”, for example.
  • Developer reference: Customer Data Platform Events.
  • What it tracks: what shoppers search for, including the difference between starting a search, completing a keyword search, and applying filters (“searchandising”).
  • Why it matters: improves search ranking and surfaces gaps (searches with no results) and merchandising opportunities.
  • Developer reference: Search, Interaction, Form and Custom.

Engaging: interactions, forms, and campaigns

Interaction

  • What it tracks: engagement with on-screen widgets, recommendations, popups, and campaign content (impressions, views, clicks, closes).
  • Why it matters: measures whether the personalized content actually works.
  • Developer reference: Search, Interaction, Form and Custom.

Form

  • What it tracks: submission of a form (for example a newsletter signup).
  • Why it matters: captures lead generation and preference collection.
  • Developer reference: Search, Interaction, Form and Custom.

Gamification

  • What it tracks: outcomes from gamified campaigns such as wheel-of-fortune or scratch cards.
  • Why it matters: measures engagement and reward redemption from playful campaigns.
  • Developer reference: Search, Interaction, Form and Custom.

Re-engaging: push notifications

Push Subscribe

  • What it tracks: a device opted in and registered for push.
  • Why it matters: builds the audience you can reach with push campaigns.
  • Developer reference: Push Notification Events.

Push Interaction (View / Click)

  • What it tracks: whether a push notification was seen and whether it was tapped.
  • Why it matters: measures push campaign performance and attributes the visits that follow a tap.
  • Developer reference: Push Notification Events.

A sensible rollout order

  1. Page View + Product View (browsing analytics and recommendations)
  2. Basket Add/Remove + Basket View + Purchase (the conversion funnel)
  3. Register / Login / Logout / Identify (known-user personalization)
  4. Search and Interaction (search quality and content performance)
  5. Push and Customer Data Platform (re-engagement and advanced targeting)

Where to go next