Import Wizard

Add records from any Salesforce object to Emma via a list view, report, SOQL or Salesforce campaign.
Map Salesforce fields to Emma custom fields to allow segmentation or personalization.
Add or remove records from Emma groups.

If you are working with an Emma HQ account it is not possible to add audience members to the parent level, make sure to connect a sub client.

Video overview

Below is a detailed video overview. You can skip to specific sections by hovering on the timeline or clicking on the play bar's chapter list.

Creating an import

The import wizard needs a source in the form of a Salesforce campaign, report, list view or SOQL statement. If you have not already done so create one of these first ensuring you include an email field (not applicable to SOQL).

Please note that Salesforce limits, report imports to 50,000 records if you have more than this try using the SOQL, campaigns or list view approach. List view import is not available in Salesforce Professional.

Go to the Emma tab in Salesforce
Now click Import wizard then click the New import button.
The wizard will appear asking you to select between a Salesforce campaign, report, list view or SOQL statement.
The next screen depends on what you have selected, you will be asked to choose:
a. List view - an object and a list view.
b. Report - a folder and a report.
c. Campaign - a Salesforce campaign and a status (you can also choose all statuses).
d. SOQL - an editor that you can enter your query in and validate it.
Next map Salesforce fields to Emma custom fields. If you already have custom fields in Emma, these will appear. If not you can create them from this screen. If you choose to map a Salesforce Contact or Lead ID we will use this to match records instead of an email address.
The wizard allows you to immediately Start the import, set up a Schedule for future runs or Both. If you choose to schedule you can select one, more or all run times. You can also select to add members to one or more Emma groups. And you can choose to remove members from groups.
There is also an Advanced settings which by default is collapsed. When expanded you can choose to add imported members to one or more groups. In addition you can enable the Remove members from groups options. When Remove members from groups is enabled, only audience members (i.e. Salesforce emails) in this import will be linked to the selected Emma groups. Any Emma audience members not in this import will be removed from the Emma selected groups selected .

Once submitted a subscriber import record will be created and visible on the import wizard section. Here you will be able to monitor the status of the import, see scheduling information, and view the results of a completed import. Every time an import runs it will add any new subscribers and update custom field mappings.

By default a record that has been archived in Emma will not be made active when the import wizard runs. This can be changed via Emma Settings please click here.

Remove

The remove feature should be fully understood before using. Typically it is used when you only have one scheduled import. But you can use it with multiple imports. The first thing to note is that the replace feature works at a group level.

Examples
‍
1. You have two scheduled imports one working with Group A and the other working with Group B. The replace option is enabled for both. This will work fine as the imports are working with two separate groups.

2. You have two scheduled imports one working with Group A and the other working with Group A & B. The replace option is enabled for both. Essentially this will not work as the two imports will conflict. Both will remove each other records from Group A.

Duplicates

If there are duplicate emails in Salesforce, we will first attempt to match to the most recently modified contact or lead.

Linking

By default a Salesforce record is linked to Emma via the standard email address field found on the contact or lead object. You can override this behaviour by sending the Salesforce contact or lead record ID to Emma (as a custom field).

Remove members from groups

Create your import as described above.
In the final step you will have the option to run or schedule the import.
Click on the Remove members from groups

We don't recommend using Emma Groups as there are limitations with the Emma API that could result in Rate Limit exceptions (errors will appear in the Maintenance Logs).

Consider using segments instead of Groups. These are driven from values field values in Emma that can be synced with Salesforce. They are far more flexible, dynamic and better supported. See: List segmentation

Updating an import

Go to the Emma tab‍
Now click Import wizard.
Click on the Dropdown arrow on the far right of the import you wish to Edit.
Click Edit.

Deleting an import

Go to the Emma tab
Now click Import wizard.
Click on the Dropdown arrow on the far right of the import you wish to Delete.
Click Delete.

View results

Every time an import runs we store the results to show what updates occurred in Emma.

Go to the Emma tab
Now click Import wizard.
Click on the Dropdown arrow on the far right of the import you wish to view.
Click Results.

