Support | Administration | Manage Billing

Manage Billing

4 minute read

Purchasing is managed via a dedicated billing portal.
Checkout only support monthly billing paid by card.
In app you can change billing details, view and resend invoices.

Pricing

Billing occurs monthly from your date of purchase, with pricing based on how many active Emma audience members. If your active Emma audience members total changes in the new billing month, you will be automatically moved to the appropriate billing tier.

Purchasing

To purchase, go to the billing tab in Salesforce and click on the subscribe now button for your chosen plan type. Once clicked, you will be taken to our dedicated Stripe portal to complete the purchase process.

Before you can purchase you must:
‍
1. have tried our product in a Salesforce Production environment.
2. be a Salesforce system administrator.

Change card details

To update your card details, go to the billing tab in Salesforce and click on the billing portal button. Once clicked, you will be taken to our dedicated Stripe portal to complete the process.

Change contact details

Cancellation

You can cancel at anytime you will just be charged for the month you are in. The only way to cancel is to Contact us. Uninstalling the application, leaving Emma or Salesforce will not cancel your subscription and you will still be liable for any charges incurred.

Next Steps

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

General Settings
Importing your Salesforce data

FAQs

Can you sign an NDA?

We’ve not typically needed to sign NDAs to gain access before. As an official Salesforce partner, the special grant login we use is to review logs and checking your org’s settings to help resolve specific issues.

However, I completely understand your need your data concerns. If an NDA is essential on your side, we’d need to run it through our legal team to review, which may incur an external cost. I’m happy to check what that would look like in terms of fee and timeline if you’d like me to explore that.

Just so you’re aware, we’re a small company with tight margins. Normally, we provide email-based support only, but in this case I felt we could help speed things along for you with access and see information that is only available to us stored in your org. If you’re comfortable proceeding without an NDA, access would only ever be granted to myself (I’m one of the founders) or to Barbara, our resident Salesforce MVP and Nonprofit specialist (Barbara’s LinkedIn). We do not work with any external developers our team is all in-house. Of course, if it helps, I can also notify you when we’ve completed our checks so you can immediately remove our access.

Please let me know how you’d like to proceed. If you’d prefer the NDA route, I’ll get the legal review cost and turnaround time confirmed for you straight away. Or I can provide more suggestions via email. Another option would be to engage one of our consulting partners.

How can I reduce costs?

Our integration is priced with tiers, based on your subscribed audience members. If you would like to lower your subscriber count to qualify for a lower tier, we have these recommendations:

Run a re-engagement campaign to remove disengaged audience members. Many online resources describe this process: you send a final campaign to re-engage members who haven't opened an email in a specific timeframe. Then you archive them if they don't re-engage.
Create a separate Emma Account (or sub-account) for any audiences you don't need to sync to Salesforce, as we count at the account level. Don't connect that account to our integration.

Can I map a field in both directions?

Data can be mapped in both directions using a combination of our import wizard and field mappings.

Import Wizard

Will push data from Salesforce to Emma
It can be scheduled to run as often as every hour of every day
It can add new records and update existing field mappings in Emma.

When setting up your import source, we recommend applying a filter to include only recently modified Salesforce records. For more information on the import wizard, please click here.

Field Mappings

Will push data from Emma to Salesforce.
It runs as part of the primary sync, which by default runs every hour.
Can be used when updating records or creating new ones.

For more information on the field mappings please click here.

Important notes:

Test this solution thoroughly in a sandbox first.
It is worth noting that there is no conflict resolution in this solution, and each direction's timings must be considered, so they don't overwrite each other back and forth.
When you implement this solution, please be sure to run the sync once from the source of truth to the other system (so they are aligned) before enabling the sync in the other direction.
If you need to map Salesforce checkbox fields, please see our FAQ on checkbox-handling .

Can a Salesforce Integration User be the Emma Sync User?

The problem is that the integration user is designed for non-native scenarios like Zapier-style workflows. These can be less secure as the credentials are stored off-platform, so it makes sense to have a more limited user license type.

Our product is a native Salesforce application that securely integrates with the platforms we connect to. Credentials are stored securely within Salesforce, ensuring data protection. We offer various screens and processes that operate entirely within Salesforce, unlike third-party tools like Zapier. For optimal sync performance, we recommend using a system administrator license, as it provides the necessary permissions for a successful integration that is native. Extensive permissions are contained within our permission sets, which are continually updated when we upgrade users.

In addition, the integration user license is limited in terms of assignment. Salesforce currently doesn't let you log in as the integration user, so you can't start this process. There are workarounds to this, but they add unnecessary complexity and are something that we don't support.

Do you support ICU Locale?

Yes, we have completed extensive testing with ICU locale formats, and everything functions as expected. If you or your users encounter any unexpected behavior, please let us know.

Why can I access the billing portal?

The billing portal is available to users with our Full Access permission set. If you have the permission set assigned to your user, you may be using a Salesforce Classic tab in Lightning. Classic used iframes, which are no longer supported. When you try to open the portal, it will be a blank page with the stripe logo.

"Emma Settings" is the Lightning tab. Emma Settings (Admin) is the Classic tab. You can edit the tabs of your existing app or change to using our Lightning app. Apps are managed in Setup>Manage Apps.

How do I change an Emma account name?

If you change the name of an account in Emma, it will not automatically update in Salesforce. To manually update the name in Salesforce please follow the steps below:

