Sync contacts to your systems
Get participants and what they did in OmniLab into your CRM, CDP, or customer database.
A sign-up in a campaign can become a contact in your CRM without anyone exporting a spreadsheet.
Choose 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 each event. See About webhooks.
What you can send
Participation, rewards won and redeemed, bookings and, if your plan includes Smart Links, Smart Link activity all raise events you can subscribe to. The full list is in the webhook event reference.
Subscribe only to what the receiving system uses. A CRM that only needs new contacts doesn't need every page visit, and filtering at the subscription is cheaper than filtering after delivery.
Match to an existing contact
To update someone who's already in your CRM, you need a value that identifies them in both places. If participants sign in with an account you manage, you already have it: it's the identifier you pass in as fci. See Pass a known customer into an experience.
Without it, matching falls back to the email address, which is unreliable for anyone with more than one.
Keep each contact's consent
A contact created from a campaign carries the opt-in the participant gave in that campaign. Make sure the receiving system stores it, rather than treating every arriving contact as marketable. See About opt-in.
For your developer
- Keep the receiver separate from the CRM writes, so a slow CRM doesn't cause failed deliveries.
- Verify the signature before you process an event.
- Store each delivery ID and skip repeats. Deliveries are retried, so the same event can arrive twice, and preventing a duplicate write is up to you.
- Subscribe only to the event types the destination uses.