Skip to content

Product and engineering

How Usivity integrates with your product

One script tag and a signed user identity. Your team decides what Usivity can reach; Usivity runs the rest.

Product guide · 4 min read

What Usivity never touches

Your product code is not part of the integration. Usivity works in its own layer, inside the zones you define. It never changes your application code, your database, or any system you have not connected it to.

Your test coverage, CI pipeline and deploy process stay as they are.

Out of Usivity’s reach

  • Your backend code and database
  • Your app’s navigation or routing
  • Existing event handlers and application logic
  • User authentication and access control
  • Any part of a page outside the zones you define

From zero to live

The core integration is a few steps. There is no database change and no API to build; the only server work is signing each user’s identity.

  1. 1

    Add the script tag

    One tag in your product shell, typically your root layout or app wrapper. Your engineers add it the way they would add an analytics tag. No build step.

  2. 2

    Sign each user on your server

    Your server signs the user’s ID and email with your HMAC secret and renders them, with the signature, into the script tag. Company and role are optional extras. Unsigned or invalid users are rejected.

  3. 3

    Allowlist your domains

    In the Usivity dashboard, list the domains allowed to load your SDK. Exact origins and wildcard patterns both work.

  4. 4

    Define your zones

    Name the parts of your product Usivity may work in, each with a CSS selector. Everything outside them is untouched.

  5. 5

    Approve data sources (optional)

    If you want Usivity to pull in external data (a CRM field, a live metric, a customer attribute), register that API in the dashboard. Usivity cannot reach anything your team has not approved.

The exact attributes and the signing are covered in What teams can configure, with server examples on Security and architecture.

Who owns what

Your team controls the access model. Usivity manages the personalization layer. Neither crosses into the other’s territory.

Your team controls

  • Where Usivity runsOnly inside the zones you define: named CSS selectors for the parts of your product customers may personalize.
  • Which users get UsivityEach user is signed by your server, and the portal’s Access page sets who gets Usivity, whether they see the button, and whether they can make their own changes.
  • Which data sources are approvedEvery external API must be registered by your team in the dashboard. Nothing is discovered or connected automatically.
  • Which domains can load itYour domain allowlist. Requests from any other origin are rejected.

Usivity manages

  • The personalization layerPersonalizations change presentation only, inside your zones. They never change your application code, and anyone can restore the standard view in one click.
  • Saving and syncing preferencesWhen a user personalizes their view, Usivity saves it, so it comes back across sessions and devices with no work from your team.
  • Keeping changes within boundsUsivity accepts only sanctioned, bounded changes within your zones, and calls only the APIs you have registered.
  • Updates to UsivityImprovements reach the Usivity layer automatically. Your product does not need to be updated, rebuilt or redeployed.

Your customers get a product that fits. Your roadmap stays yours.

In ten minutes we’ll show you what your customers can change on their own, and what your team never has to build.

Book a 10-minute demo

We reply within one business day.