1. Go to the Emma Settings tab.
2. Select the Sync Settings screen.
3. Locate the Connected Emma Accounts table, next to the account you want to change, click the dropdown arrow.
4. Change the Account Name.
5. Click the Validate Connection and then Save.

How Do I Trigger Automation?

Our integration can trigger certain types of Emma automation. First, you'll need to enable the Trigger Emma field change workflows setting, which you can find on our Emma Settings tab under General Options.

In Emma you can choose various trigger types. If you working with our import wizard we suggest the Contact Import trigger type. It is worth noting not all Emma accounts have the Contact Import trigger type see - https://support.e2ma.net/s/article/Trigger-events-contact-import you can check with Emma directly to see if the option can be enabled.

If you are adding records one at a time you can use the sign-up trigger type. One record could be added manually from the Emma audience related-list. Or you could use something like process builder or flow - see: https://www.beaufort12.com/emma/support/process-builder

How do I manage billing?

To help, we have our dedicated billing screen, which you can access right from within Salesforce. The billing screen will allow you to:

Purchase.
Update card details
Update billing information - the email, physical address, and tax identification.
View and resend invoices.

For detailed steps, please click here.

Can't access billing?
It is important to note that you need to be either a Salesforce system administrator or have our full permission set (preferably both), to access the billing screen.

How do I change Salesforce sync user?

Emma for Salesforce is an integration between two platforms. It requires a user from both to allow our product to work. Should one or both of those users change, you will need to update our sync settings.

Salesforce

The sync will need to run against a user on the Salesforce side. We recommend a person with a system administrator profile.
In addition, they need to have our full permission set this article shows how to add that.
Finally, go to the sync settings page and click the icon next to the Salesforce Sync User.

Emma

To reconnect please:

Go to the sync settings page.
On the Connected Accounts, table click the dropdown icon to the right of the account you want to change.
Once clicked, a sub-menu will appear.
Click on Edit Connection
Change the details there as needed.

How can I manage storage?

Two Emma for Salesforce custom objects could potentially store a large amount of data:

Emma audience members

The number of audience member records is controlled by your audience size in Emma (all statuses).

Email tracking history records (optional)

The number of email tracking history records is controlled by the "Days to Keep" in Emma Sync Settings. It is important to note that your tracking data is always safely stored in Emma, even if not synced to Salesforce.

You can change the "Days to Keep" setting as many times as you like to increase or decrease the number of records stored in Salesforce.

If you lower the days to keep, tracking history will be deleted the next time the primary sync runs.
If you increase the days to keep, you must run a Full Sync to re-sync older records.
To remove all stored email tracking history records from storage, set the days to keep to 0. Instead, you can surface data directly from Emma via our custom components.

Storage planning: Salesforce uses 2kB per record for custom objects (no matter how many fields are on the object). If you multiply the number of Emma audience members (and potentially email tracking records) you have by 2kB, and this provides a rough indicator of the amount of storage that will be used.

Is there any personally identifiable information passed across?

Emma for Salesforce does not store any customer information (given its primary role is to sync data between the two systems). Customer data is stored in Salesforce and in Emma.

The Emma application never independently calls into your Salesforce environment. This means that we don't use up inbound API calls (typically 15,000 / 24 hours) or access your customer data. The only calls that are made back into the Salesforce environment are to obtain metadata in order to support list view imports and page layout configuration. Both of these actions are driven in real-time by your Salesforce users (i.e. we don't store any of your Salesforce connection details or make calls into your Salesforce environment independently of a direct request coming from your Salesforce environment).

No personally identifiable information (PII) is sent to Emma without your permission or action. You can choose not to send any custom data to Emma or even any subscribers. Any PII is viewable within the Emma application (under subscriber custom fields). There are no other hidden fields that contain PII. More details on what is sent can be seen by viewing the technical Emma API documentation (which is used by Emma monitor for Salesforce).

Are there any API limits?

Salesforce has strict governor limits around the use of API calls. Our application does not use any API calls when syncing.

There are two types of API calls, inbound and outbound. Outbound calls from Salesforce do not count against governor limits. All syncing is via outbound calls. These do not count against your Salesforce API limit.

There are two exceptions when we need to use an inbound API call:

If you are using our import wizard with a Salesforce List View, this will use just one inbound API call.
When viewing the sync settings page in our general settings tab, again, this will use up just one inbound API call.

If you'd like to learn more about API calls, please visit this Salesforce article.

How do I perform a full sync?

It is rare but in certain cases information between Emma and Salesforce can get out of sync. There are a two primary reasons this can happen:

1. Emma API being unresponsive.
2. Custom code or processes which conflict with our integration.

To re-align the data you need to perform a full sync. A full sync we will first remove the data we have loaded from Emma into Salesforce. Your data is safe in Emma and this only affects our custom objects, it does not impact your standard objects i.e. Contacts or Leads. It will then re-import using the latest Emma data.

Performing a full sync

1. Go to the Emma Admin app
2. Select the General Settings tab.
3. On the top right there is button called Sync Now next to this there is a dropdown arrow click this and then choose the Full Sync option

Once clicked a number of jobs will be kicked off to align your data. This can take some time to complete but you are free to navigate away from the page and use Salesforce normally. Once the full sync has been completed your data will be aligned to Emma.

What happens when a person unsubscribes?

If a person unsubscribes from an email sent via Emma this first updates Emma. Then when our primary sync next runs the corresponding Emma audience record in Salesforce is updated from active to unsubscribed. Optionally there is a setting that will allow us to update the standard email opt-out field. For more information please see - https://www.beaufort12.com/emma/support/email-opt-out

In this article