Platform Agnostic
Any system that can send an HTTP POST can integrate with Scout. CRM, ERP, POS, mobile app, or custom software, it does not matter.
Scout Integration
Webhook
Integration
Collect server-side events from CRM, ERP, POS, and mobile apps with Scout Webhook API. Route data to Google Ads, Meta, and Klaviyo in real time.
What is a Webhook?
A webhook is an HTTP POST mechanism that sends data from server to server. Without loading a JavaScript SDK in the browser, you can send events directly to Scout from your CRM, ERP, POS, or any backend system.
Endpoint: POST https://scout.dnomia.app/v1/webhook/{source}
Scout's advantage: Server-side webhook data is automatically merged with client-side SDK data. This hybrid approach creates the richest possible data set to send to destination platforms (Google Ads, Meta CAPI, Klaviyo).
SDK vs Webhook Comparison
Comparison of data collection methods and Scout's hybrid approach.
| Features | SDK (Client-side) | Webhook (Server-side) | Scout Hybrid |
|---|---|---|---|
| Setup | JavaScript snippet | HTTP POST integration | Both |
| Data Source | Browser | Server | Browser + Server |
| UTM/Session Data | Automatic | None | Auto-merged |
| Order Data | Limited | Full detail | Full detail + enriched |
| Ad Blocker Resistance | Low | 100% | Hybrid: highest |
| Profile Enrichment | UTM, referrer, session | Email, phone | Full profile |
| Cost | Free snippet | Developer required | Single solution |
Scout merges client-side SDK data (UTM parameters, referrer, session info, browser cookies) with server-side webhook data (order details, customer info, CRM data). This hybrid approach creates the richest possible data set for ad platforms and automation tools.
What We Offer
Real-time Processing
Events sent via webhook are processed instantly. Orders, payments, customer updates, and other events are delivered to destination platforms within seconds.
Data Enrichment
Server-side webhook data is automatically merged with client-side SDK data (UTM, session, browser). Full profiles are sent to destinations.
Multi-destination Routing
Route data to Google Ads, Meta CAPI, Klaviyo, and other destinations from a single webhook call. No separate integration needed for each destination.
Use Cases
Any system that can send an HTTP POST can integrate with Scout Webhook API.
CRM
Customer data
ERP
Order data
POS
In-store sales
Mobile App
App events
Custom Source
Via HTTP POST
How It Works?
1
Set up your endpoint
Create your webhook source from the Dnomia Dashboard. A unique endpoint URL is assigned for each source.
2
Configure authentication
Generate an API key and add it to the Authorization header of your webhook requests. Secure communication via Bearer token.
3
Send your payload
Send an HTTP POST request in Scout's expected JSON format. Prepare a payload containing event type, customer info, and order details.
4
Route to destinations
Define which destinations receive the incoming data. Create routing rules for destinations like Google Ads, Meta CAPI, and Klaviyo.
Frequently asked
questions
What is the webhook endpoint URL?
A unique endpoint is created for each source. Format: POST https://scout.dnomia.app/v1/webhook/{source}. The source parameter is the source name you created in the Dnomia Dashboard.
How does authentication work?
You generate an API key from the Dnomia Dashboard. Each webhook request must include an Authorization: Bearer {api_key} header. Requests without a key or with an invalid key are rejected.
Are there rate limits?
Standard plans accept 100 requests per second, enterprise plans accept 1000 requests per second. When rate limits are exceeded, a 429 response code is returned with a Retry-After header indicating the wait time.
Which event types are supported?
Purchase, AddToCart, ViewContent, InitiateCheckout, Lead, CompleteRegistration, and custom event types are supported. For custom events, you can set the event_name field to anything you need.
What is the difference between SDK and webhook?
SDK runs in the browser and collects UTM, session, and browser data. Webhook runs server-side and sends order, payment, and CRM data. Scout merges both to create complete profiles.
What happens when errors occur?
Failed requests are automatically retried. After 3 failed attempts, they are moved to a dead letter queue. You can view failed requests in the Dashboard and manually resend them.
Is there a test mode?
Yes. You can activate test mode from the Dashboard. Events sent in test mode are not delivered to destinations, but payload validation and enrichment processes are applied. You can review the results in the Dashboard.
Frequently searched
questions about webhooks
How to set up webhook integration?
What is server-side tracking?
How to send CRM data to ad platforms?
ERP order data integration
POS in-store sales tracking
How to set up webhook integration?
What is server-side tracking?
How to send CRM data to ad platforms?
ERP order data integration
POS in-store sales tracking
How to set up webhook integration?
What is server-side tracking?
How to send CRM data to ad platforms?
ERP order data integration
POS in-store sales tracking
How to set up webhook integration?
What is server-side tracking?
How to send CRM data to ad platforms?
ERP order data integration
POS in-store sales tracking
What is the difference between webhook and SDK?
Server-side conversion tracking
How to achieve real-time data flow?
What is the difference between webhook and SDK?
Server-side conversion tracking
How to achieve real-time data flow?
What is the difference between webhook and SDK?
Server-side conversion tracking
How to achieve real-time data flow?
What is the difference between webhook and SDK?
Server-side conversion tracking
How to achieve real-time data flow?