Skip to main content

​
What is the Events API?

The Events API is RevBridge AI’s data ingestion endpoint. It lets you send customer events — purchases, page views, sign-ups, and any custom action — along with user profile data directly from your application. Once ingested, this data powers:
  • Unified Customer Profiles — every event is linked to a customer identity, building a 360-degree view.
  • Dynamic Segments — audiences are automatically updated based on real-time behavioral data.
  • AI Campaigns — the optimization engine uses your event data to personalize messaging, timing, and channel selection.
┌─────────────┐       ┌──────────────┐       ┌──────────────────┐
│  Your App   │──────▶│  Events API  │──────▶│  RevBridge AI    │
│  (Backend)  │ POST  │  /ingest/    │       │  ┌─ Profiles     │
│             │       │  events      │       │  ├─ Segments     │
└─────────────┘       └──────────────┘       │  └─ Campaigns    │
                                             └──────────────────┘

​
Use cases

E-commerce

Track purchases, cart events, product views, and wishlist actions to drive personalized product recommendations and win-back campaigns.

Mobile Apps

Send in-app events like screen views, feature usage, and subscription changes to trigger behavior-based push notifications.

SaaS Platforms

Ingest sign-ups, feature adoption, and billing events to power onboarding sequences and churn prevention campaigns.

Omnichannel Retail

Unify online and offline events — POS transactions, loyalty actions, and website activity — into a single customer profile.

​
How it works

1

Authenticate

Include your API key and customer ID in every request. Set up authentication →
2

Send events

POST user events to the /ingest/events endpoint with user identifiers and event data. Learn the payload format →
3

Identify users

Attach at least one identifier (email, user ID, phone) so events are linked to the right customer profile. See identification rules →
4

RevBridge processes your data

Events are validated, linked to customer profiles, and made available across Segments, Campaigns, and Analytics — typically within seconds.

​
Next steps

Authentication

Generate API keys and authenticate your requests.

Ingesting Events

Full payload reference with code examples.

User Identification

How customer identity resolution works.

Event Types

Common event schemas and custom properties.