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.- In Eloqua, go to Settings → Users and Security → Users.
- Open the Groups tab in the left panel.
- Click ▾ next to Advanced Users - Marketing and select Copy Security Group.
- Name the copy, for example
Conversion API, and create it. - Open the new group and click Action Permissions.
- Click Edit.
- Under API, check Consume API.
- Save your changes.
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.- Go to Settings → Users and Security → Users.
- On the Users tab, click Users ▾ → Add New User.
- 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
- Set User’s Password Expires? to No. Password never expires.
- Leave User is SSO only? set to No. User can log in without SSO. The connection uses a password login.
- Under Security Groups, select the group from Step 1 in All Security Groups and click › to move it to Selected Security Groups.
- Under Communication Preferences, leave Send User a New User Welcome email? set to Yes.
- Click Save.
- Open the welcome email, set the user’s password, and store it securely.
- Sign in to Eloqua as the integration user with the company name, username, and password to confirm the login works.
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.- Sign in to Eloqua.
- Look at the address bar. The pod is the part after
secure., such asp03inhttps://secure.p03.eloqua.com.
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
- Click Add server.
- Click Connect on the Eloqua server.
- Complete the authorization flow and return to Conversion.
- Confirm the server shows Authorized.
Test the connection
- Open the server’s Tools tab and confirm Eloqua tools are listed.
- Start a Conversion AI chat and ask it to list up to three existing Eloqua emails, without creating or changing anything.
- Approve the read-only tool call if prompted.
- Compare the returned names with the same Eloqua instance. A successful empty result is valid if it has no emails.
Troubleshooting
- Not Found or Unreachable: check the server URL, pod (such as
p03, notPOD3), and/mcpsuffix. - Authentication errors: confirm the OAuth client ID is
CompanyName\Usernameand 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.