Business use cases

What to track

Unknown event names are accepted and stored as custom events. Names can't be empty or contain control characters.

// 1. A custom event in a category, sent as commerce:purchase.
client.track('commerce:purchase', {}, { amount: 99, currency: 'SAR' });
//    A name without a category works too:
//    client.track('loan_application_started', {}, { amount: 50000 });

// 2. An engagement event: the person tapped the block's call to action.
client.trackCtaClick(block);

import { useCF, useCFBlock } from '@contentflow/sdk/react';

function OfferCard() {
  const cf = useCF();
  const block = useCFBlock('home_banner');

  // 1. A custom event in a category, sent as commerce:purchase (call it from your checkout).
  const onPurchase = () => cf.track('commerce:purchase', {}, { amount: 99, currency: 'SAR' });
  //    A name without a category works too:
  //    cf.track('loan_application_started', {}, { amount: 50000 });

  if (!block) return null;
  // 2. An engagement event: the person tapped the block's call to action.
  return <button onClick={() => cf.trackCtaClick(block)}>{block.ctaLabel}</button>;
}

import { Button } from 'react-native';
import { useCF, useCFBlock } from '@contentflow/sdk/react-native';

function OfferCard() {
  const cf = useCF();
  const block = useCFBlock('home_banner');

  // 1. A custom event in a category, sent as commerce:purchase (call it from your checkout).
  const onPurchase = () => cf.track('commerce:purchase', {}, { amount: 99, currency: 'SAR' });
  //    A name without a category works too:
  //    cf.track('loan_application_started', {}, { amount: 50000 });

  if (!block) return null;
  // 2. An engagement event: the person tapped the block's call to action.
  return <Button title={block.ctaLabel} onPress={() => cf.trackCtaClick(block)} />;
}

// 1. A custom event in a category, sent as commerce:purchase.
try await client.commerce(CommerceEvent(action: .purchase, amount: 99, currency: "SAR"))

// 2. An engagement event: the person tapped the block's call to action.
try await client.trackEngagement(.ctaClick(block))

import click.contentflow.events.CommerceAction
import click.contentflow.events.CommerceEvent

// 1. A custom event in a category, sent as commerce:purchase.
client.commerce(CommerceEvent(commerceAction = CommerceAction.Purchase, amount = 99.0, currency = "SAR"))

// 2. An engagement event: the person tapped the block's call to action.
client.track(CFEngagementEvent.of(block, CFEngagementEvent.CTA_CLICK))

final cf = ContentFlow.instance;

// 1. A custom event in a category, sent as commerce:purchase.
await cf.commerce(CommerceEvent.typed(action: CommerceAction.purchase, amount: 99, currency: 'SAR'));

// 2. An engagement event: the person tapped the block's call to action.
await cf.trackCtaClick(blockKey: block.key, instanceId: block.id);

Industry vocabularies

Typed helpers record standard events per sector, so dashboards and journeys speak your business's language, for example client.trackBanking('transfer_completed', { amount: 2500, currency: 'SAR' }):

Fintech apps use trackBanking and custom events; there's no separate fintech helper yet.

Event pipeline

Accepted, dropped, rejected

What the dashboards show

• Impressions count impression, banner_impression and block_view; clicks count tap, banner_click and cta_click; click rate and conversion rate are both per impression.
• Engagement over time, hourly activity, daily reach, conversions by segment, location and geofence activity, experiment results, and exports.
• Per person: the last 500 events, with an analytics card on the person's page.
• Funnels: from your events and from sensor trackers.

Behaviour becomes segments

Every hour (at minute 50) ContentFlow writes each person's last 90 days into enrichment attributes you can use in segments: enrichment.analytics_impressions, analytics_clicks, analytics_conversions, analytics_events_total, analytics_last_active_days and analytics_ctr. Example: clicked at least 3 times, no conversions, active in the last 7 days.

Test data

Events from a test key are stamped env: test, excluded from live dashboards and never update block counters. Test mode in the dashboard shows them, with a test summary and a button to delete test data.

Privacy and retention

• No analytics consent, no events: dropped in the SDK and again by the server.
• Events are kept for 365 days; hourly activity views for 30 days.
• Erasure deletes a device's events.
• Anonymous visitors are counted with a salted visitor hash that rotates monthly.

Offline and queued events

Events wait on the device while there is no network, within limits that differ by platform: JavaScript and Flutter keep a stored outbox that survives a restart, Swift keeps its queue in memory only, and Kotlin sends each event at once without queueing it. Every queue holds at most 500 items and drops the oldest first, and nothing is queued before analytics consent. Flush before sign-out: Flutter's logout() clears its queues. The limits, retries, inspection methods and flush samples per platform are in Offline, queues and delivery.

Getting data out

• Reports: in the dashboard, Reports requests a report across segments, people, audit logs, analytics or delivery, with filters and a choice of columns. Finished files are under Downloads, and Scheduled repeats a report on a schedule.
• Per person, from your backend: the read key answers which devices and segments ContentFlow holds for a user (REST guide: read key).
• As things change: webhooks notify your systems of campaign changes (REST guide: webhooks).

Report types, filters, columns, formats and scheduling are covered in Reports and exports.

When it doesn't work

Next

• Sensors: measure any text in your app without inventing event names.
• Segments: target people using the enrichment.analytics_* fields the roll-up writes.