Skip to main content
Flowboard does not force a tracking vendor. Use onStepChange and onOnboardEnd to send events to your own tools (MMP, ads SDK, product analytics).

What you can track from Flowboard callbacks

formData keys match your Flowboard input id values. Example:
Keep input id values stable in Flowboard. They are your analytics data contract.

Simple custom tracking examples

Use this pattern when you only need to forward events to your own tracking layer.

Concrete example: Amplitude + Adjust

The example below sends:
  • Product analytics events to Amplitude
  • Attribution / marketing events to Adjust
For Expo, use a development build or prebuild setup for native SDKs such as Adjust.

React Native / Expo (development build)

Flutter

For native iOS, install your Amplitude and Adjust SDKs in the same app target that hosts Flowboard, then forward Flowboard callbacks into those SDKs from one small bridge object.

Tracking recommendations

  • Avoid sending raw PII to ad attribution tools unless your policy allows it.
  • Keep event names stable (flow_step_viewed, flow_completed).
  • Forward only the fields your downstream tools actually use.
  • Version your event schema if you change formData keys.