In our previous articles we have explore how Magic xpi Integration Platform can automate business processes in the Oracle Marketing Cloud using the Oracle Eloqua Marketing Cloud REST API 1.0 for Data Integration and Process Integration.
As discussed previously, Oracle offers the Oracle Eloqua Marketing Cloud Service as part of the Oracle Marketing Cloud in the Oracle CX Cloud. Oracle Eloqua Marketing Cloud Service offers capabilities for Web Marketing, Lead Management, Marketing Ops, Marketing Measurement, Targeting, Sales Enablement and Integration.
In this article, we will identify how Magic xpi Integration Platform can access the extended capabilities of the Oracle Eloqua Marketing Cloud REST API 2.0 for the same basic structures of Data Integration and Process Integration handled by the REST API 1.0.
The Magic xpi Integration Platform can access the Oracle Eloqua Marketing Cloud REST API 2.0 covers additional capabilities for Accounts, Contacts, Custom Objects, and Custom Object Data. In addition, the 2.0 API introduces capabilities for Account Groups, Campaigns, Email Deployment, External Activities, External Assets, External Asset Types, Visitors, and Visitor Profile Fields.
Adding to the capabilities of the Eloqua Cloud Marketing API 1.0, the 2.0 API provides extended and enhanced capabilities for:
Accounts. As previously described, an Eloqua Account, also known as a company, is a data entity that contains explicit data around a customer account or prospective account in the Eloqua database. Along with contacts, accounts are used as building blocks for segments, and are central to account-based marketing. Magic xpi can post (create), delete, put (update), and get Eloqua Accounts in the Oracle Marketing Cloud (API 1.0). Magic xpi can get information about the Account Group memberships of specified Accounts in the Oracle Marketing Cloud (API 2.0). In addition, Magic xpi can post search results for up to 200 Eloqua Accounts by search id. The depth of the information may be complete or partial (API 2.0). While it may seem counter-intuitive that a POST is used to retrieve a list of accounts, one should keep in mind that the API is essentially getting the list of accounts and then posting the search results, therefore this API functionality is ultimately classified as a POST activity.
Contacts. As previously described, an Eloqua Contact is a data entity that contains the explicit data around an individual person in the database. Contacts (and associated accounts) are used as the primary building blocks for segments. Contact information can be derived from email responses or form submissions, from website visits, event registrations or via external (non-Eloqua) activities. Magic xpi can post (create), delete, put (update), and get Eloqua Contacts in the Oracle Marketing Cloud (API 1.0). Magic xpi can get a list of the Contact Lists that a specified Contact belongs to (API 2.0). In addition, Magic xpi can post search results for up to 200 Eloqua Contacts by search id. The depth of the information may be complete or partial (API 2.0). For the same reasons discussed above in regards to accounts, the search results activity are regarded as a POST rther than a GET.
Custom Objects and Custom Object Data. As previously stated, an Eloqua Custom Object contains custom records beyond the standard contact and account records. Magic xpi can post (create), delete, put (update), and get Eloqua Custom Objects and post (create), and get Custom Object Data in the Oracle Marketing Cloud (API 1.0). With the 2.0 API, Magic xpi can also manage Custom Objects permissions and Custom Object Data permissions in Oracle Eloqua Marketing Cloud as well as delete and update Custom Object Data (with permissions) (API 2.0).
While these capabilities discussed here are essentially enhancements to the capabilities offered Magic xpi Integration Platform via the Oracle Eloqua Marketing Cloud API 1.0, in our next entry we will explore enhanced capabilities for Account Groups, Campaigns, Email Deployment, External Activities, External Assets, External Asset Types, Visitors, and Visitor Profile Fields.
While all of these API capabilities are useful, the lack of campaign management in the API 1.0 was particularly difficult. In Eloqua, campaigns are central to the management of marketing processes and constitute a fundamental element of workflow and activity for the marketing department using Eloqua Marketing Cloud.
We have been particularly eager to see these capabilities added to the REST API 2.0 because marketing Campaigns are at the center of the Eloqua application. Indeed, Eloqua campaigns are comprised of the various different elements that we have already discussed such as segments, emails, landing pages, microsites, contacts, accounts, etc.) that are used to perform a variety of functions. Because you can combine the different elements in a number of ways to customize your campaign flow, the campaign capabilities of the Eloqua Marketing Cloud REST API 2.0 will prove to be central to business process orchestration in the Oracle Eloqua Marketing Cloud.
oracle cloud integration
Oracle Eloqua Marketing Cloud
Oracle Eloqua Marketing Cloud Integration
Oracle CX Cloud
Oracle Marketing Cloud
Oracle Marketing Cloud Integration
Source: SANS ISC SecNewsFeed @ January 27, 2017 at 05:12AM