Setup

Note

API Users
Global users, which should be used for the API, should not be used to login into the Evalanche UI!
If a user opens a customer, when logging out, all API requests will use this customer and will ignore the used customer_id.

E-mail validation

Documentation

E-mail are validated, to prevent to add invalid e-mails to a pool.

Following validation checks are done:

e-mail syntax is correct
e-mail is not on the blacklist
Domain has a valid A record (test)
Domain has a valid MX record (test)

Multi select fields

Multi select values are serialized into a single string, separating each option ID with a pipe (|) and starting and ending with a pipe (|).

Example:

|1233|1234|1235|

Single select

User created single select fields behave exactly like multi select fields.

The option ID is encapsulated with the pipe (|).

Example:

|1233|

Date & Time

Evalanche uses the format YYYY-mm-dd HH:ii

Depending on the use case this needs to be converted to a ISO format.

Fields

All fields are dynamically read from Evalanche. New pool fields can be easily added to an adapter.

The profile also returns the unique profile ID (SID).

Different identifier than PROFILEID

A different identifier can be used while configuring a plan, there are some implications:

the identifier field values must be unique to identify exactly one profile across the evalanche pool
identifier value is not created by evalanche API and must be mapped
SID can not be used as identifier

Real Change Date

The adapter provides a virtual field REAL_CHANGE_DATE, which is not available through the Evalanche API.

This field contains the lastest change date from CHANGE_DATE and UNSUBSCRIBE_DATE.

It can be used to fetch unsubscription and profile updates in a single plan.

Permission

To use mass transfer the “Profile Import” permission is needed!

https://help.evalanche.cloud/hc/de/articles/360042265151-SOAP-Profile