# Omeda ### Setting Up the Integration To create an Omeda integration in Feedotter, navigate to your integrations settings and add a new connection with the following fields: **Connection Label** — A memorable name for this connection (e.g., "Omeda" or something more specific if you manage multiple). **API Key** — Your Omeda API key. **Client Code** — Your Omeda client abbreviation code. **Owner User ID** — The Feedotter/Email Builder account user ID that will own deployments created through this integration. This Omeda user must have: * API access permissions * Full Email Builder permissions **API Endpoint** — Leave blank to use the default (`https://ows.omeda.com`), or enter a custom endpoint if required. > **Tip:** Before publishing to a live audience, we strongly recommend creating a small test list in Omeda. Use this list for initial testing to verify your setup and content before sending to your full audience. *** ### Publishing a Newsletter Issue When you're ready to publish an issue, Feedotter will walk you through the following configuration: #### Issue Details Confirm the issue name and the Omeda connection you're publishing to. #### Publishing Action Choose one of two options: * **Create deployment only** *(default)* — Creates the deployment in Omeda without sending. * **Create deployment and send** — Creates the deployment and schedules or immediately triggers the send. **Test Recipients (optional)** Tests are delivered to the deployment owner by default. You may optionally add additional test email addresses (comma-separated). #### Omeda Details | Field | Notes | | -------------------------- | ---------------------------------------------------------------------------------------------------------- | | **Deployment Type** | Required. Select from the dropdown, which is populated from your Omeda account. | | **Deployment Campaign ID** | Optional. Assign an Omeda Campaign ID to the deployment. | | **Audience Type** | In most cases, use **Audience Builder Query**. Recipient List (FTP upload) is available as an alternative. | | **Query Name** | The exact name of the saved Audience Builder query in Omeda. This must match precisely. | #### Schedule Your Send Choose **Send Now** to send immediately, or **Schedule** to set a future date and time. *** ### Important Considerations #### Approval Email from Omeda When a deployment is published, **Omeda will automatically send an approval email to the user attached to the integration**, asking them to approve the send. This is Omeda platform behavior and cannot be disabled — there is no way to prevent this email from being sent. The send itself is not blocked or held pending approval. Be aware of this during initial testing, as it can be unexpected. #### Merge Variables All of Omeda's standard merge variables are available for use in Feedotter. Refer to the [Omeda Merge Variables documentation](https://knowledgebase.omeda.com/omedaclientkb/email-merge-variables) for the full list. Common variables include: **Personalization** * `@{First Name}@` — Recipient's first name * `@{Last Name}@` — Recipient's last name * `@{Email Name}@` — Recipient's email address **Dates** * `@{mv_date_M/d/yyyy}@`, `@{mv_date_MMM d, yyyy}@`, and several other date format variants **Links** *(must be placed inside `` tags)* * `@{mv_online_version}@` — Online version of the email * `@{preferencepagelink}@` — Email preference/unsubscribe preference page * `@{confirmunsubscribelink}@` — Confirm unsubscribe page * `@{forwardtoafriendlink}@` — Forward to a friend page **Other useful variables** * `@{customer_id}@` — Omeda customer identifier * `@{encrypted_customer_id}@` — Encrypted customer identifier (useful for tracking and cache busting) * `@{hashed_email_address}@` — Hashed email address for tracking purposes **Custom merge variables** are also supported. Wrap any field header from your audience list with `@{` and `}@` — for example, `@{unique_id}@` — and the value will be merged per recipient. The field header must match exactly. #### Unsubscribe Links and Preference Centers Omeda uses standard variables for unsubscribe links and the online version URL. If you are using a custom preference center, this is typically handled through Omeda's forms feature, and the relevant URL will usually contain a user token or ID to connect subscriber data. **No errors or send blocks will occur if these variables are missing from your email.** The deployment will still send. Plan your unsubscribe and preference center approach based on your Omeda setup, not on Feedotter requirements. #### Dynamic Content > ⚠️ Omeda's dynamic content feature is compatible with API-based deployments. This has not been definitively confirmed, but exercise caution if you rely on dynamic content blocks — they may not render as expected when publishing through the Feedotter integration. We will update this documentation once this is verified. #### Audience Attachment — Do Not Interrupt Attaching a large audience to a deployment can take **one to two minutes** for lists with hundreds of thousands of contacts. During this time, the Feedotter UI will show a progress spinner and may appear to stall. This is expected — Feedotter is waiting on Omeda to confirm that the audience has been successfully attached. > ⚠️ **Do not cancel, navigate away, or close the browser during this phase.** The process is actively running in the background. Interrupting it may result in an incomplete or failed deployment. Wait for the spinner to resolve before taking any further action. Feedotter is actively investigating ways to move audience attachment to a background process to improve this experience in a future update. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.feedotter.com/integrations/omeda.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.