DATA ORCHESTRATION
Capabilities
Context reporting & schemas
Context is the raw material of every personalized experience. Flybits gives you a typed, versioned way to describe what you know about a customer, several ways to report it, and a history of how it changed.
Reported context is what audience selection, triggers and personalization all read from. The platform separates the definition of a context object from the mechanism used to populate it, so the same rule works whether a value arrives from your server, a CSV or a device.
REPORT → SCHEMA → CONTEXT PLUGIN
Server API▸Context schema▸Attribute values
CSV upload▸Bulk import▸Test users
Device SDK▸Reported context▸Historical plugin
WHAT IT DOES
Typed context schemas
A schema declares the shape of a context object — its attributes, types and units — before any data arrives. Because the shape is known up front, rules and audiences written against it stay valid as sources change, and a new source only has to map into an existing schema.
Parameterized attributes
Attributes can take parameters, so a single definition covers a family of values — balance by account, limit by product, status by relationship — without declaring one attribute per case.
Several reporting paths
The same schema can be populated server-to-server through the data management APIs, in bulk by CSV for onboarding and testing, or directly from a device through the mobile and web SDKs.
Historical context
Context plugins retain values over time, so rules can reason about trend and recency — not only what is true right now, but what changed and when.
IN DETAIL
—
Schemas are defined once and then referenced by rules, audiences and triggers rather than restated per experience.
—
Parameterized attributes cover families of values — balance by account, limit by product — from a single definition.
—
Context data files let an experience be driven by an uploaded dataset, useful for campaign lists and pilots.
—
Historical context plugins keep prior values so rules can look at change and recency, not only current state.
SERVICES & BUILDING BLOCKS
CONTEXT SCHEMA
Typed definition of a context object and its attributes, versioned and reusable across experiences.
API REPORTING
Server-to-server reporting of attribute values for a user, device or account.
CSV UPLOADING
Bulk load for onboarding, backfills and test users, validated against the schema on import.
PARAMETERIZED ATTRIBUTES
One attribute definition that resolves per parameter, keeping schemas compact.
HISTORICAL CONTEXT PLUGINS
Retention of prior values so trend, frequency and recency can be evaluated.
DEBUG / USER STATE
Inspect the resolved context for a specific user or device when validating a rule.