Attach destinations to an experience and send a test lead

Choose when an experience sends, review its fields, save, and prove the destination works.

Experiences
Written forExperience managers

A team-level connection stays idle until it is attached to an experience. The experience controls the send timing, consent rule, and any extra field mappings for that destination.

Steps

  1. 1Connect the destination from Integrations before opening the experience.
  2. 2Open the experience and select the Destinations tab.
  3. 3Choose the active destination from the list.
  4. 4Select Details submitted to send when guest details arrive, Media ready to send when the result is complete, or both when the destination needs both moments.
  5. 5Choose the consent policy. Keep Marketing consented unless your team has approved and confirmed the All leads exception.
  6. 6Review the automatic name, email, phone, and consent mappings. Add an advanced mapping only when the receiving service needs another field.
  7. 7Save the destination settings.
  8. 8Select Send test lead. A test will ask you to save first if the settings changed after the last save.
  9. 9Confirm the test panel reports success, then check the test record in the destination.
  10. 10Complete one real guest-flow test and use Integrations > Activity to confirm that live delivery is Delivered.

What to know

  • Trigger names describe two different moments.Details submitted can arrive before generated media is ready. Media ready waits for the completed submission and is the better choice when the destination needs result links.
  • Automatic fields need no extra mapping.Use advanced mappings only for a known destination property. A wrong property name can turn a test into Action needed.
  • Test leads stay out of Activity.The test button sends directly and reports its result on the Destinations tab. Complete a real guest-flow test when you need to prove the live Activity record too.
  • Pause and detach are different.Pause keeps the saved setup but stops sends for future captures from that attachment. Detach removes the destination from the experience.

Tips

  • Use a unique email address in every end-to-end test so the destination result is easy to find.
  • Save before testing and test again after any trigger, consent, or mapping change.

Related articles

Still need help?

Tell us the experience name and what you were trying to do, and our team will pick it up from there.

Email ops@thesnapbar.com