Integrating Formulayt with Eloqua
Formulayt forms can send submissions to Eloqua via HTTPS POST to capture user data within your Eloqua instance. Additionally, Formulayt can retrieve contact information for form pre-population using both the Eloqua API and Web Data Lookups (WDLs), providing the most reliable data retrieval.
Form Submission Capture
Basic Setup
Create an Eloqua form to capture data from Formulayt form submissions:
Typically, only a single Eloqua form is needed
Include all possible fields from all Formulayt form types, including hidden fields
Disable validation on all fields (validation rules can cause silent submission failures)
Add the HTML form name in a hidden field called "elqFormName" on your Formulayt form
Ensure all Formulayt field names match the HTML names of receiving fields on your Eloqua form
Add these details in the Formulayt Apps area:
Eloqua site ID
Form submission URL
Multiple Eloqua Forms
If you plan to use multiple Eloqua forms:
Use Rules within Formulayt to control which Eloqua form receives submissions
Note that Formulayt can only submit to one Eloqua form at a time
Use Eloqua resubmission processing steps where data needs to be submitted to multiple Eloqua forms simultaneously
Anti-Spam Measures
Eloqua offers optional anti-spam measures to reduce spam submissions. Important implementation steps:
Contact your Oracle account manager to enable this on your Eloqua account
Once you can see the anti-spam option in Eloqua, activate anti-spam in the Formulayt Apps area
Then enable it on the Eloqua form
Always test submissions after activation
Note: A honeypot field (typically named "address1") is added to all forms. If your honeypot field has a different name, ensure it exactly matches the value in the honeypot field in the Formulayt Apps area.
Pre-Population Data
API Configuration
Create an API account specifically for Formulayt with read access to these endpoints:
data/visitors
data/contacts
data/contact/view
assets/contact/lists
assets/contact/fields
assets/contact/view
assets/forms
You'll also need to create a view that lists all contact fields for any given contact.
Web Data Lookups (WDL) Configuration
Configure these WDLs:
Visitor lookup:
Should not accept search criteria
Should return the visitor record (including email address) for the current site visitor
Email recipient ID lookup:
Should accept an email recipient ID
Should return the visitor record including the visitor's email address
Ensure "Restricted Data Lookups will only return data if the visitor is already linked to that Contact" is checked
Email contact lookup:
Should accept an email address
Should return the full contact record associated with this email
Must include all fields marked for pre-population in your account
Integration Information Required
Provide the following in the Formulayt Apps area:
For API account:
Company name
Username
Password
ID of the 'all contact fields' view
For Web Data Lookups:
Visitor lookup:
Web lookup ID
Name of the email address field returned (e.g., 'V_Email_Address')
Email recipient ID lookup:
Web lookup ID
Name of the email recipient field expected (e.g., 'V_EmailRecipientID')
Name of the email address field returned (e.g., 'V_Email_Address')
Email contact lookup:
Web lookup ID
Name of the email address field expected (e.g., 'C_EmailAddress')
Name of the email address field returned (e.g., 'C_EmailAddress')
Once fully integrated, you'll be able to select Eloqua fields to pre-populate Formulayt fields from the field editor.
Gate Performance Considerations
For optimal performance:
Include the Eloqua tracking script on any webpage where Formulayt gates are located
Ensure the Eloqua script appears on any page where the Formulayt script is used
Gates will wait up to 10 seconds for pre-population data (including from Eloqua)
If the Eloqua script is missing, gates won't render until this timeout has elapsed