Administration of Emma for Salesforce.
Email opt out/in settings.
Primary sync settings & storage management.
General maintenance messages.
Manage billing (card details, invoices etc).
The Primary sync is responsible for pulling data from Emma into Salesforce (i.e. it does not relate to pushing records from Salesforce to Emma, for that use the Import wizard). It will import details such as Members, Email Tracking history and Mailings. By default, we won't touch any of your Salesforce data, but you can configure the integration to create new leads and contacts for Emma members (see: Creating records).
You can optionally set the number of email tracking history to keep in Salesforce (whilst it is still safe in Emma, this can be helpful to save on Salesforce storage). In addition you can also select which email history types to pull back into Salesforce (i.e. sent, opens etc).
The primary sync can be configured to run a different intervals. This can be configured under the Import frequency dropdown.
Email Tracking History
Prevent contacts or leads being added to lists when Salesforce email opt out is checked
If the Salesforce email opt out field is checked on a contact or lead, then they cannot be added to any subscriber list in Emma. This setting is not retrospective - i.e. it will not automatically remove people from a subscriber list, it will come into effect when the 'Email opt out' field on a contact or lead is updated. When the 'Email opt out' is checked, the Salesforce user will see a message that says that the contact or lead cannot be added to a subscriber list.
Archive Contact or Lead from Emma when Salesforce email opt out is checked
When enabled, if a Salesforce record standard Email Opt Out field is checked they will be automatically archived in Emma.
- Sync Salesforce 'Email opt' field to true with (active/opt-out state) Emma
Automatically sync the 'Email opt out' field to true when the email is archived or removed from Emma. This field is updated when the primary sync next runs (typically hourly). Turn this off if you don’t want the standard Salesforce 'Email opt out' field to be updated by the Emma integration.
Given that setting the 'Email opt' field can result in the Salesforce contact or lead being updated, be sure there are no Salesforce validation rules that would prevent the update. Any conflicts will be available in the Maintenance log.
Also use the 'Error' state to set the Salesforce 'Email Opt' field
When enabled, the Emma Member status of 'Error' will also be used to set the Salesforce 'Email Opt' (i.e in addition to the status of 'opt-out')
Archive Emma subscriber when the Salesforce contact or lead is deleted
If a contact or lead is deleted in Salesforce, move the corresponding membership record in Emma to the archive.
Archive Emma member when the email value is removed from a Salesforce contact or lead
If a contact or lead email address is cleared out in Salesforce, move the corresponding membership record in Emma to the archive.
Trigger Emma field changes workflows
With this option enabled workflow in Emma will be triggered.
Perform full daily sync of members
This option will perform a nightly full sync instead of an incremental sync. Use this option if email statuses appear to be getting out of sync between Emma and Salesforce.
Set archived Emma members back to active via Import Wizard
Enable this setting to set the status of archived Emma members back to active when using the Import Wizard.
Disable Salesforce account, contact and lead triggers
With this option enabled our triggers will be disabled for the account, contact and lead objects. This effectively stops our application from working in part for single updates.
Disable bulk triggers account, contact and lead
With this option enabled our triggers will be disabled for the account, contact and lead objects. This effectively stops our application from working in bulk operations
Internal Governor Limits
But via this screen you can change the default value for a particular job. For example if you are hitting a limit on our email opt-out batch job you can decrease the value. This will mean less records in the batch and more jobs.