Glossary
For everyone
A quick reference for the words that appear across these docs. Terms are grouped by topic. Developer-specific keys link to where they are used.
Core tracking terms
Event A single reported moment from the app, such as a product view or a purchase. Events are what the SDK sends to Segmentify.
Event family
The category an event belongs to (for example, page view, basket operations, user operations). The technical name is the event name.
Step
A sub-action within some event families. For example, basket operations have steps add, remove, and clear; checkout has steps like view-basket and purchase.
Payload The data carried by an event — the business fields you provide plus the context the SDK adds automatically.
Enrichment The context the SDK attaches to every event for you (user, session, device, currency, language, and more), so you only send business fields.
Identity and visits
User / userId
A person, tracked across visits with a stable identifier. Linked to an email once the shopper is known.
Session / sessionId
A single visit. One user has many sessions over time.
Identify Reporting or updating who the shopper is and what they consented to.
Consent A record of whether a shopper agreed to be contacted on a channel (email, SMS, WhatsApp, call). Valid values are subscribed, unsubscribed, or not set.
IYS A consent registry used in certain markets (İleti Yönetim Sistemi). The SDK can send IYS permission information alongside user events when relevant.
Pages and navigation
Page type Segmentify’s vocabulary for the kind of screen a shopper is on (for example, Home Page, Product Page, Basket Page).
pageTypeMapping
The configuration that maps your app’s technical screen names to Segmentify page types. Keeping it aligned with your web setup keeps campaigns consistent. See the Page Mapping Guide.
Unknown Page
The fallback page type used when a screen name is not present in pageTypeMapping. Events still send, but reporting quality drops.
Search
Instant search A plain keyword search (including the “before search” state while the shopper is opening search or typing).
Faceted search / Searchandising A search refined with filters and merchandising rules that influence how results are ranked.
Widgets and campaigns
Interaction A reported engagement with on-screen content — an impression, a view, a click, or a close.
instanceId
The identifier of a specific campaign or widget instance. It ties an interaction back to the campaign that produced it.
interactionId
An identifier for a specific interaction. Note for developers: when instanceId is provided, the SDK sets interactionId to match it (see Known Gotchas).
Popup / Banner campaign On-screen promotional content Segmentify can trigger. The lifecycle (shown, clicked, closed) is reported via interactions. See Popups, Search and Push.
Customer Data Platform (CDP)
CDP The part of Segmentify that stores rich shopper profiles for segmentation and targeting.
User Traits Arbitrary profile attributes (demographics, loyalty tier, preferences) sent to enrich a shopper’s CDP profile. See Customer Data Platform Events.
Push notifications
FCM token A device-specific identifier from Firebase Cloud Messaging that lets Segmentify deliver push notifications to that device.
Deep link A link that opens a specific screen inside your app (for example, a product page) rather than a web page.
Universal link A standard web URL that, when tapped, opens directly in your app if it is installed. Supported for push notifications.
Configuration and testing
API key The credential that identifies your Segmentify account to the SDK.
testMode
A flag marking events as test data so they can be separated from real analytics.
Debug mode A logging setting that prints SDK activity (including the final payload sent) to help during development.
Where to go next
- New to the system? Start with What is Segmentify?.
- Want the business meaning of each event? See the Event Catalog in Plain Language.
- Need exact field names? See Event Parameters and Types.