Emma for Salesforce is available only to Emma Plus, Premium and Enterprise Customers.
To determine which version of the integration package you’ve got downloaded into your Salesforce org, you’ll want to refer to the “installed packages” section within your Salesforce org’s setup. Just locate “Emma Email Marketing for Salesforce” in the installed packages list, and you’ll find the version included there.
We'll sync all of the contacts of your selected Emma audience groups with their Salesforce Lead or Contact records. From this point on, the email address for these records will automatically be synced across platforms -- Any change in either Emma or Salesforce will result in the same change in the other application. The same will be true of any additional member fields that you've chosen to sync during the setup process. If there are contacts in your Emma groups whose email addresses do not match an existing Salesforce record, we'll create a new lead record for that Emma contact with the information from their Emma contact record.
We'll also begin sharing email response data from your Emma mailings to your Salesforce account in the "Emma for Salesforce" section. Once you've synced your accounts, you'll be able to view the response activity of all new mailings in the "Emma Mailings" section. If the recipient opened or interacted with your mailing, you'll also be able to view the response interactions of individual leads or contacts in the "Emma Response Activities" sections of their profiles. This response data will only be available for mailings that are sent after you've connected your accounts; we're not able to share historical response data at this time.
We don't want to accidentally delete valuable contact records from either your Emma audience or your Salesforce account. Therefore, deleting a contact record in either system won't delete the contact record in the other; your Emma contact member or Salesforce record will simply be removed from all Emma audience groups while retaining their Emma contact record (if manually deleted in Salesforce) or their Salesforce profile (if manually deleted in Emma).
Emma and Salesforce differ on their definitions of checkbox fields. In Emma, a checkbox field has multiple options that you can then check. It's really a multi-select field. In Salesforce, a checkbox field is literally just one checkbox: on or off, yes or no, True or False. Because of this, you can't map the two to each other.
If you're looking to map a Salesforce checkbox field to Emma, we recommend using a short answer text field. If the checkbox is checked, it will show as True in Emma. Unchecked will show as False.
Note that any value other than True (not case sensitive) on the Emma side will be interpreted as False. So be careful about updating a checkbox field on the Emma side.
|Emma field type||Salesforce field type|
|Short answer||string, phone, picklist, id, reference, checkbox|
|Numeric answer||double, percent, currency|
|Radio button menu||string, phone, picklist, id, reference, checkbox|
|Drop down menu||string, phone, picklist, id, reference, checkbox|
|Country||string, phone, picklist, id, reference|
Yes, you can! During the setup process, you can add any custom object you use to track individuals and use those for mapping to Emma members. You can also remove the standard objects from those mappings, and you have full control over which object will be the Primary Object used for creating records. To learn more about how to do this, click here.
Absolutely. During the setup process, you’ll have the option of setting default values for fields when records are created. That means that if your company requires an Industry to be added before a record can be saved, you can choose a default value for that field if no value is provided (something like “Other,” perhaps). This will allow those records to be added to your Salesforce organization even if you’re not collecting all of the necessary data on your signup forms.
There are a couple things that could be making up the quantity difference on that audience group:
For the vast majority of users, storage should not be an issue. Some temporary storage will be used while processing mailings, but that data will be deleted as soon as pending changes are committed in Salesforce. Otherwise, the storage used will be to store mailing data about your contacts, which equates to about 2KB per record.
Over time, those records can build up, so we have provided a way to easily delete mailing data after a certain period of time determined by you and your team. You can learn how to do that in the Install Guide, located here.
In Salesforce, you can have many different records with the same email address. This allows you to add a contact to various opportunities or accounts, or account for folks that share an email address in some way. However, in Emma, email address is the unique identifier for a record, meaning it can only exist in Emma once. This creates some scenarios where it’s not immediately clear what should be done when one of these records is updated. Below, we’ll try to cover all of these scenarios so that you can know what to expect.
In this scenario, Member A and Member B are both in Salesforce with different email addresses. Member B’s email address is changed to match Member A’s email address. Here’s what will happen in that case.
From here onwards, any change to either member's contact info or membership should reflect on the other member and in Emma as well.
In this scenario, Member A and Member B already have the same email address. Member B’s email address is changed to a new email address that is NOT already in your Salesforce organization. Here’s what will happen in that case.
In this scenario, Member A and Member B already have the same email address. Member B’s email address is changed to a new email address that is already in your Salesforce organization. Here’s what will happen in that case.
In this scenario, Member A and Member B have the same email address in Salesforce, and Member A is deleted. Here’s what will happen in that case.
In this scenario, Member A has a unique email address in Salesforce. Member A is deleted. Here’s what will happen in that case.
When a record is updated in Salesforce, the Emma For Salesforce integration uses the Salesforce API to send that data to Emma.
When a record is updated in Emma, we send a notification to Salesforce to indicate something has changed. Salesforce will then make an API call to get that updated data from Emma.
If an Emma Group inside of Salesforce is auto-refreshed from a Salesforce report, the auto-refresh itself doesn’t use an API call (since it happens inside of Salesforce), but transferring the data over to Emma will use an API call.
Although we have worked to make it as efficient as possible, the Emma For Salesforce integration does use Salesforce API calls when Emma Groups or their contact records are updated, refreshed, or synced.
We've got instructions for this here.