Form spam protection overview
Important: This feature is currently released under our Controlled Availability program. To request access to this feature, please contact your account representative for more information.
To minimize form submission spam, the Oracle Eloqua form spam protection feature can help identify and limit form submissions that are from unverified sources. When spam protection is enabled, and the form is saved, the form HTML will be updated to add submission validation to forms on Eloqua landing pages (HTML needs to be updated manually on externally hosted forms).
By using this feature to help exclude spam submissions from your form data, you can improve the accuracy of this data, for example in the Form Submission Overview report and the Form Submission Data report. This feature is disabled by default. To reduce the risk of a user improperly enabling form spam protection for a form integrated with an external web page, Eloqua administrators control which users can enable this feature. Contact your administrator if you cannot enable form spam protection. To enable this feature for users, enable the Change Form Spam Protection Status action permission for the security group they belong to. Learn more about setting the action permissions for a security group. Learn more about Enabling spam protection for forms.
Note: Blind form submit spam protection is not supported via Landing Pages or Cloud Content.
With this feature, if validation fails upon submitting the form, the submission will not pass; however, the user who submitted the form will still see a successful submission message so as not to alert them that it was marked as spam. The spam submission is subsequently stored in a separate table than that for verified form submissions, and you can retrieve these spam submissions via API.
Note: During sandbox replication, spam submission data is not replicated.