Formulayt enables scalable Eloqua automation using a single Master Eloqua Form to manage contact creation and profile updates, with Form Processing Steps triggering different actions based on the information submitted.
This approach allows marketing teams to create and manage large numbers of Formulayt gates without needing to create separate Eloqua forms for every campaign or content asset.
There are three main ways to configure automation:
Form Processing Steps: Trigger different actions from a single Master Eloqua Form, based on hidden field values supplied by Formulayt.
Eloqua Form Overrides: Dynamically change the Eloqua form receiving a submission using Formulayt's elqFormName hidden field.
Form Reposting: Configure Eloqua to forward submissions to additional forms using the Post Data to Server Processing Step.
For most implementations, using a single Master Eloqua Form with conditional Form Processing Steps is the recommended approach.
Master Eloqua Form Setup
The Master Eloqua Form is the primary destination for Formulayt submissions.
It is responsible for:
Creating new contacts in Eloqua.
Updating existing contact profiles.
Capturing form data, hidden fields and campaign metadata.
Executing Form Processing Steps based on submitted data.
Triggering downstream lead management and campaign workflows.
Configuration
Navigate to Assets → Forms in Eloqua.
Create a new form to act as your Master Eloqua Form.
Include all fields used across your Formulayt gates, including relevant hidden fields.
Ensure the HTML field names match the corresponding Formulayt fields.
Configure the appropriate field validations (we recommend turning all Eloqua validation off apart from ensuring the email field is mandatory; let Formulayt handle the validation).
Under Processing, configure the Key Field Mapping, normally using Email Address to identify contacts.
Add an Update Contacts – With Form Data Processing Step and configure the field mappings.
Save the form.
Make a note of the form's HTML name, which will be used when configuring Formulayt.
This centralized configuration ensures that all submissions follow consistent data collection and processing standards.
Configuring the Master Eloqua Form in Formulayt
Formulayt determines which Eloqua form receives a submission using a hidden field named:
elqFormName
This field contains the HTML name of the destination form in Eloqua.
Creating the Hidden Field
Navigate to Setup → Fields in Formulayt.
Create a hidden field named elqFormName.
Set its pre-population source to Fixed Value.
Enter the HTML name of your Master Eloqua Form.
Save the field and publish your changes.
For example:
elqFormName = GlobalLeadCapture
With this configuration, all Formulayt gates using the Eloqua integration will submit to the GlobalLeadCapture form by default.
Important: The value must match the Eloqua form's HTML name, not necessarily its display name in the Eloqua interface.
Overriding the Default Value
Although a fixed value is recommended for the default configuration, Formulayt provides several ways to populate or override hidden field values.
These include:
Fixed Value: Use a predefined Eloqua form name.
Gate Editor: Allow gate authors to specify values when creating or editing individual gates.
Form Field: Copy a value from another field.
Query String: Capture a value from a URL parameter.
Page Attributes: Derive values from the hosting page, including metadata.
Formulayt Rules: Dynamically change the field value based on conditions such as gate type, region or other submitted information.
This flexibility allows customers to implement centralized form routing while accommodating different business requirements.
For example, submissions could be routed to different Eloqua forms based on geography, campaign type or the product selected by a visitor.
Using Form Processing Steps to Trigger Actions
Eloqua Form Processing Steps provide a powerful way to execute actions after a form submission.
Using Formulayt, different gates can submit different hidden field values into the same Master Eloqua Form.
Processing Steps can then use these values to determine which actions should execute.
For example, hidden fields could identify:
The Formulayt Gate ID.
The content asset being accessed.
The Salesforce Campaign ID.
The product or service of interest.
Whether an immediate MQL process should be triggered.
The required lead management workflow.
Creating a Conditional Processing Step
Open your Master Eloqua Form.
Navigate to Processing.
Add the required Processing Step.
Configure the action you want to execute.
Change the Processing Step execution setting from Always to Conditionally.
Add conditions using the form fields submitted by Formulayt.
Save your configuration.
The Processing Step will execute only when its configured conditions are met.
Example: Triggering Actions Using Gate Name
Suppose you have a Formulayt gate for downloading a product guide.
You could configure a hidden field with the value:
GateName = product-guide-2026
In Eloqua, you could create several conditional Processing Steps.
Processing Step 1: Send Submitter an Email
Action: Send Product Guide Follow-Up email.
Condition: GateName equals product-guide-2026.
Processing Step 2: Add to Shared Contact List
Action: Add contact to Product Interest List.
Condition: GateName equals product-guide-2026.
Processing Step 3: Send Notification Email
Action: Notify the relevant sales team.
Condition: GateName equals product-guide-2026.
These actions execute when the relevant gate is submitted, without requiring a separate Eloqua form.
Using Dynamic Processing Step Values
Some Eloqua Processing Steps allow their configuration to be determined dynamically by submitted field values or lookup tables.
For example, the Add to Shared Contact List Processing Step can select different Shared Lists based on values submitted by Formulayt in hidden fields. This allows a single Processing Step to support multiple campaign workflows.
Formulayt provides several ways to configure these dynamic values:
Gate Editor Fields: Allow gate authors to select or enter values that determine which actions Eloqua executes.
Formulayt Rules: Automatically populate hidden fields based on conditions such as gate type, product interest, region or campaign metadata.
Fixed Values: Use predefined values where the same action should apply to all submissions.
Selecting Eloqua Assets Dynamically
Formulayt can also use the Eloqua APIs to retrieve available assets and present them as dropdown lists within the Gate Editor.
These include:
Shared Lists: Allow gate authors to select an Eloqua Shared List into which contacts should be added following submission.
Eloqua Forms: Allow gate authors to select an Eloqua form to which submissions should be reposted. See the Reposting Form Submissions in Eloqua section below.
Email Assets: Allow gate authors to select an Eloqua email to be sent as an autoresponder following submission.
The selected values can be stored in Formulayt hidden fields and passed to Eloqua, where they are used by dynamically configured Processing Steps to execute the appropriate actions.
This approach combines centralized automation management with self-service campaign configuration. Marketing operations teams can establish standardized Processing Steps within the Master Eloqua Form, while gate authors can select from available Eloqua assets directly within Formulayt.
New campaigns can therefore be launched without creating additional Eloqua forms or Processing Steps, significantly reducing administration and improving consistency across campaign workflows.
This functionality must be requested from Formulayt support.
Overriding the Destination Eloqua Form
Although a single Master Eloqua Form is recommended, some organizations may need submissions from specific gates to be sent to different Eloqua forms.
This may be necessary where different business units, integrations or campaign processes require separate form configurations.
Formulayt allows this by dynamically changing the value of elqFormName.
Recommended Method: Gate Editor Override
The recommended approach is to retain the default value of elqFormName and create a separate hidden field that allows gate authors to select an alternative form.
This avoids requiring every gate author to configure the Master Form destination manually.
Step 1: Create a Gate Editor Field
Navigate to Setup → Fields in Formulayt.
Create a new hidden field, for example EloquaFormOverride.
Set its pre-population source to Gate Editor.
Configure a descriptive label such as "Eloqua Form Override".
Optionally configure a dropdown containing the available Eloqua form HTML names.
Leave the field optional so that gates without an override continue using the Master Form.
Save and publish your changes.
Gate authors will now see this field in the Miscellaneous tab when creating or editing a gate.
Step 2: Create a Submission Rule
Next, create a rule on the elqFormName field that copies the override value into it when a form is submitted.
Open the elqFormName field in Formulayt.
Navigate to the Rules tab.
Create a new rule, for example "Override Eloqua Form".
Set the rule to run on Form Submission.
Configure the condition:
IF EloquaFormOverride is not empty.Configure the action:
THEN: Change the value of elqFormName to the value of EloquaFormOverride.Save and publish the rule.
Example Configuration
Field | Value |
elqFormName | GlobalLeadCapture |
EloquaFormOverride | EventRegistration |
When the gate is submitted, the rule updates elqFormName to EventRegistration.
The submission is therefore sent to the EventRegistration Eloqua form instead of the default Master Form.
If EloquaFormOverride is empty, the submission continues to the Master Eloqua Form.
Important: When overriding the destination form, the selected Eloqua form must be configured to accept the submitted fields and execute the required Processing Steps.
Other Dynamic Routing Options
Formulayt Rules can also be used to select different Eloqua forms based on other conditions.
For example:
Route European submissions to a regional Eloqua form.
Route webinar registrations to a dedicated registration form.
Route contact sales enquiries to a specialised lead management form.
Select an Eloqua form based on a particular gate type or product category.
This enables complex routing requirements without needing to create separate Formulayt form templates.
Reposting Form Submissions in Eloqua
Eloqua also supports reposting form submission data to another server or form using the Post Data to Server Processing Step.
This provides an alternative way to execute additional automation workflows.
Rather than changing the original destination, the submission is first received by the Master Eloqua Form and then forwarded by Eloqua to another destination.
This is particularly useful when:
The Master Form should always handle contact creation and profile updates.
Additional actions need to be executed using a different Eloqua form.
Existing Eloqua forms already contain Processing Steps that you want to reuse.
Form data needs to be forwarded to another system or Eloqua instance.
Configuring a Repost Destination Using a Hidden Field
Eloqua's Post Data to Server Processing Step can obtain the destination URL from a form field.
This means Formulayt can provide the destination URL dynamically using a hidden field.
Step 1: Create a Hidden Field in Formulayt
Navigate to Setup → Fields in Formulayt.
Create a new hidden field, for example EloquaRepostURL.
Configure the appropriate pre-population source.
Save and publish your changes.
The value of this field will be the URL to which Eloqua should repost the submission.
You can use a Fixed Value for a standard destination or a Gate Editor field if you want gate authors to select different destinations.
You can also use Formulayt Rules to populate this field conditionally based on campaign metadata or other values.
Important: The EloquaRepostURL name is an example. Unlike elqFormName, this is not a reserved Formulayt field name.
Step 2: Add the Hidden Field to the Master Eloqua Form
Open your Master Eloqua Form and add a corresponding hidden field.
Ensure the HTML name matches the field configured in Formulayt, for example:
EloquaRepostURL
This allows Eloqua to receive the repost destination URL with each submission.
Because the value contains a URL, review the field's validation settings. Eloqua normally blocks URLs in text-based fields by default, so this field may require an explicit exception for URL values.
Step 3: Configure the Post Data to Server Processing Step
Open the Master Eloqua Form.
Navigate to Processing.
Add a new Post Data to Server Processing Step.
For the destination URL, select Form Field rather than Constant Value.
Select the EloquaRepostURL field.
Configure the field mappings for the data that should be forwarded.
Set the Processing Step to run Conditionally.
Configure the condition so that the step executes only when EloquaRepostURL contains a value.
Save the form.
When a submission is received, Eloqua will use the URL provided by Formulayt to determine where the data should be reposted.
Step 4: Reposting to Another Eloqua Form
To repost to another Eloqua form, you need the receiving form's submission URL and HTML form name.
Open the receiving Eloqua form and navigate to:
Actions → View Form HTML → Integration Details
Use the submission URL and form details provided by Eloqua to construct the repost destination.
A typical destination URL has this structure:
Replace the example values with those from your Eloqua configuration.
For server-side reposting to Eloqua, follow Oracle's guidance on elqCookieWrite=0 and visitor identification where applicable.
Important: When reposting to another Eloqua form, ensure the destination URL contains the receiving form's HTML name (elqFormName) and Eloqua Site ID (elqSiteID). Configure the Processing Step's field mappings to forward the required data, using the receiving form's HTML field names.
The receiving form should contain the email address field for contact identification, together with any additional fields required by its Processing Steps.
The Master Form can continue to handle the main contact profile updates, while the receiving form executes its own automation actions.
Example: Triggering a Campaign-Specific Autoresponder
Suppose all gate submissions are sent to a Master Eloqua Form, but a particular content download requires a dedicated autoresponder.
You could configure:
In Formulayt
elqFormName = GlobalLeadCapture
EloquaRepostURL = the submission URL for the content-specific Eloqua form.
In Eloqua
The Master Form:
Creates or updates the contact.
Executes standard Processing Steps.
Uses Post Data to Server to repost the submission to the selected form.
The secondary form:
Identifies the contact by Email Address.
Executes the campaign-specific autoresponder.
Performs any additional required Processing Steps.
This provides a way to reuse existing Eloqua automation configurations without changing the primary submission destination.
Important Considerations for Reposting
Reposting is performed by Eloqua, not by Formulayt.
The receiving form must be configured to accept the forwarded fields.
Field mappings must use the receiving system's expected HTML field names.
The destination URL should use HTTPS and point to an approved endpoint.
Avoid allowing untrusted users to supply arbitrary repost destinations.
Test the reposted submission separately to confirm that it is processed successfully.
Prevent circular reposting configurations that could result in repeated submissions.
Form reposting is best used where a separate processing workflow is genuinely required. For simpler actions, conditional Processing Steps on the Master Eloqua Form are usually easier to manage.
Typical Lead Management Actions
Eloqua provides a wide range of Processing Steps that can be triggered by Formulayt submissions.
Action | Recommended Approach |
Send an autoresponder | Conditional Send Submitter an Email |
Add contact to a shared list | Add to Shared Contact List |
Notify a sales representative | Send Notification Email |
Update contact profile | Update Contacts – With Form Data |
Set a lead qualification field | Update Contacts – With Custom Values |
Add contact to a nurture campaign | Add to Campaign |
Add contact to a program | Add to Program |
Trigger CRM processing | Run Integration Rules |
Execute a different form workflow | Eloqua Form Override or Repost |
Forward submission to another platform | Post Data to Server |
Several of these Processing Steps support dynamic field values or picklists, enabling more advanced configurations without creating large numbers of separate forms.
Implementing an Immediate MQL Process
Formulayt can simplify MQL processing by allowing gate authors to identify which submissions should trigger an immediate qualification workflow.
For example, demo requests and contact sales enquiries may need to be processed differently from standard content downloads.
Configuration
Create a hidden field called TriggerMQL in Formulayt.
Create a corresponding field in the Master Eloqua Form.
Set the Formulayt field's pre-population source to Gate Editor.
Configure a Yes/No toggle labelled "Immediate MQL".
Open the Master Eloqua Form's Processing Steps.
Configure conditional steps that execute when TriggerMQL equals true.
These actions might include:
Updating the contact's lead status.
Adding the contact to an MQL processing program.
Sending a notification to the sales team.
Triggering CRM integration rules.
Recording the relevant campaign or qualification metadata.
Gate authors can now enable the Immediate MQL option when creating high-value gates without requiring separate Eloqua configuration for each campaign.
For more complex MQL processing, the form can add contacts to an Eloqua Program or Campaign where additional qualification, scoring and routing can take place.
Testing Your Configuration
Before deployment, test the complete process with both new and existing contacts.
Verify that:
The Master Eloqua Form receives submissions correctly.
New contacts are created and existing contact records are updated.
All visible and hidden field values are captured accurately.
Conditional Processing Steps execute when the required conditions are met.
Processing Steps do not execute for submissions that do not meet their conditions.
The elqFormName override correctly routes submissions to alternative forms.
Gates without an override continue to use the Master Eloqua Form.
Reposted submissions reach their intended destinations.
Receiving Eloqua forms execute their Processing Steps correctly.
Repeated submissions behave as intended without triggering duplicate or unwanted actions.
Review Eloqua's form submission data, contact activity and Processing Step results to confirm the configuration is working correctly.
Summary
Formulayt enables a scalable and standardized approach to Eloqua form automation.
Using a single Master Eloqua Form, organizations can manage contact creation and profile updates while using conditional Form Processing Steps to execute campaign-specific actions.
The elqFormName hidden field provides flexible control over the destination Eloqua form, allowing submissions to be dynamically routed using Gate Editor values, pre-population sources or Formulayt Rules.
Where additional processing is required, Eloqua Form Reposting allows submission data to be forwarded to other forms or systems using the Post Data to Server Processing Step.
Together, these capabilities reduce duplicated form configuration, simplify marketing automation and enable campaign teams to deploy new forms without requiring extensive Eloqua administration or developer support.