Sync contacts to your systems
Get participants and what they did in OmniLab into your CRM, CDP, or customer database.
Get the people who take part, and what they did, into the systems your teams already work in — so a sign-up in a campaign becomes a contact in your CRM without anyone exporting a spreadsheet.
How data leaves OmniLab
| Method | Good for | Timing |
|---|---|---|
| Webhooks | Keeping another system continuously up to date | As it happens |
| Exports | One-off analysis, or a hand-off to a team that works in spreadsheets | On demand |
Most contact sync uses webhooks: OmniLab notifies your systems as participants act, and your side decides what to do with it. See About webhooks.
What you can send onward
Participation, rewards won and redeemed, bookings, and Smart Link activity all raise events you can subscribe to. Subscribe only to what the receiving system actually uses — a CRM that only cares about new contacts does not need every page visit, and filtering at the subscription is cheaper than filtering after delivery.
The full list is in the webhook event reference.
For your developer
Use webhooks when another system should react to activity without polling for it.
Habits that keep this reliable:
- Separate the OmniLab receiver from the downstream write logic, so a slow CRM does not cause delivery failures.
- Verify the signature before the event enters your queue.
- Keep the receiver idempotent by storing the delivery id — retries are normal and a duplicate write is your problem to prevent, not OmniLab's.
- Subscribe only to the event types the destination actually uses.
Matching to an existing contact
If the same person already exists in your CRM, you need a value that identifies them in both places. When participants sign in with an account you manage, that value already exists — it is the same identifier you pass in as fci. See Pass a known customer into an experience.
Without it, matching falls back to email address, which is unreliable for anyone with more than one.
Decide what happens to consent
A contact created from a campaign carries whatever opt-in the participant gave in that campaign. Make sure the system receiving it stores that, rather than assuming everything arriving is marketable. See About opt-in.