Data Ingestion

There are various ways to get data into Omeda if you are collecting it via an outside source. This document will go through each option and help you determine which might work best for your use-case and workflow.

Method	Description	Use-Case	Things to Consider
Omeda APIs	Provides the ability to post a transaction (customer order) to the Omeda database real-time.	Website Registration happening outside of Omeda	Developer needed on the client side to setup the API integration to push data to Omeda.
Data Management One Time List Load	Allows a client to upload a list of customers via the Support Portal for our Data Management team to ingest	Outside List Source, Event Registrants, Webinar Attendees	Typically, a one-time setup fee to create the program (or input) to process this data. Once this input is created, the same file can be processed in the same format at no additional charge.
Data Management Auto-Processor	Files can be dropped to an Omeda hosted SFTP site, in an expected format, and will be automatically processed to Omeda.	Telemarketing Files	Files need to be dropped to a specified SFTP site and 2 constants (supplied by our DM team) will need to be added to the file. You will work with our DM team to establish the expected layout.
Data Loader	External facing tool that allows a client to upload a file and map the data to be loaded to Omeda.	Event Registration, Whitepaper Downloads, Newsletter Opt Ins, Email Opt Ins	Currently you can load customer data including demographics, email permissions, newsletter products & behaviors. Magazine & Website Registration coming in 2022.
Data Loader Automated Jobs	External facing tool where files can be dropped to a specified SFTP site to be regularly ingested on an automated basis.	Event Registration, Whitepaper Downloads, Outside Newsletter Opt In form, Email Opt Ins	Automates a Data Loader job; same rules apply on the types of data that can be ingested via DL. SFTP site can be client or Omeda hosted.
Data Loader Webhooks	External facing tool that allows a client to create a webhook to pull data into Omeda on a real-time basis.	Outside form use	Once the webhook is created, the client will need to map the data. One webhook is recommended per form. Same rules apply on the types of data that can be ingested through the DL Webhook
Form Listener need to be an Omeda CDP customer to use this solution	CDP clients can place our javascript on a site that is hosting a form in order to collect the data. This sends the data to Omeda without the need of an API integration.	Outside form use	The forms need to be a single page and need to allow for a 3^rd party js to be running on the form. You need to work with Data Management in order to set up an Input for the data to be processed. Processes Overnight.
Omeda Forms	Clients can build forms using Omeda’s Form Builder Tool. Data is connected directly to Omeda and can be processed real-time or overnight.	Magazine Subscriptions, Preference Pages, Lead Forms, Registration Forms including Username/Password, Payment Forms, etc	No mapping needed since the Form Builder tool is connected directly to Omeda’s database. If collecting payment, we connect your merchant account to our Hosted PCI integration to securely process payments.

Tags:

Table of Contents