> ## Documentation Index
> Fetch the complete documentation index at: https://www.domo.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Emma Connector

## Intro

Emma offers web-based email marketing services. Domo's Emma connector allows you to see Emma data in context with your entire organization so you can make real-time adjustments to your automated campaigns that boost not only your open rates, but your business as a whole. Use Domo's Emma connector to compile reports about mailing groups and members, searches, responses, webhooks, and the like. To learn more about the Emma API, go to [http://api.myemma.com/](http://api.myemma.com/).

The Emma connector is a "Cloud App" connector, meaning it retrieves data stored in the cloud. In the Data Center, you can access the connector page for this and other Cloud App connectors by clicking **Cloud App** in the toolbar at the top of the window.

This topic discusses the fields and menus that are specific to the Emma connector user interface. For general information about adding DataSets, setting update schedules, and editing DataSet information, see [Adding a DataSet Using a Data Connector](/docs/s/article/360042926274).

***

## Prerequisites

To connect to your Emma account and create a DataSet, you must have the following:

* Your Emma public API key
* Your Emma private API key
* Your Emma account ID

You can find this information in your Emma **Account Settings**. For more information, see [http://api.myemma.com/](http://api.myemma.com/).

## Connect to Your Emma Account

This section enumerates the options in the **Credentials** and **Details** panes in the Emma Connector page. The components of the other panes in this page, **Scheduling** and **Name & Describe Your DataSet**, are universal across most connector types and are discussed in greater length in [Adding a DataSet Using a Data Connector](/docs/s/article/360042926274).

### Credentials Pane

This pane contains fields for entering credentials to connect to your Emma account. The following table describes what is needed for each field:

| Field           | Description                 |
| --------------- | --------------------------- |
| Public API Key  | Enter your public API key.  |
| Private API Key | Enter your private API key. |
| Account ID      | Enter your Emma account ID. |

For information about obtaining these credentials, see "Prerequisites," above.

After you have entered valid Emma credentials, you can use the same account any time you go to create an Emma DataSet. You can manage connector accounts in the **Accounts** tab in the Data Center. For more information about this tab, see [Managing User Accounts for Connectors](/docs/s/article/360042926054).

### Details Pane

This pane contains a **Report** menu in which you can select an Emma report type. Another selection menu, **Action**, appears when you select the **Response Mailing Information** report type.

<table border="1" cellpadding="1" cellspacing="1">
  <thead>
    <tr><th>Menu</th><th>Description</th></tr>
  </thead>

  <tbody>
    <tr>
      <td>Report</td>

      <td>
        Select an Emma report. The following reports are available:

        <table border="1" cellpadding="1" cellspacing="1">
          <thead>
            <tr><th>Report</th><th>Description</th></tr>
          </thead>

          <tbody>
            <tr><td>Fields</td><td>Returns information about defined fields for the account, such as shortcut names, display names, field types, fields IDs, etc.</td></tr>
            <tr><td>Group Members</td><td>Returns information about group members, such as group and member IDs, status, email addresses, etc.</td></tr>
            <tr><td>Groups</td><td>Returns information about groups, such as group names and IDs, account IDs, etc.</td></tr>
            <tr><td>Mailing Groups</td><td>Returns information about groups to which specific mailings have been sent.</td></tr>
            <tr><td>Mailing Headsup</td><td>Returns heads-up email addresses for specific mailings.</td></tr>
            <tr><td>Mailing Members</td><td>Returns lists of members to whom specific mailings have been sent. Does not include groups or searches.</td></tr>
            <tr><td>Mailing Messages</td><td>Returns personalized message content sent to given members as part of specified mailings.</td></tr>
            <tr><td>Mailing Searches</td><td>Returns all searches associated with sent mailings.</td></tr>
            <tr><td>Mailings</td><td>Returns information about current mailings.</td></tr>
            <tr><td>Member Groups</td><td>Returns information about groups to which a member belongs.</td></tr>
            <tr><td>Member Import Stats</td><td>Returns information and statistics about a given import.</td></tr>
            <tr><td>Member Imports</td><td>Returns information about all imports for this account.</td></tr>
            <tr><td>Member Mailing History</td><td>Returns the entire mailing history for a member.</td></tr>
            <tr><td>Member Optout</td><td>Returns details of member opt-outs, including date and mailing ID.</td></tr>
            <tr><td>Members</td><td>Returns a basic listing of all members of the account, including account and member IDs, email address, membership date, etc.</td></tr>
            <tr><td>Members Imported</td><td>Returns a list of members affected by imports.</td></tr>
            <tr><td>Response Customer Share</td><td>Returns a list of customer shares for given mailings.</td></tr>
            <tr><td>Response Mailing Information</td><td>Returns a list of messages based on a specified action.<Note><strong>Note:</strong> When this connector was initially implemented, the "Mailing ID" column in this report was mislabeled as "Import ID." Because changing the column name would break existing DataSets, this name will not be changed. If you need the Mailing ID, use the value in the "Import ID" column.</Note></td></tr>
            <tr><td>Response Mailing Share</td><td>Returns lists of shares for given mailings.</td></tr>
            <tr><td>Responses</td><td>Returns the response summary for the account.</td></tr>
            <tr><td>Searches</td><td>Returns a list of saved searches, including search name, search ID, search criteria, last run date and time, etc.</td></tr>
            <tr><td>Searches Members</td><td>Returns the members matching given searches.</td></tr>
            <tr><td>Triggers</td><td>Returns a basic listing of all triggers for the account.</td></tr>
            <tr><td>Triggers Mailings</td><td>Returns a list of mailings sent by triggers.</td></tr>
            <tr><td>Webhook Events</td><td>Returns a list of webhook events, including event name, ID, and description.</td></tr>
            <tr><td>Webhooks</td><td>Returns a list of webhooks.</td></tr>
          </tbody>
        </table>
      </td>
    </tr>

    <tr>
      <td>Action</td>
      <td>Select the desired action. The <strong>Response Mailing Information</strong> report retrieves all messages based on this action.</td>
    </tr>
  </tbody>
</table>

### Other Panes

For information about the remaining sections of the connector interface, including how to configure scheduling, retry, and update options, see [Adding a DataSet Using a Data Connector](/docs/s/article/360042926274).

## FAQ

<AccordionGroup>
  <Accordion title="Can I use the same account to create multiple DataSets?">
    Yes.
  </Accordion>

  <Accordion title="How often can the data be updated?">
    As often as needed.
  </Accordion>

  <Accordion title="Are there any API limits I should be aware of?">
    Although the Emma API has rate limits, Domo's Emma connector automatically paces to that limit.
  </Accordion>
</AccordionGroup>