CONTEXT & INTELLIGENCE
Capabilities
Analytics & optimization
Delivery is only half the loop. Flybits records what was shown, what was engaged with and what was ignored, then makes that history available as context so the next decision is better informed than the last.
Behaviour observed through analytics is one of the inputs Flybits treats as context, which is what makes the loop from delivery back to decisioning a closed one rather than a report you read separately.
EVENT → METRIC → CONTEXT → DECISION
Impression▸Event stream▸Experience metrics
Engagement▸Attribution▸Content performance
Outcome▸Historical context▸Next decision
WHAT IT DOES
Delivery and engagement events
Impressions, opens, taps, dismissals and action-link follow-through are captured per content instance and per user, through the SDKs and server-side.
Experience-level reporting
Performance rolls up to the experience, so an author can see which rule, content variant and placement combination is working.
Engagement as context
Because event history is retained as context, rules can reference it directly — suppress what has already been seen, escalate what has been ignored, and rank on prior response.
Export to your stack
Events can be forwarded to your own analytics and warehouse tooling through webhooks and server-side APIs, so Flybits reporting does not become a silo.
IN DETAIL
—
Events are captured from the SDKs and server-side, covering impressions, opens, taps, dismissals and action-link follow-through.
—
Performance rolls up per experience, content instance and placement, so authors can see which combination worked.
—
Engagement counts are available as context, so rules can suppress what has been seen and escalate what has been ignored.
—
Events can be forwarded to your own analytics stack and warehouse through webhooks so reporting is not trapped in the platform.
SERVICES & BUILDING BLOCKS
ANALYTICS EVENTS
SDK and server-side event capture for impressions and engagement.
EXPERIENCE METRICS
Aggregated performance per experience, content instance and placement.
ENGAGEMENT CONTEXT
Event history exposed back as context attributes for rules and ranking.
FREQUENCY SIGNALS
Seen, dismissed and acted-on counts that feed suppression logic.
WEBHOOK EXPORT
Push events to your own analytics, warehouse or CDP.
DEBUG TOOLS
Per-user inspection of what was eligible, what was shown and why.