Skip to main content
Create an Eloqua security group with API access and a dedicated integration user, find your pod, then add the Eloqua MCP server to Conversion. The server gives Conversion AI chats and agents tools for Eloqua’s Application API: emails, landing pages, forms and form data, campaigns, programs, contacts, accounts, contact lists, segments and filters, custom objects and their data, images, microsites, email groups, headers and footers, option lists, and users. The Bulk and Reporting APIs are not included.

Set up Eloqua

Before you begin

  • A Conversion Administrator account to add the server.
  • Eloqua administrator access to create security groups and users.
  • Your Eloqua Company Name, the value you enter on the Eloqua sign-in page.
  • An email inbox you can read for the integration user. Eloqua sends the new user a welcome email.

Step 1: Create an API security group

Eloqua requires at least the Advanced Users - Marketing permissions for API logins, but that group doesn’t include API access. Copy it and add API access to the copy. This keeps API access off your existing marketing users.
  1. In Eloqua, go to Settings → Users and Security → Users.
  2. Open the Groups tab in the left panel.
  3. Click ▾ next to Advanced Users - Marketing and select Copy Security Group.
  4. Name the copy, for example Conversion API, and create it.
  5. Open the new group and click Action Permissions.
  6. Click Edit.
  7. Under API, check Consume API.
  8. Save your changes.
Add other permissions to this group only if Conversion needs to read or change assets that Advanced Users - Marketing can’t. The tools can only do what the integration user can do in Eloqua.

Step 2: Create an integration user

Eloqua authenticates API calls with the same company name, username, and password used to sign in to the web app. We recommend a dedicated integration user rather than an individual employee’s account, so the connection doesn’t break when that person leaves or changes their password.
  1. Go to Settings → Users and Security → Users.
  2. On the Users tab, click Users ▾ → Add New User.
  3. Under Login Info, fill in:
    • First Name: Conversion
    • Last Name: Integration
    • Email Address: An inbox you can read, such as a shared mailbox
    • User Name: Conversion.Integration
  4. Set User’s Password Expires? to No. Password never expires.
  5. Leave User is SSO only? set to No. User can log in without SSO. The connection uses a password login.
  6. Under Security Groups, select the group from Step 1 in All Security Groups and click › to move it to Selected Security Groups.
  7. Under Communication Preferences, leave Send User a New User Welcome email? set to Yes.
  8. Click Save.
  9. Open the welcome email, set the user’s password, and store it securely.
  10. Sign in to Eloqua as the integration user with the company name, username, and password to confirm the login works.
To give an existing user API access instead, go to the Users tab, click ▾ next to the user, select Edit User Settings, and add the group from Step 1 under Security Groups. A login without Consume API connects successfully, then returns an HTTP 403 on the first tool call.

Step 3: Find your pod

Each Eloqua instance lives on a numbered pod, and the MCP server URL must name it.
  1. Sign in to Eloqua.
  2. Look at the address bar. The pod is the part after secure., such as p03 in https://secure.p03.eloqua.com.
You can also go to Settings → Display Preferences → Company Defaults and read the POD field. It shows the pod as a number, such as POD3. Use the two-digit form in the server URL: POD3 is p03.

Step 4: Add the server in Conversion

In Conversion, go to Settings → AI → Connections. Under MCP servers, click Add MCP server (or Add server below an existing list). Fill in the fields below. Replace YOUR-POD with the pod from Step 3, such as p03. Do not enter your Eloqua address (secure.p03.eloqua.com) as the server URL. For example, company Acme and user Conversion.Integration use the client ID Acme\Conversion.Integration. If a form field changes the backslash, use a forward slash instead: Acme/Conversion.Integration.
The client ID appears in the authorization URL. Never put the password in the client ID or the server URL.

Step 5: Authorize the connection

  1. Click Add server.
  2. Click Connect on the Eloqua server.
  3. Complete the authorization flow and return to Conversion.
  4. Confirm the server shows Authorized.
The wrapper checks the login with Eloqua before it finishes authorizing. If the company lives on a different pod than the server URL names, the error tells you which pod to use. Each member must connect individually. The Eloqua permissions come from the user whose login is entered in the OAuth fields.

Test the connection

  1. Open the server’s Tools tab and confirm Eloqua tools are listed.
  2. Start a Conversion AI chat and ask it to list up to three existing Eloqua emails, without creating or changing anything.
  3. Approve the read-only tool call if prompted.
  4. Compare the returned names with the same Eloqua instance. A successful empty result is valid if it has no emails.
Review tool approval settings before using tools that change data.

Troubleshooting

  • Not Found or Unreachable: check the server URL, pod (such as p03, not POD3), and /mcp suffix.
  • Authentication errors: confirm the OAuth client ID is CompanyName\Username and the client secret is the integration user’s current password. If the error names a different pod, use that pod in the server URL.
  • A tool fails after connecting: check that the integration user’s security group has Consume API, and the error returned by Eloqua.
After correcting the settings, reconnect if needed and use Refresh tools on the server page. A tools list confirms discovery; a successful read-only call confirms access to the platform.