What Ovante sends, and what stays
Registrations, check-ins, orders, refunds, gifts and the contact changes they cause go out. Your own edits, merges and imports stay in Ovante, and so do requests until you approve them.
Your integrations hear what your guests and buyers do: registrations, check-ins, orders, refunds and gifts, and the contact changes those cause. What you do to tidy your own list (editing a contact by hand, merging two contacts, importing a spreadsheet) stays in Ovante.
What goes out
- A registration, once the ticket has a holder.
- A check-in, and a check-in undone.
- A ticket set to Not going.
- An order, once, when it's paid or free.
- A refund, once per order.
- A gift, including sponsorships, journal ads and the part of a ticket's price above its value.
- A new contact, or a change to one, when a registration caused it.
What stays in Ovante
| You | Why it stays |
|---|---|
| Edit a contact on the People page | Your edit is a correction to your own list. It also locks the field against later automatic changes. |
| Merge two contacts, or undo a merge | Tidying your list isn't news to your CRM |
| Import contacts from a spreadsheet | Same reason |
| Receive a request | Nothing about a request goes out until you approve it. Declined requests never go out. |
| Sell a ticket nobody has named | It belongs to the buyer's order until someone names it. Then it goes out as a new registration. |
A member who joins from your org page, or edits their own profile, also stays in Ovante. Their registrations still go out like anyone's.
- When
- You edit, merge or import contacts
- Then
- Nothing goes to your CRM or webhooks. Only contact changes that a registration makes are sent.
- When
- A request is waiting
- Then
- Your contacts, CRMs and webhooks hear nothing about it. When you approve it, they get it as a new registration and a completed order.
- When
- You approve a request
- Then
- Your integrations hear about it then, as a new registration for each named ticket and one completed order, as if it had been bought that moment.
- When
- A guest ticket has no name and no email
- Then
- It stays on the buyer's order as an unnamed ticket, carrying the buyer's name, email and phone so the confirmation and the door have something. It makes no contact and sends nothing to integrations until you name it.
Which events
Every event syncs. There's no switch on screen to keep one event out, and no setting to sync published events only. If History says an event is marked to stay out of your CRM, it was switched off before that setting was removed. See Turn off CRM sync for one event.
What a webhook can leave out
A Zapier, Make or custom webhook connection has three more choices, under Privacy when you create or edit it:
- Only send contacts who opted into marketing holds back registrations, check-ins and contact events for anyone who hasn't opted in, or who has unsubscribed from your emails. Orders, refunds, gifts and Not going still go, so accounting automations keep working.
- Leave out phone numbers.
- Leave out custom field answers.