Skip to content
Segmentify React Native SDK Docs

What is Segmentify?

For everyone

No code here. This page explains, in plain language, what the Segmentify React Native SDK is and why a team would use it. If you are ready to integrate, jump to the Developer track.

In one sentence

Segmentify is a personalization and customer-engagement platform. The React Native SDK is the piece that lives inside your mobile app and quietly reports what shoppers do, so Segmentify can power recommendations, search, popups, and push/email/SMS campaigns that feel personal.

What the SDK actually does

Think of the SDK as a messenger between your app and Segmentify:

  • Your app tells the SDK about meaningful moments (“a product was viewed”, “an item was added to the cart”, “an order was completed”).
  • The SDK packages each moment as an event, attaches some context (which device, which session, which user), and sends it to Segmentify.
  • Segmentify uses those events to build a picture of each shopper and to decide what to recommend, what to search-rank, and which campaigns to trigger.

The SDK does not redesign your app or take over your screens. You stay in control of the UI; the SDK just listens for the moments you choose to report.

Why it matters for the business

CapabilityWhat the events make possible
Personalized recommendations”Customers who viewed this also bought…” needs product-view and purchase events.
Smarter searchSearch events let Segmentify learn which queries lead to which products.
Conversion analyticsBasket and purchase events show where shoppers drop off in the funnel.
Targeted campaignsIdentity and consent events let you reach the right person on the right channel (push, email, SMS).
Cross-channel consistencyThe same page names and product IDs used on web keep mobile campaigns aligned.

The short version: the richer and cleaner the events, the better every Segmentify feature performs.

The three building blocks

The whole system rests on three simple ideas, explained more fully in How Tracking Works:

  1. Events — the moments you report (view, add to cart, purchase, search, login…).
  2. Sessions and users — who did it, and within which visit.
  3. Page types — a shared vocabulary for “what kind of screen is this” so mobile and web line up.

Who does what

  • Non-developers (marketing, product, analytics) decide which moments matter and what each event should mean for the business. The Event Catalog in Plain Language is written for you.
  • Developers decide where in the code to fire each event and ensure the data is correct. Their starting point is the Quick Start.

Where to go next