Integrations
Send leads to a connected destination
Attach a connected destination to an experience, choose when to send and who may be sent, then test it.
On this page
Connect a destination at the team level first. Then attach it in each experience that should send data. You need integrations enabled and permission to edit the experience.
Attach the destination and choose timing
Open the experience and select the Destinations tab. Under Destination, choose the connected account.
Under Send when, choose the guest moments that create a delivery: After details are submitted, After media is ready, or both. Details arrive before processing finishes; media ready carries the finished result links.
Choose which guests may be sent
Guests who agreed to marketing is the default. Choose it when the destination is used for marketing or follow-up that depends on guest permission.
All guests with contact details sends every guest who left an email address, even when marketing consent was not collected; managed destinations need an email, so a phone-only lead is skipped. Choose it only when your organization has a lawful basis to send every captured lead and your guest notice supports that use.
If you choose all guests, read the warning and check the confirmation. It records that your organization accepts responsibility for the broader use, and no API key can bypass it.
Save and test
Email, first name, last name, and phone map automatically. A destination that accepts extra properties shows a Data mapping section; open it only when you need one. Slack ignores mappings, so a Slack destination has no Data mapping section.
Select Save destination, then Send test lead, both beside the Destination heading. If you change any setting, save again before testing.
The test sends a sample guest named Test Lead with the address test@snapbar.com to the real destination. For Slack it lands in the connected channel as a normal New lead at message. Check the result in the test panel and confirm the sample guest arrived.
Complete a real guest-flow test using the event consent choice, then look for Delivered in Integrations > Activity. A healthy destination shows it within seconds of the guest moment you chose. The test button alone does not create an Activity record.
Send leads captured before you attached
Open the More destination actions menu beside the Destination heading and select Send finalized leads to queue guests who completed the experience before the destination was attached. Snapbar shows how many are finalized, already sent, without consent, or without contact details before you confirm.
Each click queues at most 500 finalized leads, and the preview counts stop at 500 as well. For a larger event, confirm, wait for the queued deliveries to finish, and select Send finalized leads again until the preview reports nothing left to send.
Finalized leads follow the same consent rules as new activity, and a submission whose media-ready delivery already reached this destination is not queued again. A guest whose details went out earlier at submission time can still receive the media-ready message. Each request is recorded in the audit log with who confirmed it.
What to know
- Pause and remove are different.Pause destination keeps the saved setup and stops sends for future captures. Remove destination detaches it from the experience. Existing Activity history stays either way, and saving a paused destination turns it back on.
- Consent is checked twice.Snapbar checks consent when the lead is queued and again just before sending. A guest without marketing consent under the default policy appears in Activity as Skipped with reason.
- The destination still has responsibilities.Consent details travel with the lead when available, but your organization remains responsible for how the receiving service stores and uses the data.
Tips
- Save before testing and test again after any trigger, consent, or mapping change.
- Write the approved consent policy into the event launch plan.
- Do not replay a lead that was skipped because consent was absent.