Mapping your Adestra-Salesforce Core Table, Fields, and Event Data

After authenticating your connection between Adestra and Salesforce, you will be taken to the Adestra Settings workflow. Here you will:

In addition to mapping your data, you will need to sync your campaigns in Salesforce to complete the integration.

If you are returning to map your core table and fields at a later time, you can get to the app configuration settings by:

  1. Logging in to Salesforce as an administrator.

  2. Locating the Adestra app (search for Adestra in the main menu).

  3. Going to Adestra Settings in the Adestra app.

Note: you may need to collaborate with the end user(s) of the app to complete this workflow.

Mapping your core table

On the Step 1: App Configuration screen:

  1. Press the Browse button next to the Core table field to open a list of available core tables.

  2. Locate and select the radio button for the core table to be linked with Salesforce.

  3. Press the Select button to confirm your table.

  4. If required, Configure event sync. Otherwise, press the Next button to go to field mapping.

Configuring Adestra-Salesforce event sync

If you wish to enable a daily sync of your Adestra event data into your Salesforce account:

  1. Check the “Enable daily sync of Adestra event data into Salesforce” checkbox.

    Note: you can return to the Adestra Settings workflow at any time to toggle the daily sync on/off. However, data will not retroactively sync so only toggle data off if you do not want to sync events from the off period, i.e. there will be a gap in your data if turned off.

  2. Press the Browse button next to the Event Types field to open a list of event types.

  3. Use the check boxes to select the event types to sync.

    Tip: consider the storage space of your Salesforce account when choosing how many event types to sync.

  4. Press the Select button to confirm your event selection.

  5. Press the Next button to go to field mapping.

Mapping fields

For all configurations, email is a mandatory field.

Note: you need to include the object type and the field, e.g. CampaignMember.status.

Tip: when mapping fields, the dropdowns for Adestra Fields only include the fields in your selected core table. If you need to map a data table field, this will need to be entered manually in the format TableID.FieldName, e.g. 1234.created_by.

Screen capture showing an example of the data table mapping as it appears within the app.

The app recognises valid data table entries and will notify you when you press the Submit button if you enter an invalid name for an Adestra field.

Note: If you wants to sync both leads and contacts then you will need to map email with CampaignMember.email.

On the Step 2: Field Mapping screen:

  1. Verify that your email fields for Salesforce and Adestra are correctly mapped.

    Use the dropdown menus to make changes, if required.

    Note: you can only map fields to which you have admin access.

    Caution: do not map compound fields, e.g. BillingAddress. Instead, use the fields inside the compound fields.

    Example: if BillingAddress is a compound field using Name, StreetName, and PostalCode, map the Name, StreetName, and PostalCode fields.

    Tip: if you cannot locate a field to be mapped, ensure they exist in the selected core table within Adestra. If not, you will need to create them in Adestra.

  2. If you are performing a daily event data sync from Adestra, the Salesforce contactid field is required.

    Use the dropdown menus to map this field to the corresponding field in your Adestra core table.

    Note: the Salesforce Contact ID must be mapped to a Core Table field rather than a Data Table for the sync to work.

  3. If you are sending lead profiles to Adestra, the Salesforce leadid field is also required.

    Use the dropdown menu to map this field to the corresponding field in your Adestra core table.

    Note: the Salesforce Lead ID must be mapped to a Core Table field rather than a Data Table for the sync to work.

  4. If you are not performing an event data sync or lead send, the associated fields will need to be removed from the mapping.

    Press the trashcan icon to remove a row from the mapping.

  5. If you wish to add additional rows, press the + New row button.

  6. Select the fields to map using the dropdown menus.

    Note: you cannot repurpose the default leadid or contactid fields if they are unused. They must be mapped accordingly or deleted.

  7. When you have mapped all the fields you wish to be mapped, press the Submit button.

If connection is successful, you will get a confirmation that your data is mapped.

If you encounter any error messages or issues, please contact your Customer Service Representative or adestra-support@uplandsoftware.com.

After mapping your data, you will need to sync your campaigns in Salesforce to complete the integration.