Convertr Help Centre Help Center home page
Submit a request
Sign in
  1. Convertr Help Centre
  2. Integration

HTTP Integration Example: Eloqua Forms Follow

Michael Konomanyi
  • June 21, 2021 09:58
  • Updated

Introduction

You can use the HTTP Integration to integrate to a variety of API Endpoints. An example of where you can do is with Eloqua Forms.

If you are unable to integrate directly into a Eloqua instance using the direct Integrate to Eloqua or Create/Update Eloqua Integration jobs, then you may be able to do this using HTTP Integration.

While the two integrations mentioned above are the best ways to submit leads into Eloqua securely and provide more transparency on a lead's status when being submitted, you may need to use the HTTP integration for the following reasons:

  • Your client is unable to provide you access to the Eloqua instance required for direct integration
  • Your client has provided you with an Eloqua form to submit to, which cannot be achieved with the direct integrations

In general, you will be able to tell which integration you need by the data you've been provided:

  • Username, Password, Site Name/Company Name: Direct
  • Form Name, Site ID: HTTP Integration

Below we will go through how to set up the HTTP Integration.

 

Prerequisites

  • Form Name
  • Site ID
  • Eloqua Form HTML Field Names

 

Setup Process

1. Within your HTTP Integration configuration, you need to input your API URL at the very top. For this, you need your Site ID.

For Eloqua Forms, the API URL always has the same format:

https://s[SiteID].t.eloqua.com/e/f2

In this URL, you will need to replace [SiteID] with the relevant ID, as seen in the configuration window below for Site ID 1234567.

blobid0.png

 

Also ensure that your method is set to 'post'.

 

2. The next area you need to populate is the mapping section. The first 2 fields you should map are the Form Name and again, the Site ID.

On an Eloqua form, their field names for these two fields are:

  • elqFormName
  • elqSiteID

You will need to add them to the mapping as below:

blobid1.png

 

You can then add your usual field mappings directly underneath these two.

 

After completion, your integration should resemble the below:

blobid2.png

 

This will complete your HTTP Integration to an Eloqua form! Please ensure to test and confirm with your client before beginning delivery through this integration.

For more information on how you can use the HTTP Integration, see here.

Articles in this section

  • Scheduled Delivery
  • Integration Requirements
  • Multiple Campaign Integration
  • List of Convertr Supported Integrations and Their Versions
  • Additional Integration Fields
  • HTTP Integration Example: Salesforce Web-to-Lead
  • The Credentials Manager
  • Hosting a Convertr Form On Your Own Page
  • HTTP Integration Example: Eloqua Forms
  • HTTP Integration Example: Marketo Forms
See more

Related articles

  • Deliver Leads to an External Form URL Using the HTTP Post Integration
  • Integrating with Hubspot
  • HTTP Integration Examples: Hubspot Forms
  • Additional Integration Fields
  • Replacement Leads In The Convertr Platform
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request
Return to top

Related articles

  • Deliver Leads to an External Form URL Using the HTTP Post Integration
  • Integrating with Hubspot
  • HTTP Integration Examples: Hubspot Forms
  • Additional Integration Fields
  • Replacement Leads In The Convertr Platform