Service descriptions

Action services

Actions allow a marketer to add an action step to a campaign or program that is performed by an external system. For example, an action service could send contacts SMS messages, trigger a direct mailing, or register a contacts for a webinar. When contacts enter an action step, Eloqua calls out to the app, and the app responds by performing an action in an external system. The app then informs Eloqua that the process is complete and the contact moves on in the workflow. Read more about actions in the development guide and service registration instructions.

Learn more by watching the video

Decision services

Decisions allow a marketer to delegate a decision-making step in a campaign to an external system without having to bring the system's data into Eloqua. Decision services evaluate contacts using externally-held data, and determine whether the contacts meet the criteria. The service responds with yes or no to determine which path the contact should take through the campaign or program workflow. For example, a decision service could check if a contact exists in a CRM system, and sort the contacts accordingly. With Eloqua decision services, the data used in the decision never needs to be brought into Eloqua. Read more about decisions in the development guide and service registration instructions.

Learn more by watching the video

Feeder services

With feeders, developers can build apps that use data in third-party services to drive campaign and program membership. Feeders allow marketers to populate a campaign or program with contacts or custom objects from an external system, automatically importing the contacts or custom objects into Eloqua and adding them to a campaign or program. Read more about feeders in the development guide and service registration instructions.

Note: For marketers using Eloqua's campaign canvas, feeder services are referred to as AppCloud Audiences.

Learn more by watching the video

Content services

Content allows marketers to source pieces of content in Eloqua emails and landing pages from an external source. This is the new and improved version of Eloqua's cloud components framework, and it includes many improvements such as asynchronous bulk processing (for emails), the ability to fully test the content service within Eloqua, and design-time interaction with the email and landing page editors. Read more about content in the development guide and service registration instructions.

Menu services

The AppCloud menus service is all about context. AppCloud menus enable a marketer to launch an externally-hosted application from within Eloqua via a menu dock. This menu dock floats on the right side of the screen in the campaign canvas or asset editor screens. Read more about menus in the development guide and service registration instructions.

Firehose services

The firehose service acts as a web hook and notifies an external system when a marketer performs an action in Eloqua. For example, when a marketer creates a campaign or edits an email, Eloqua can call out to the third-party with the update. Read more about the firehose service in the development guide and service registration instructions.