Developer Quickstart

Pick where your events come from. Browsing (page views, products viewed, carts) comes from the website. Orders, sign-ups and history usually come from your server. Most stores use both.

Website
Server

Option 1: let the setup agent install it. In your project folder, run:

npx @revbridge/setup

Confirm the project

The CLI detects Next.js (App Router or Pages Router), React (Vite or Create React App) or a server-rendered HTML site. Nothing changes until you confirm.

Your browser opens the RevBridge sign-in. Your organization’s publishable key comes from your account, so there is nothing to copy.

Review the changes

The agent installs @revbridge/web-sdk, starts it once, adds identify on login and reset on logout, and adds commerce events only if the site sells something. It then runs your typecheck and build and shows a report. At the end it offers to put the changes on a revbridge/web-sdk branch. Nothing is committed without your yes.

You need Node.js 22 or newer and an interactive terminal. A run usually takes 3 to 10 minutes. Run npx @revbridge/setup --detect-only to see what it detects without changing anything.Option 2: paste the snippet. Copy the script tag from Web SDK → Install into the <head> of every page, with your publishable key from Settings → API Keys.Then open your site in a browser. Each page load sends a page_view.

Create a secret key

In Settings → API Keys, click New API key, name it and click Create. Copy the rbak_ key: it is shown once. See Authentication.

Send one event

export REVBRIDGE_API_KEY="rbak_YOUR_SECRET_KEY"

curl -i -X POST https://api.revbridge.ai/ingest/events \
  -H "Authorization: Bearer $REVBRIDGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "users": [
      {
        "identifiers": {
          "email": "you@yourcompany.com",
          "first_name": "Your name"
        },
        "events": [
          { "event_name": "quickstart_test", "timestamp": "2026-10-27T12:00:00Z" }
        ]
      }
    ]
  }'

Use your own email and today’s date, so the test lands on your own profile.

Read the response

Status 202 with "users_accepted": 1 means it worked. If the response has a warnings list, a field was dropped. A 401 HTML page means the key is wrong. See Errors.

Check that it arrived

In the app, open Data → Events.
Under Received events, find your event (page_view or quickstart_test) and open it to see its properties and how the person was identified.
Open People and search for the email you sent to see the profile.

More on reading that screen in Check your events.

There is no test environment for customer keys. Test with your own contact, as above, before you connect real traffic or import history.

Next steps

Ingesting Events

The full request and response, and how to import history.

Event Types

The standard commerce and page events.

User Identification

Identifiers, merges, profile fields and consent.

Best Practices

The mistakes that pass validation and break your numbers.

Getting Started

Events API

Web SDK

Reference

Check that it arrived

Next steps

Ingesting Events

Event Types

User Identification

Best Practices

​Check that it arrived

​Next steps

Ingesting Events

Event Types

User Identification

Best Practices

Check that it arrived

Next steps