Next Steps

Below are two articles that are recommended reading and the best next steps.

FAQs

Segments are based upon custom fields contained in your Emma subscriber lists. An audience record in Emma will need to have a value that matches the segment criteria. If records are missing from your segment, there are a few easy checks you can do in the order below:

Emma

If the custom field in Emma is a picklist, ensure the values are the same as those in Salesforce.
Find an Emma audience member that should be in the segment but is not.
Check the Emma audience member to see if they are active on the list; records that are not active will not be updated.
Does the Emma audience member have the correct values to be part of the segment? If they are correct, the problem is with the segment itself.

If you are happy, the points above are correct, and the problem lies in Salesforce, please copy the email address.

Salesforce

Paste the email address into the Salesforce global search. If you have more than one result (i.e., duplicate records with the same email address), this could be a problem.
If you have only one record, check to see:
1. If the value in Salesforce is different from Emma
2. They are active on the subscriber list the segment relates to.

Again if you are happy with the points above, the next step is to check the subscriber list itself in Salesforce. There are two ways our integration can update a custom field in Emma. The import wizard of field mappings.:

Import Wizard
The import wizard requires a source i.e., a list view, report, campaign, or SOQl query.

Check to make sure that:

The record you are looking for is included in the source.
The field you are segmenting upon is included in the source.
On the import wizard mapping screen, the field is mapped.
The import has run recently and successfully.

Field Mappings
If a person is active in Emma and has field mappings set up when the Salesforce record is edited, it will fire a trigger to update Emma. Check to see that:

Field mappings have been set up on the subscriber list.
The field the segment is based upon is mapped in the direction of Emma to Salesforce.

To test field mappings, you have two choices:

While on the field mappings, Click the Retrospective Sync button. This will kick off a process to update all records that are active in the subscriber list. Once the process has run, check to see if the record has been updated in Emma.
Go to the contact or lead record in Salesforce and Click edit, without making changes Click save. This will fire our trigger and attempt to update the data in Emma.

If the record has been updated, this points to a problem with the trigger, most likely permissions, or a conflict.

Conflicts
Although we use standard Salesforce triggers, they can conflict with other code. A trigger fires when a Salesforce record is changed; this might happen by a user or an automated process. If there is a conflict, it could stop our code from executing as expected. It is tough to diagnose this type of problem.

Permissions
When a trigger fires, it needs specific permissions. So if the user editing the Salesforce record (which fires our trigger) does not have one of our permission sets, the trigger will fail. If this is the problem, it is straightforward to correct by assigning a permission set; this article explains how.

Long term solution
Although field mappings have their place, you might want to consider switching to our import wizard. Or you could use the import wizard as a safety net to run alongside your field mappings. The import wizard runs as scheduled APEX batch code, which means it is far less likely to encounter conflicts. Permissions are not a factor as you can only set up the wizard if you have permission, the code then executes under your Salesforce user.

If you'd like to use the import wizard as a safety net, I do have a few suggestions:

Create a Salesforce report that contains the fields you are using in-field mappings.
Filter that reports so that it only includes records that were last modified today.
When you set up the scheduling of the import wizard, choose to have it run every hour of every day.

Using this approach, should the field mapping not work, the import wizard will keep Salesforce and Emma in sync. Filtering on records only modified today makes the import very efficient, which is better for your overall Salesforce Org performance.

In this article

Basics

Import Wizard

Video overview

Creating an import

Remove

Duplicates

Linking

Remove members from groups

Updating an import

Deleting an import

View results

Next Steps

FAQs

Basics

Partners

Legal

Product

Resources

Import Wizard

Video overview

Creating an import

Remove

Duplicates

Linking

Remove members from groups

Updating an import

Deleting an import

View results

Next Steps

FAQs

Why can I not see an object when working with the import wizard and list views?

What happens if my import has duplicate records?

What is the 50,000 limit when working with reports?

Why are record missing from my segment?

How do segments work?

Why are records missing from my import?

Basics

Partners

Legal

Product

Resources