Evalanche Integration

In this article, you'll learn how to connect meetergo with Evalanche to automatically transfer contact details from bookings into your Evalanche pool and trigger double opt-in emails. If you use Evalanche for marketing automation and want to grow your contact pool directly from your meetergo bookings, this integration is for you.

What you need before connecting

To set up the integration, you need a SOAP API user in Evalanche and a few configuration values from your Evalanche account:

• Evalanche URL – Your Evalanche instance URL, e.g. https://scnem.com or https://scnem3.com.
• Username – The username of an Evalanche SOAP API user.
• Password – The password for that API user.
• Pool ID – The numeric ID of the contact pool where new contacts should be created.
• Double opt-in email ID – The numeric ID of the email template that should be sent as the double opt-in confirmation email.

How to connect the integration

1. Open the integrations page Go to https://my.meetergo.com/integrations.

2. Find Evalanche Scroll to the Evalanche integration and click Connect.

3. Enter your connection details Fill in the Evalanche URL, username, password, Pool ID and double opt-in email ID.

4. Save the connection meetergo validates the credentials against the Evalanche API. If everything is correct, the connection is saved and ready to use.

Consent fields on your booking forms

When you connect Evalanche, meetergo automatically creates two consent checkboxes in your data fields and adds them to your booking forms:

• Datenübertragung (ev_datenuebertragung) – Required tier 1 consent. Without this checkbox being ticked, the contact is not transferred to Evalanche.
• Werbeeinwilligung (ev_werbeeinwilligung) – Optional tier 2 marketing consent. If the attendee ticks this box, the Evalanche double opt-in email is sent automatically after booking.

You can rename these fields, translate their labels and adjust their position in your booking forms like any other data field. The internal field names (ev_datenuebertragung, ev_werbeeinwilligung) must not be changed.

What gets synced

When an attendee books a meeting and has ticked the data transfer checkbox, the following information is sent to your Evalanche pool:

• Email address – Used to identify and deduplicate the contact in Evalanche.
• First name and Last name – Mapped to the standard Evalanche name fields.
• Phone number – If provided, the country prefix (first 3 characters) is stored in PHONEPREFIX and the remaining digits in PHONENUMBER.
• Custom field values – Any data field you have mapped to an Evalanche field ID (see below).

If the attendee also ticked the marketing consent checkbox, the configured double opt-in email is triggered for the contact.

Sync custom data fields

You can map any of your meetergo data fields to a corresponding field in Evalanche:

1. Go to https://my.meetergo.com/data-fields.
2. Open the data field you want to sync.
3. In the field settings, enter the Evalanche Field ID that matches your Evalanche pool attribute.
4. Save the changes.

From now on, the value entered into this field during a booking is transferred to the matching Evalanche attribute.

How contact sync works

• If the contact doesn't exist in Evalanche, a new contact is created in the configured pool.
• If the contact already exists (matched by email), the existing record is updated with the latest booking data.
• New contacts that also gave marketing consent receive the configured double opt-in email automatically.
• The transfer happens immediately after the booking is confirmed.

---

FAQ

Why isn't my contact appearing in Evalanche after a booking?

The most common reason is that the attendee did not tick the Datenübertragung consent checkbox – without this, meetergo will not send the contact to Evalanche. Also make sure the data field is present on the booking form you are testing.

Where do I find my Pool ID and email template ID?

Both IDs are visible in the Evalanche backend. The Pool ID is shown in the URL or settings of your contact pool, and email template IDs are visible in the mailing list overview.

Can I have multiple Evalanche connections?

Each user can have one Evalanche connection. If multiple hosts on a meeting type have Evalanche connected, meetergo uses the first available connection of the meeting's hosts to push the contact.

What happens if the SOAP API user's password changes?

The integration will stop syncing contacts because the credentials are no longer valid. Reconnect Evalanche on https://my.meetergo.com/integrations with the new password.

Can I disconnect the integration later?

Yes. You can disconnect Evalanche anytime on https://my.meetergo.com/integrations. The two consent data fields (ev_datenuebertragung, ev_werbeeinwilligung) are removed together with the connection.