Search the Omeda Knowledge Base

Form Listener

Summary:  

Form Listener integration is one component of Omeda’s CDP solution.  By placing Olytics JavaScript on a site that is hosting one of your forms, you can begin creating transactions back to Omeda without the need for an API integration.   The form will complete its normal transaction on submission, the transaction will process where it normally does, but now Olytics will also capture the data and pass it back to Omeda. In addition, you can add processing rules for the transactions as well as on-demand welcome emails. 

Since there are a lot of different 3rd party forms out there each with its own subtleties, it’s important to confirm if the vendor will allow you to place Olytics JavaScript on a form.   In general, if the form is hosted on your site natively, then the Form Listening integration will be the most successful.  If you are using an obscure 3rd party form hosting company, then there is a chance that it will require some investigating.

Beta Version FAQs:  

  • What if I have a multiple page form? Form Listener is a good fit for forms that are single page forms.  
  • What data will be passed back to Omeda Within the UI, you can specify, which fields you want to pass back to Omeda. In some cases, forms can contain various fields that you don’t want passed back to Omeda e.g. utm tags, page Id or paid fields like credit card information.  
  • How is the data processed? Once the data is in Omeda, an your Audience Relationship Manager  will need to create a processing input.  This input id will be later referenced in the setup portion of the UI. 
  • How do I access Form Listener?  To Access Form Listener go to your Omeda Portal Menu and under the Activate section select Integrations then Form Listener. If you do not see the form listener Icon, please contact your Audience Relationship Manager for access.

 

 

 

 

Future Enhancements 

  • Enhance UI FTP section 
  • Integrate with Omeda Data Loader to eliminate need to contact Omeda to create an Input 
  • Daily transaction summary how many transactions, rejects etc.  

Setup:

  1. Give Form Listener a Unique name 
  2. The URL location of the site where the form is located.  
  3. A brief description (optional)
  4. Form HTML Id – forms placed on a site will generally have an ID associated to them. This Id is what is needed to identify the form that will be capturing data and associate it to the correct Form Listener job.
  5. Daily Processing via Input: (not required).
    * If data that is captured needs to be loaded into Omeda, then a processing input will need to be created by Omeda.
    * The Processing Input is used to map the form contact and demographic fields to Omeda. In addition, the input can have rules like match on contact, email only or hold transactions for approval.
    * If there are changes to the form after the processing input is created e.g. adding new demographics, contact fields, or even new responses to an existing demographics, then Omeda will need to update the processing input or the transactions will reject.  
  6. Daily FTP Upload – (not required)
    * Nightly job that will FTP any data that has not already been sent.
    * If there is a Processing Input created, then Omeda will give you the ftp site and file name.
    * If the data needs to post somewhere else, you can provide ftp site information here.  
  7. Delimiter for Multi-Response Questions: Only required if your transaction has multiple response questions.  
  8. View Recent Data: Once setup is completed and you saved your integration, you can generate a test link to “save and test on my site” to confirm the form submission data. To view test data, select the “view recent data” within setup.

Use “Output Test Submissions” to export the data in an excel file  

Reporting 

Each Form Listening job has its own report that provides anonymous and known visitor counts on Submission by Day, by URL and Entry. You can limit the reporting to a specific date range by entering in a start date and end date and then export the form transaction data from that period. 

Last Updated On November 21, 2018
Knowledge Base Feedback