Omniconnect
Omniconnect lets you connect third-party platforms to Bloomreach using webhooks. You write a JavaScript transformation function to shape incoming webhook data into Bloomreach events and customer properties—no middleware or manual API calls required.
How it works
When an event happens in a third-party platform, that platform sends a webhook (an HTTP POST request) to Omniconnect. You provide a JavaScript function that transforms the incoming payload into a format Bloomreach understands. Bloomreach then processes the data as events or customer property updates.
With Omniconnect, you can:
- Receive webhooks directly in your Bloomreach project.
- Write JavaScript transformation functions to map incoming data to Bloomreach's data model.
- Control exactly what data reaches Bloomreach—customer properties and events.
- Monitor integration health and debug issues using built-in request logs.
Limits
Integrations and requests
Your workspace has 2 request limits.
| Limit | Description |
|---|---|
| Monthly inbound requests | The maximum number of inbound requests per month. Requests over this limit will still be processed, but Bloomreach may suspend integrations that consistently exceed it. |
| Processing rate | The maximum number of requests processed per minute (RPM). Sending more than this value will cause processing lags—data will eventually be processed, but not in real time. |
NoteYour monthly request limit and processing rate limit are visible on the usage dashboard Omniconnect gauge at workspace level. Project-level gauges don't show limits.
Bloomreach may suspend integrations that generate unusually high peak request rates. This protects platform stability for all users.
Profile updates
Omniconnect processes data in two steps: incoming requests count toward your Monthly inbound requests allowance. The customer updates and events that result from those requests count toward your Profile updates allowance.
Campaign events sent through Omniconnect also count toward Profile Updates, because event types excluded from Profile updates are only excluded when generated internally by Bloomreach.
Payload size
Each webhook payload must be under 1 MB (1,032,192 bytes). Larger payloads are rejected.
For best results, keep payloads under 500 KiB.
Historical data imports
Omniconnect isn't designed for bulk data loads. Don't use it to backfill large volumes of historical events. Use the Import feature instead.
Retry behavior
Omniconnect doesn't control whether failed webhooks are retried—that's up to your source platform. If your platform doesn't retry on failure, failed events are lost. Check your platform's webhook documentation to confirm how it handles retries and errors.
Ownership and support
You own your integrations and are responsible for:
- Writing and maintaining your transformation functions.
- The data your integration sends to Bloomreach.
- Ensuring your integration continues to work if the source platform changes its webhook format.
Contact Support for platform-level issues. For example, if a button isn't working or an integration isn't visible. However, Support can't help build or debug your specific transformation functions.
Data privacy
You are the data controller for all data sent to or received from third-party platforms through Omniconnect.
This means:
- Only send what you need. Don't share full customer profiles when only a few attributes are required.
- Don't transmit prohibited data. This includes payment card numbers, biometric data, health information, and other sensitive categories.
- Vet your source platforms. Before connecting a platform, review its data practices to ensure they meet your compliance requirements.
For more details, see Data minimization and Managing PII.
Updated 1 day ago