> For the complete documentation index, see [llms.txt](https://docs.feedotter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feedotter.com/integrations/omeda.md).

# Omeda

This guide covers how to connect Feedotter to Omeda and publish newsletter issues through the integration.

### In Feedotter

Navigate to:

* Settings
* Integrations
* Click **Add Integration**

The new integration form will appear. Keep this open.

<div align="left"><figure><img src="https://2086102864-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIdHBGk8cqznUpEqm5g1U%2Fuploads%2FU50PzlyBT3JsOSju59Zu%2Fimage.png?alt=media&amp;token=4c82d565-1428-48f4-9b6a-ee291bf426c3" alt="" width="563"><figcaption></figcaption></figure></div>

### In Omeda

Our next task will be to create/gather the necessary keys/values to authenticate Omeda w. Feedotter.

* Click on **Your Name** in the upper right
* Click on **Manage Database**
* Click on **API KEYS** in the left menu
* Click **Create**

We recommend entering "Feedotter Integration" in the description field and setting an expiry date FAR into the future.

Open the **Brand Lookup & Store** permissions and select Brand Deployment Types Lookup

Open the **Email Builder** permissions panel and **Select All.**

<figure><img src="https://2086102864-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIdHBGk8cqznUpEqm5g1U%2Fuploads%2FSJv4hY1Vl8eVkBCcSjde%2Fimage.png?alt=media&amp;token=8eb8c510-b4dd-48bd-9b48-3984e898e903" alt=""><figcaption></figcaption></figure>

Copy the API Key value and paste it into the Feedotter input labeled **Api Key**.

Back in Omeda click **Create** to complete the new key creation.

#### Find Your Client Code

If you are unsure of this value you may need to ask your Omeda admin. Once acquired, paste it into the Feedotter input labeled **Client Code.**

#### Select an Owner User ID

This can be any user in your Omeda account.  Alternatively, you may wish to create a dedicated user as Omeda tends to send a large number of test emails and notifications to this user.

{% hint style="info" %}
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
  {% endhint %}

At this point you should have the Feedotter form looking like below with your details filled in.

<figure><img src="https://2086102864-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIdHBGk8cqznUpEqm5g1U%2Fuploads%2FU50PzlyBT3JsOSju59Zu%2Fimage.png?alt=media&amp;token=4c82d565-1428-48f4-9b6a-ee291bf426c3" alt=""><figcaption></figcaption></figure>

Click **Save**

On the following screen, next to your newly created Omeda Connection click the **Test** button.  Ensure it returns a success message.  If it fails, please review the permissions of your API Key and the Owner User.

***

## Part 2. Unique Newsletter Settings

Once your connection is setup you will need to configure unique Omeda settings for each newsletter.  This is how you define the Omeda Audience Query, Deployment Type, and other Omeda specific sending details.

For a given newsletter navigate to the Newsletter Details page.  It will look similar to this:

<figure><img src="https://2086102864-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIdHBGk8cqznUpEqm5g1U%2Fuploads%2FIK1DblZZigjHthwqjOyT%2Fimage.png?alt=media&amp;token=18329cb2-a30d-4852-af10-4b3a49bed815" alt=""><figcaption></figcaption></figure>

* Click the **Newsletter Default Settings** button
* Click on **Integration**
* Select **Omeda** from the dropdown and click **Configure**&#x20;

On the page that follows you will establish DEFAULT settings for this specific newsletter to use.  These settings will be remembered and need only be entered one time during setup.

#### Newsletter Integration Settings

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.                    |

### Omeda 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.

#### Common Omeda 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 `<a href="">` 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.

#### Audience Attachment — Do Not Interrupt

Attaching a large audience to a deployment can take several minutes and in cases of busy Omeda sending times upwards of 10 minutes. &#x20;

Feedotter has specifically built an engine to support this and prevent failure.

In most cases audiences will attach quickly.

Here are the possible outcomes and how to handle/approach them:

1. Wait for audience to attach in UI, it completes in a minute or two, job completes and shows the success message.
2.

> ⚠️ **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.

### Omeda deployment staggering and automatic retry&#xD;&#x20;&#xD;

Omeda's API can reject deployment requests that arrive within milliseconds of each other. This mostly affects high-volume accounts that publish several newsletters to Omeda at the same moment.&#x20;

FeedOtter guards against it. Before each newsletter creates its deployment in Omeda, FeedOtter waits a random delay of 0 to 3 seconds. That spreads simultaneous publishes apart so they don't reach Omeda at the same instant.

If Omeda still rejects the deployment, FeedOtter waits a random 3 to 8 seconds and tries again, up to 3 attempts in total. Each retry is logged in the campaign's history, for example: "Omeda rejected the deployment (attempt 1 of 3). Retrying in 5 seconds..."&#x20;

This allows everyone to see what happened. If a retry succeeds, the send carries on normally and the only effect is a few seconds of extra delay. If all 3 attempts fail, the campaign reports Omeda's error via email.
