UserCurrent
Get started

Product

One profile per user. Two products on one core.

What a person does on your website and in your app lands on one profile. Growth and marketing teams and product and engineering teams work from it, each in the product built for them.

Get startedFor developers
The platform, its core and its two products

UserCurrent Web

web

Growth and marketing

  • Site experiences and slots
  • Acquisition analytics
  • Outbound and journeys
  • Web and content experiments
  • AI-generated variants

UserCurrent App

app

Product and engineering

  • Feature catalog
  • Feature flags
  • Product experiments
  • Product analytics views
  • In-app messages

Shared core

one project

One SDK per platform, one profile per user. No end-user screens except admin.

  • Clients and SDKs
  • Event stream
  • Identity graph
  • Profile store
  • Segments
  • Decision engine
  • Experiment engine and statistics
  • Analytics store
  • Autonomy and guardrails
  • Config as code and agent surface
  • Privacy and admin

One profile per user

The profile is the unit everything reads

Web, server and Astro integrations share one identity graph. When an anonymous visitor signs in, their history joins the known user in realtime, so the next decision uses everything the user has done.

One profile, events from the website and the appExample data

user u_4821 Trial, Acme Studio

  1. Oct 24, 09:12webpricing_page_viewedutm_source: newsletter
  2. Oct 24, 09:14webcta_clickedlabel: Start trial
  3. Oct 24, 09:16appsigned_upmethod: google
  4. Oct 24, 09:16profileidentifyanonymous visitor joined user u_4821
  5. Oct 26, 15:40appdocument_createdkind: note
  6. Oct 28, 11:05webpricing_page_viewedutm_source: none
  7. Oct 28, 11:09appshare_dialog_opened

  • Traits

    Set, set once and unset from an SDK, your server or the API.

    Increment and computed traits coming

  • Behavior over time

    Counts for each event in time buckets, plus first and last seen, over your plan's behavioral window.

  • Segments and experiments

    Current segment memberships and experiment assignments, so a decision reads them without a lookup.

  • Accounts

    A user can belong to several accounts, and events carry the active one. Account traits can target a decision.

  • Consent

    The visitor's consent choices, which narrow what is stored and what a decision may use.

  • Recent decisions and why

    Each decision is logged with its reason, so you can ask why a user saw what they saw.

Capability map

Eighteen capabilities in five groups

Each capability is owned by the shared core or by one product, or shared between the two products. Where part of one is not built, the card says so.

core Shared coreweb UserCurrent Webapp UserCurrent App

Collect

Get events in and decisions out.

  • Clients and SDKs

    core

    Web, server and Astro integrations, an EmDash plugin and OpenFeature providers, with one identity model.

    ComingiOS, Android, React Native and Electron SDKs

  • Tracking

    core

    Events under a typed tracking plan that agents keep in sync with the code, with sessions, UTM and referrer context and a visitor class on every event.

  • Features and modules

    app

    A feature catalog tied to flags, with adoption, frequency and retention for each feature and module.

Know

One person, one profile.

  • Identity

    core

    Anonymous visitors merge into the known user on identify, across devices. Accounts group users for B2B.

  • Profiles

    core

    Traits, behavior aggregates, segment memberships, experiment assignments, consent and recent decisions, read by every decision.

  • Segments

    core

    Behavioral and attribute segments that update on every event, and when time passes.

Act

Decide what each user gets.

  • Decisions

    core

    Rules, percentage splits, experiment arms and bandit selection, each logged with the reason.

  • Experiences and slots

    webapp

    Slots declared in code; variants, targeting and schedule edited in the console or in config.

  • Flags

    app

    Boolean, multivariate and JSON flags with percentage and behavioral targeting.

  • Experiments

    webapp

    A/B/n tests on flags and experiences, with sequential statistics and guardrails.

  • Outbound and journeys

    web

    Email, mobile push and signed webhooks, in multi-step journeys triggered by behavior.

    ComingPush tokens from native apps

Understand

Analytics on the same events.

  • Analytics

    webapp

    Trends, funnels, paths, retention, acquisition and behavior over time.

  • Dashboards

    core

    Tiles for saved insights and a live counter, defined in the console or in config, with share links.

    ComingHosted SQL tiles

Operate

Set the limits, keep the data safe.

  • AI hooks

    core

    Asynchronous AI decisions and drafted variants, an in-product analyst and agent access over MCP.

  • Autonomy and guardrails

    core

    Autonomy levels, experimentation budgets, an approval queue, kill switches and an audit trail.

  • Config as code and agent surface

    core

    A typed config file in your repo, a CLI, an MCP server and agent skills.

  • Privacy and data governance

    core

    Consent, PII classes, deletion, export, residency and a written data-use promise.

    ComingExport and residency are partly built; the promise is published at launch

  • Admin, access and billing

    core

    Organizations, roles, invitations and usage.

    ComingBilling

How the two products split it

How the two products split the modules

The core has no end-user screens except admin. Everything with its own screens belongs to a product, written for one buyer.

For growth and marketing

UserCurrent Web

Personalize the site, run web experiments and trigger journeys in realtime, with no CMS migration.

About UserCurrent Web

For product and engineering

UserCurrent App

Flags, experiments and product analytics on one profile, set up from the repo by your agent.

About UserCurrent App

  • One project, two products

    A customer who uses both turns on the second in the same project. There is no data copy, no second SDK and no identity stitching.

    Per-product entitlements coming

  • Shared objects are shared

    Segments, profiles, experiments, dashboards and the decision log are visible to both products. A segment built for the app can target a website experience, and the reverse.

  • One SDK per platform

    Each platform keeps one SDK for both products. A site that only needs slots loads only the parts it uses.

  • Messages

    In-app messages have a light surface in App: banner, modal, tooltip, inline card and a one-question survey. Campaign workflows belong to Web.

  • Experiments

    One experiment engine. Product rollout setup is in App, and content and web setup is in Web.

  • Reporting

    Basic referrer and UTM reporting is in App. Campaign operations are in Web.

Today the console shows every module in one navigation. Separate product navigation and a product switcher come with per-product entitlements.

Autonomy, AI and privacy

You set the limits

People set the goals, budgets and approvals. The platform may experiment and learn on its own inside them.

  • Autonomy you set limits on

    Each experience and action has a level: observe, recommend, prepare for approval, or act within budget. A budget caps traffic share, users exposed and time. The platform can reallocate traffic among approved variants and roll back when a guardrail metric regresses. When an agent starts an experiment or ships a winner, the change goes to the approval queue for a person.

  • AI that stays out of the render path

    An AI hook runs after an event and writes its result to the profile, so a page never waits on a model. AI-drafted variants are held for approval, and anything AI generated carries the AI label.

    AI

  • A data-use promise

    Customer data is never used for advertising or to train shared models. Consent, deletion by user, and masking of personal data in agent answers are part of the product.

    Published at launch

Start with one product

Both products run on the same project, so you can add the other later without a data copy.

Get startedRead the docs
Why this button?

It is this page's own suggestion for now. As you read, this site keeps a small profile of who each page is for and what it is about, in your browser, and picks this button from it. Nothing is sent.

See your vector on the live demo