/
Adestra - Contact Import Destination

Adestra - Contact Import Destination

Overview

This connector sends contact data to the Adestra data table, allowing you to easily activate your first-party data on multiple-channel marketing to engage your audience.

Pre-requisites for using Adestra in Wondaris

You will need to request whitelisting of the Wondaris IP addresses within your Adestra account

Please contact your Wondaris Account Manager or support@wondaris.com for further information to support you in making this request to your Adestra client support team.

Instruction

  1. Go to Create Destination

image-20240918-064732.png

  1. Select The Adestra destination-type card

  2. Complete the Adestra Destination Configuration screen


    adestra guide 1.png

     

  3. Connection Name: Name your connection. This is required.

  4. Description: Optionally add a description

  5. API Token: Insert your API token. You can find it on your user profile → Manage API tokens. This is required.

  6. Workspace: After filling in the API token, the associated workplace list will be loaded. Select one workplace. This is required.

  7. Data List: The associated data list will be loaded after selecting the workplace. Select one data list. This is required.

  8. Data Table: The associated data table will be loaded after selecting the Data List. Select one table. This is required.

  9. Data Source ID: If you want to push data to this source ID, you can optionally add one.

  10. Configure default settings:

    1. Deduplication type: You are required to select one type to determine how you want to proceed with the imported data to Adestra

      1. Skip New Records: Duplicate records are ignored

      2. Overwrite Old Records: Duplicate records are overwritten with new data

      3. None: Duplicate records are imported. This will lead to duplicate records in your core table.

    2. Deduplication Field: This defines the core table column containing the data you wish to perform deduplication. This would typically be the column containing the email address. The column name will be one of the fields in your core table and must correspond to one of the keys in your field_map. If not supplied, the default value of email will be used.

    3. Notify User: Specifies the ID or email address of the user who should be sent a notification email when the import is complete. If omitted, this defaults to the current API user. If you specify an email address, it must be associated with a MessageFocus user.

  11. Allow override: Choose whether or not another user can override these settings when activating. 

  12. Click Create to save. You can now use this destination in activations.