Omeda
The Omeda integration connects Ad Orbit with Omeda's audience management platform, enabling publishers to synchronize subscription data, contact information, and list management between the two systems. This eliminates manual data transfers and keeps your audience records up to date in real time.
What this integration does for you
Exports print, digital, newsletter, and marketing list subscriptions from Ad Orbit to Omeda automatically
Imports subscription updates (address changes, deliverability flags, opt-outs) from Omeda back into Ad Orbit
Supports file-based data transfer via SFTP
Tracks every exported and imported file so records are never processed twice
Notifies your team when subscriber data changes due to an Omeda update
Data Flow
Direction | What happens |
|---|---|
Ad Orbit → Omeda (Export) | Subscription records are exported as CSV files and sent to Omeda via SFTP. Omeda uses this data to manage your subscriber fulfillment and audience segments. |
Omeda → Ad Orbit (Import) | Omeda returns update files containing address corrections, deliverability changes, opt-outs, and email bounce information. Ad Orbit processes these files and updates the corresponding subscriber records. |
Export Types
Export Type | Description |
|---|---|
Full Export | A complete snapshot of all subscribers for a given publication or list. Used for initial setup and periodic full refreshes. |
Incremental Export | Only records that have changed since the last export. Exported records are tagged with transaction types: Add, Update, or Delete. |
Simplified Digital Media Export | An abbreviated export format for digital media publications, using a condensed set of fields accepted by Omeda. |
Print Subscription Export | Exports print subscriber data, appending _p to the filename to distinguish from digital exports of the same publication. |
Digital Subscription Export | Exports digital subscriber data, appending _d to the filename to distinguish from print exports of the same publication. |
Marketing List Export | Exports marketing contacts with subscription type M. Inclusion is controlled by a configuration setting on the Omeda Setup page. |
Newsletter Export | Exports newsletter subscription records as distinct per-newsletter lists. |
Import (Updates from Omeda)
Omeda sends back two types of update files that Ad Orbit processes automatically each day:
Print update files: contain address changes and physical mail deliverability status (e.g., undeliverable / Nixie COA)
Digital update files: contain email address changes, bounce notifications, and email opt-out flags
For each file received, Ad Orbit will:
Match records using the Ad Orbit Subscription ID (passed as the LaunchPad ID in the outgoing file)
Update the subscriber's contact details, deliverability flag, or email status
Log the change in Subscription History, including a link to the specific Omeda file
Send a notification to the publication's configured Subscription Update notification user(s)
Note
Subscriptions marked as undeliverable are flagged and deactivated but are not permanently deleted from the system.
Transaction Types
Transaction Type | When it is used |
|---|---|
Add | The subscription has never been exported to Omeda before. |
Update | The subscription was previously exported and one or more fields have been changed. |
Delete | The subscription has been deleted in Ad Orbit and Omeda should remove it. |
Note
Transaction types are set automatically. You do not need to manage them manually.
Required Information from Omeda
Before configuring the integration in Ad Orbit, you will need the following from your Omeda account representative:
Environment ID — a unique identifier assigned to your publisher account by Omeda
Input IDs — unique identifiers for each publication or list you plan to export (print and digital editions of the same publication may share an Input ID in Omeda)
SFTP credentials — server address, username, and password for the Omeda file transfer server
Configuring the Omeda Setup Page
Navigate to Settings > Integrations > Omeda to access the setup page.
Setting | Description |
|---|---|
Environment ID | Your unique Omeda publisher environment identifier. |
Export SFTP Server | Server address for sending export files to Omeda. |
Import SFTP Server | Server address from which Ad Orbit retrieves Omeda update files. |
FTP Account Passwords | Passwords are masked in the UI for security. Re-enter when updating credentials. |
Export Publication Subscription Format | Controls whether print and digital exports are sent as separate files (recommended) or combined. |
Exclude Print Subscribers on Digital Export | When enabled, subscribers who already appear in the print export will not be duplicated in the digital export. This prevents Omeda from downgrading bundled (print + digital) subscriptions to digital-only. |
Export Marketing Subscriptions | Controls whether marketing list subscriptions are included in Omeda exports. Disabled by default. |
Configuring Publications
Each publication you want to export to Omeda must have an Input ID assigned. For publications with both print and digital editions, you can set a single Input ID at the publication level — Ad Orbit will automatically append _p or _d to the filename to differentiate the files.
For more granular control, you can also assign an Input ID at the subscription plan level. This allows different subscription tiers (e.g., Basic vs. Premium) to be tracked as separate audience segments in Omeda.
Note
Input IDs must be unique within a given type (publication or contact list), but the same ID can be reused across types.
Customizing Export Column Headers
By default, Ad Orbit uses a standard set of column headers in the export CSV. If Omeda has requested custom header names for your account (which may be required for your specific Omeda configuration), you can rename headers directly on the Omeda Setup page without needing a code change.
The following fields are included in the standard Omeda subscription export. You can enable or disable individual columns on the Omeda Setup page:
Environment ID: Your Omeda publisher identifier
Input ID: Publication or list identifier
Subscription ID: Ad Orbit's unique subscription identifier
LaunchPad ID: Ad Orbit's Contact ID - used by Omeda to match returning records
Transaction Type: Add, Update, or Delete
First Name
Last Name
Prefix: Optional - enable on Setup page
Middle Name: Optional - enable on Setup page
Suffix: Optional - enable on Setup page
Company Name: Optional - enable on Setup page
Street 1/ Street 2
City/ Region/ Zip/ Country
Email Address
Fax: Optional - enable on Setup page
Promo Code: Optional - enable on Setup page
Publication Name
Format Served: Print (P), Digital (D), or Marketing (M)
Receive Promo Emails
Start Date/ Expire Date
Created Date: Optional - enable on Setup page. Required by some Omeda configurations to control processing timing.
Verification Date: Always exported as blank per Omeda specification
When Omeda sends update files back to Ad Orbit, each record contains the following fields:
Customer ID: Omeda's internal subscriber identifier (stored in Ad Orbit if returned)
LaunchPad ID: Ad Orbit's Subscription ID - used to match the record in Ad Orbit
First Name
Last Name
Title
Company Name
Street 1
Street 2
Street 3
City
Region Code
Zip/ Postal Code
Country
Email Address
group_key: Describes the type of change: Nixie (undeliverable physical address), COA (change of address), Email Opt Out, Email Undeliverable, or Email Address Change
Note
Ad Orbit can also match import records by Contact ID or Contact Email Address in addition to Subscription ID — useful when exporting without subscription-level identifiers.
Some publishers sell subscriptions that include both a print and a digital edition as a single bundled subscription. Ad Orbit handles these with the following logic:
If Exclude Print Subscribers on Digital Export is enabled, the digital portion of a bundled subscription will not be exported separately — Omeda handles the digital access automatically based on the print subscription.
When a bundled subscription is partially deleted (e.g., only the print portion is removed), Ad Orbit will prompt you to confirm whether you want to delete both the print and digital subscriptions or only the print.
If the digital subscription remains active but the print subscription has expired or been deleted, Ad Orbit will correctly export the digital subscription to Omeda — even if the 'Exclude Print on Digital' setting is active.
Export Logs
Every file sent to Omeda is logged under Settings > Data Import & Exports > Generate Exports. You can search logs by publication name or file name to track the status of specific exports. Each log entry shows when the file was generated and whether it was successfully delivered.
Import Logs
Every file received from Omeda is recorded to prevent duplicate processing. Import logs are accessible under Settings > Integrations > Omeda > Omeda Imports and include a record of every subscription that was updated and why.
Subscription History
Individual subscription changes made via an Omeda import are recorded in the Subscription History for that contact. This includes:
Address updates
Email address changes
Deliverability status changes (print and digital)
Email opt-outs and bounces
Each Subscription History entry includes a link to the specific Omeda import file that triggered the change.
Notifications
Ad Orbit can send email notifications when Omeda imports change subscriber data. To enable this, assign one or more Subscription Update notification users on the relevant publication record.
Print subscriptions: notifications are triggered by address changes or undeliverable flags
Digital subscriptions: notifications are triggered by email address changes or email deliverability issues
Can I control which subscriptions are exported?
Yes. Marketing list subscriptions are excluded from exports by default and can be turned on via the Omeda Setup page. You can also configure whether print subscribers are excluded from the digital export to avoid duplicate records in Omeda.
What happens if the same publication has both print and digital subscriptions?
Ad Orbit generates separate export files for print (_p suffix) and digital (_d suffix) editions of the same publication. Both files use the same Input ID. This is the expected behavior for Omeda bundled subscription processing.
Can I customize the column names in my export file?
Yes. Header names can be customized on the Omeda Setup page. This is useful when your Omeda account requires non-standard column names.
Does Ad Orbit use SFTP for file transfers?
Yes. All file transfers to and from Omeda use SFTP. You will need to provide your SFTP server address, username, and password when configuring the integration on the Omeda Setup page.
What is a 'Nixie' update?
A Nixie is postal industry terminology for a piece of mail that was undeliverable as addressed. When Omeda returns a Nixie flag on a print subscriber, Ad Orbit will mark that subscription as undeliverable and notify the appropriate contact. The record is deactivated but retained in the system.
How do I add or remove export columns?
On the Omeda Setup page, there is a column mapping table where you can check or uncheck each available export field. Some fields (such as Prefix, Middle Name, Suffix, Company Name, Fax, Promo Code, and Created Date) are disabled by default and must be explicitly enabled.
Need help with the Omeda integration?
If you need assistance configuring or troubleshooting your Omeda integration, please reach out to your Ad Orbit account manager or contact our support team.
When contacting support, please have the following ready:
The publication(s) affected
A description of the expected vs. actual behavior
Relevant export or import log entries from the Omeda integration page
New 3/13/2026