> 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/automations/getting-started/eloqua-sending.md).

# Eloqua Sending

{% hint style="info" %}
If you haven't integrated your ESP in the settings yet, it's best to do that before finalizing your automated campaign. [Click here to learn how.](/integrations/eloqua.md)
{% endhint %}

### Finalize Your Eloqua Automation Settings <a href="#headline-60-20978" id="headline-60-20978"></a>

When you are within your automated campaign, select the **Integration** tab on the left sidebar.&#x20;

<div align="left" data-with-frame="true"><figure><img src="/files/XQ6HBYaM2Zf5xenN69F3" alt=""><figcaption></figcaption></figure></div>

Click Connect, then you will see this:

<div align="left" data-with-frame="true"><figure><img src="/files/UcEMHegRkBVbsxNUs5hV" alt=""><figcaption></figcaption></figure></div>

Choose the Eloqua Connection previously established.&#x20;

**FeedOtter uses Simple Email Campaigns to automate sending with Eloqua.** To learn about advanced settings for Canvas Email, please follow this link:

{% content-ref url="/pages/FRKovdBE6HMYQguVOG3I" %}
[Updating Eloqua Canvas Email](/integrations/eloqua/faq/updating-eloqua-canvas-email.md)
{% endcontent-ref %}

You should see **Segments** appear. **Segments** is the list of people who will receive your email. Eloqua only allows you to select one.

You can paste in the exact name of the segment and click **Lookup.** Select the segment to the right to select.  We strongly recommend creating a "test segment" or "internal segment" that contains one or more test emails. This will allow you to test the full Eloqua send process with internal stakeholders.  This segment can be changed at a later date when you are ready to send to the masses.

### Choose your **Email Groups**

This allows you to control pre-pending and appending Eloqua header and footer details to your FeedOtter emails. Some customers prefer to use an Eloqua dynamic content block for the footer which works as well. To do this, the user would edit the FeedOtter html template code and insert their Eloqua Dynamic Content token in the desired place, footer, etc.

### Save and Go! <a href="#headline-934-24943" id="headline-934-24943"></a>

Now you are ready to send out your Eloqua RSS Email Campaign. Once you've filled out the required settings, click Save Settings and Start Campaign.\
Your Automated Email will appear in the Campaign blocks and will send according to the sending schedule you made in your Automated Email.

### Advanced Eloqua RSS Email Options <a href="#headline-937-24943" id="headline-937-24943"></a>

Under the **Email Groups** information, there are **Advanced Options** to select if you have these setup. Please email our team if you have questions on these settings or ask your Eloqua contact.&#x20;

After activation, you can monitor and manage your automation from either the **Automations** dashboard or the **Automation Details** page.&#x20;

{% content-ref url="/pages/qpMKtJKyYL08DaTQAjQV" %}
[Automation Details](/automations/automation-details.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.feedotter.com/automations/getting-started/eloqua-sending.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.