Capture

Collection & panel

Behavix collection runs inside your own mobile apps and browser extensions — so the panel stays yours, and the consent screen carries your brand.

The platforms we support

Collection runs natively on both mobile operating systems and inside every major desktop browser — a journey that starts on a phone and ends on a laptop stays one journey.

Android

8 and above

iOS

16.7 and above

Chrome

88 and above

Edge

88 and above

Brave

1.44 and above

Firefox

109 and above

Ethical collection

Collected with explicit user consent and a clear audit trail

A member opts in before anything is captured — in plain language, specific to behavioral collection, and revocable at any time. The SDK enforces that rather than documenting it: the collection surface stays inert until a consent record exists, and stops the moment it is withdrawn.

It is also what gets you through app-store review — we work closely with your team, on top of the per-store submission guidance the SDK ships. We have been through those review processes with our own apps and with multiple partners across the globe.

Submission guidance for

  • Google Play
  • Apple App Store
  • Chrome Web Store
  • Firefox Add-ons
  • Microsoft Edge Add-ons

The panel stays yours

Behavix is the collection and processing layer, not the brand your members join. Nothing in the integration puts us between you and the people who opted in.

Your identifiers

Pass your own user identifier and the data comes back keyed to it, so it joins your existing records without a matching exercise.

Your branding

Design your own screens or take ours white-label — members see your program, within your brand guidelines and in their own language.

Your users

You stay in control of panel management and composition, member communications and store submissions — Behavix is the collection layer underneath, not a party your panel deals with.

What the collection produces

Whichever surface the data was captured on, it arrives as the same set of feeds against the same taxonomy — so an Android panel and a browser panel are one dataset rather than two integrations to reconcile.

  • App sessions

    Session-level mobile app usage across Android and iOS — which apps, for how long, and in what context.

    app_session u-3f91…c7a2 com.instagram.android 11m24s

  • Clickstream

    Page-level web browsing, with duration, domain categorization and company mapping.

    page_view u-7b42…0fd1 bbc.co.uk/news 2m18s

  • Search

    Search terms from the browser and from inside mobile apps, including AI search tools.

    search_query u-8ad0…1b47 "running shoes" in-app

  • AI conversations

    How members use on-device AI assistants: prompts and topics, with sentiment and brand mentions per turn — never private message content.

    ai_turn u-d80c…55aa travel positive 2 brands

  • E-commerce

    Shopping at the major retailers: search, product views, add to cart, checkout and purchase.

    add_to_cart u-7b42…0fd1 amazon 2 items

  • Media consumption

    Viewing sessions across streaming services — what was watched, on which platform, and how much of it.

    watch_time u-d80c…55aa youtube 18m40s/24m10s

  • Ad impressions

    Ad exposure across the major social and content platforms, with advertiser and creative detail.

    ad_impression u-3f91…c7a2 instagram T-Mobile

  • Audience feed

    Aggregated profiles, engagement and activity tables, for segmentation rather than raw events.

    users u-c215…9e30 profile refreshed daily

See how signals become events →

Ready to look at the integration itself?

Setup guides, platform requirements, consent APIs and the store-by-store submission guidance all live in the partner portal. Request access and we’ll get your team set up.

Not ready to commit engineering time? Pilot first on the Behavix app and browser extension — no integration at all, and enough to watch real feeds arrive keyed to your own identifiers before anyone writes code.