Sensors. Your strings, as signals.
Turns a string already in your app into a dormant signal you can enable remotely, feeding segments, journeys and rules.
Sensors is not generally available. It is in preview, available only to selected workspaces behind a feature flag.
Enabling a sensor on a string that is already integrated does not require a new app release. Integrating the localised string and its preview instrumentation in the first place does, and needs engineering.
Four steps, once enabled.
Each one is an ordinary string on the screen in step 01: the balance line, the button on the top-up card, the top row of the shortcut list. Integrated once, a string stays dormant until an admin enables it.
Signals can be used as conditions in audience rules and journey triggers.
Sensors is in preview and available to selected workspaces behind a feature flag.
Preview today, not everywhere yet.
Preview, not general release
Sensors is available to selected workspaces behind a feature flag and is not generally available.
Eligible strings only
A string can only become a sensor once it is part of the integrated localization set, so initial coverage depends on that integration.
What a sensor can see.
Dormant string sensors
Each eligible localised string can exist as an inactive runtime observation point.
Remote activation
An integrated sensor can be enabled.
Consent-aware collection
Signal collection can be gated according to configured user consent.
Runtime signal types
The preview collects view and interaction signals from an enabled string.
Downstream activation
Signals can feed configured rules, segments, and journey decisions within the preview.
Small setup, dormant by default.
Integrate the preview
Engineering integrates the Sensors preview so eligible localized strings can be observed at runtime.
Capture consent
Signal collection only runs where the user's consent state allows it, so consent capture has to be in place first.
Enable a string
An authorised admin switches a specific string from dormant to active.
Use the signal
The resulting signal becomes a condition in an audience segment, a journey trigger, or a campaign rule.
Where a dead screen wakes up.
Beneficiary screen signals
A bank enables the sensor on the add-beneficiary screen's strings and collects view and interaction signals for each one.
Finding the dead screen
A team suspects a settings screen is unused but has no event for it.
Signals for a new label
A marketplace renames a menu item and wants to know whether anyone reaches it.
What teams ask before enabling one.
Are Sensors available to all customers?
No. Sensors are in preview behind a beta flag and are not generally available.
Does enabling a sensor require an app release?
Not after the eligible localised string and preview instrumentation have been integrated. The initial integration may still require engineering and an app release.
Can Sensors replace an event specification?
They can reduce the need to add certain observation events, but they do not replace every product event, data model, consent process, or analytics requirement.
Feeds Audiences and Journeys.
Journeys
Preview sensor signals can act as inputs for journey entry rules, branches, and recovery flows.
Sensors is one of eight.
Production integration today uses the REST API. Native SDKs for React Native, iOS, Android and Web are in preview and are not generally available. The @contentflow/cli package is not published yet.