Eloqua Email API

Author: b | 2025-04-24

Collect delivery event data for specific email using Eloqua API. 0. Unsubscribe in rxjs. 0. Override email exclusions in Eloqua. 0. Eloqua's update event API endpoint overwrites

Email Metrics Retrieval with Eloqua API

API-fy Your Eloqua: A Beginner's Guide, Part 1Eloqua のユーザー インターフェイスを使用すると、マーケティング担当者は複雑なプロセス、統合、カスタム レポートを構成できるため、デジタル キャンペーンにとって価値のあるツールになります。しかし、これがこれらのメカニズムにアクセスする唯一の方法ではありません。Eloqua のオープン API は、まったく新しいレベルのマーケティング自動化機能を解放し、複雑なタスクを実行し、他のアプリケーションとシームレスに統合できるようにします。新しいリードをキャンペーンに自動的に追加したり、顧客データに基づいてメールをパーソナライズしたり、キャンペーン活動を外部ダッシュボードに同期したりすることを想像してみてください。これらすべてが手動介入なしで行われます。API を初めて使用する場合は、この記事で基本的な概念と、それが Eloqua にどのように適用されるかを詳しく説明します。これらの API 原則は、他の多くのツールにも適用できます。APIとは何ですか?API (アプリケーション プログラミング インターフェイス) は、アプリケーション間の仲介者として機能します。レストランのメニューと似ています。 API はメニューとして機能し、利用可能なオプションとその注文方法 (データ エンドポイントと関数) をリストします。 API を使用して注文を送信し、Eloqua 内でデータをリクエストしたりアクションを実行したりします。ここで、Eloqua でメインコースを注文し、それを別のシステムのサイドと組み合わせたいとします。この状況では、API はプラットフォーム間のメッセンジャーとして機能します。この通信が行われる主な方法は 2 つあります。API 呼び出しはリクエストに依存して双方向通信を促進します。アプリケーションはデータを要求することができ (サーバーからメニューを取得するなど)、場合によってはデータを変更することができます (注文するなど)。返信（あなたの注文）はレスポンスとして返ってきます。Webhook はイベント駆動型で、主に一方向です。アプリケーションはデータ (注文の準備ができたという通知など) を送信しますが、応答は期待しません。API で何ができるのでしょうか?Eloqua では、API 呼び出しと Webhook の両方で、REST (REpresentational State Transfer) と呼ばれる基盤となるアーキテクチャが使用されます。 REST は、アプリケーションが HTTP リクエスト (GET、POST、PUT、DELETE など) とレスポンスを使用して通信するためのルールを定義します。これらのリクエストは、質問したり、指示を与えたりするものです。 CRUD (Create、Read、Update、および Delete の略) について聞いたことがあるかもしれません。これらは、新しい連絡先レコードの追加や既存の連絡先レコードの編集など、データに対して実行できる基本的なアクションです。 REST API は多くの場合、CRUD アクションごとに特定の HTTP メソッド (読み取りの場合は GET、作成の場合は POST、更新の場合は PUT、削除の場合は DELETE) を使用した CRUD 操作を使用します。 REST は CRUD だけに限定されないことに注意してください。より複雑なタスクを処理できるようになります。私たちの目的のために、私たちはこれらの HTTP メソッドに固執します。Eloqua の API の可能性を探るOracle は、Eloqua 機能を拡張するために次の API を提供しています。アプリケーションAPIバルクAPIレポートAPIどの API を使用する必要がありますか?どの API を活用するのが最適かを決定する重要な機能がいくつかあり、複数の API を使用するのが一般的です。各 API が特定のニーズにどのように対応できるかを見てみましょう。アプリケーションAPIアプリケーション API (または REST API) は、個々のレコードに対する CRUD 操作のための汎用インターフェイスです。小規模なデータ転送やリアルタイムのやり取りに最適です。REST API 関数の良い例は、Eloqua フォーム送信アプリです。連絡先レコードがキャンバス上のアプリ ステップに到達すると、POST リクエストが起動され、マップされた値がフォーム データの特定のエンドポイントに送信されます。次に、Eloqua は応答 (フォーム送信データ) をアプリに送り返すことで、フォーム データの作成を確認します。REST API は基礎となるアーキテクチャであるため、Bulk API および Reporting API の基盤でもあります。バルクAPIBulk API (または REST 内の一括操作) は、REST API を使用して、操作するレコードのリストを含む単一のリクエストを送信する手法です。これは、大量のデータに対するアクションを効率的に実行するのに理想的です。 Salesforce 統合アプリケーションは、Bulk API を使用して、Eloqua で連絡先レコードを作成および更新します。この同期を維持するために、Eloqua は定期的に Salesforce データのバッチを自動的に取得します。 Eloqua はバッチごとに、変更されたレコードのデータセットを含む GET リクエストを実行します。レポートAPIReporting API (または REST 上の OData) は、データのクエリ、フィルター、操作の標準化された方法を定義するプロトコルです。この API は Eloqua Insight へのブリッジとして機能し、Insight データ ウェアハウスから直接データを取得できるようにします。この API を使用すると、Insight サブジェクト領域からメトリクスと属性を、Tableau、Power BI、Oracle Analytics などの好みのビジネス インテリジェンス ツールに取り込むことができます。

Eloqua: API: Getting Started with Eloqua's API

Between the and to a text file.Add -----BEGIN CERTIFICATE----- at the beginning of the file.Add -----END CERTIFICATE----- at the end of the file.Save and change the file extension to .cer.Configuring Eloqua in Oracle Identity Cloud ServiceUse this section to register and activate the Eloqua app and to enable provisioning for Eloqua. You can then assign users or groups to Eloqua and start the user provisioning process.Note: The Synchronization feature is currently not supported for Eloqua. However, you can manually import user accounts from Eloqua in Oracle Identity Cloud Service by using a flat file. For details, see the "Creating a Flat File for Manually Importing User Accounts from Eloqua" section.Registering and Activating the Eloqua ApplicationAccess the Oracle Identity Cloud Service administration console, select Applications, and then click Add.Click App Catalog.Search for Eloqua, and then click Add.In the App Details section, enter the Identity Provider ID, and Site ID for Eloqua. The Identity Provider ID and Site ID are located in the SP metadata that you downloaded in the “Configuring an Identity Provider” section.Verify that the Display in My Apps check box is selected, and then click Next.Click Upload, locate the signing certificate that you converted to PEM format in the "Saving the X509 Certificate in PEM Format" section, and then click Open.Click Next to enable provisioning for Eloqua. See the "Enabling Provisioning for Eloqua" section.After you enable provisioning, click Finish. Oracle Identity Cloud Service displays a confirmation message.Click Activate, and then click Activate Application. Oracle Identity Cloud Service displays a confirmation message.Enabling Provisioning for EloquaUse this section to enable provisioning for managing user accounts in Eloqua through Oracle Identity Cloud Service.On the Provisioning page, select Enable Provisioning.Use the table to enter values for establishing a connection with Eloqua through Oracle Identity Cloud Service:This table lists the parameters that Oracle Identity Cloud Service requires to connect to Eloqua.ParameterValueSite Name\Administrator UsernameEnter the value in the "Site Name\Administrator Username" format. In this format, replace Site Name with the company name that you specified while logging in to Eloqua. Replace Administrator Username with the Eloqua service account user name. For example: "idcsApp\example.username"Administrator PasswordEnter the Eloqua service account password.Host NameEnter the host name of the server that is hosting Eloqua. For more information on determining the host name, see the Determining base URLs section in REST API for Oracle Eloqua Marketing Cloud Service.Click Test Connectivity to verify the connection with Eloqua. Oracle Identity Cloud Service displays a confirmation message.To view predefined attribute mappings between the user account fields defined in Eloqua and the corresponding fields defined in Oracle Identity Cloud Service, click Attribute Mapping, and then click OK.Note: To add a new attribute for provisioning, click Add Attribute, specify the attributes in the User and

Email dispatch from Eloqua using the REST API (Eloqua 10).

Before You BeginIntroductionThis document describes how to configure Oracle Identity Cloud Service to provide Single Sign-On (SSO) using SAML and provisioning for Oracle Eloqua.About EloquaOracle Eloqua enables marketers to plan and execute campaigns while delivering a personalized customer experience for their prospects.After integrating Eloqua with Oracle Identity Cloud Service:Users can access Eloqua using their Oracle Identity Cloud Service login credentials.Users can start Eloqua using the Oracle Identity Cloud Service My Apps console.Admins can assign and revoke user access to the Eloqua app using the Oracle Identity Cloud Service administration console.What Do You Need?An Oracle Identity Cloud Service account with authorization rights to manage apps and users (Identity Domain Administrator or Application Administrator).An Eloqua account with authorization rights to configure federated authentication.An Eloqua service account (added to the Customer Administrator and Everyone security groups) to manage user accounts in Eloqua through Oracle Identity Cloud Service.Identity Provider metadata. Use the following URL to access the metadata: SSO for EloquaUse this section to configure SSO in Eloqua with Oracle Identity Cloud Service.Configuring an Identity ProviderLog in as an administrator to: the Settings icon.On the Settings page, click Users from the Users and Security section.Click the Single Sign-On menu, and then select Identity Provider Settings.On the Identity Provider Management page, click Upload Identity Provider from Metadata, and then follow the on-screen instructions.Enter a name for the identity provider settings, and then upload the Identity Provider metadata file that you downloaded in the “What Do You Need” section.Click Save. The uploaded IdP information appears.Click Edit at the bottom of the page. The Edit Identity Provider Details page appears.Verify that Protocol Binding is set to HttpPost.Select Sha256 from the Signature Algorithm drop-down list box.Verify that User Identity Location is set to The user identity is located in an assertion subject’s name identifier.Select Assertion contains the Username from the User object in the User Identity Mapping section, and then click Save. The Identity Provider Details page appears with the settings that you just configured.Click Download at the bottom of the page to download the SP metadata information. You need the following information from this file while configuring Eloqua in Oracle Identity Cloud Service.The entityID url in the metadata file has the following format: the metadata file sample:The Site Id of the entityID is 561407682.The Identity Provider ID of the entityID F568F44F86E94F398E04D797C33FDA51.The signing certificate in the metadata file appears as the X509Certificate value. Use this value to create the certificate file that you must upload later in the “Registering and Activating the Eloqua Application” section.Saving the X509 Certificate in PEM FormatUse this section to convert the X509Certificate value into a format that is suitable for Oracle Identity Cloud Service.In the SP metadata file, locate under .Copy the value. Collect delivery event data for specific email using Eloqua API. 0. Unsubscribe in rxjs. 0. Override email exclusions in Eloqua. 0. Eloqua's update event API endpoint overwrites

Email Metrics Retrieval with Eloqua API - tempmail.us.com

Apps.Click Eloqua. The Eloqua home page appears.On the Eloqua home page, confirm that the user that is logged in is the same for both Eloqua and Oracle Identity Cloud Service.This confirms that SSO that is initiated from Oracle Identity Cloud Service works.Verifying Service Provider Initiated SSO from EloquaAccess Eloqua at: Sign in with SSO or another account. You are prompted to sign in using your company credentials.Enter the Company name and click Sign In. The Oracle Identity Cloud Service Sign In page appears.Note: When there are multiple identity providers, select the appropriate identity provider, and then click Sign In.Log in using credentials for a user that is assigned to the Eloqua app. The Eloqua home page appears.On the Eloqua home page, confirm that the user that is logged in is the same for both Eloqua and Oracle Identity Cloud Service.This confirms that SSO that is initiated from Eloqua works.Verifying Identity Provider Initiated SLOOn the Oracle Identity Cloud Service home page, click the user name in the upper-right corner, and then select Sign Out from the drop-down list.Access the user profile in Eloqua, and then confirm that the login page appears.This confirms that SLO works and that the user is no longer logged in to Eloqua and Oracle Identity Cloud Sevice.Verifying Service Provider Initiated SLOOn the Eloqua home page, click the user icon in the upper-right corner, and then select Logout from the drop-down list.Click OK at the confirmation message that displays.Access the Oracle Identity Cloud Service My Console, and then confirm that the login page appears.This confirms that SLO works and that the user is no longer logged in to Eloqua and Oracle Identity Cloud Service.TroubleshootingUse this section to locate solutions to common integration issues.Known IssuesEloqua Service displays the error, "Your user is unknown."Cause: The email attribute sent to Oracle Identity Cloud Service during SSO doesn't match any existing user in Eloqua.Note: The above error message gets displayed when the debug mode is enabled. Error message when the debug mode is disabled: "Your request either didn't include a SAML response or the SAML response was malformed.”Solution: Check your SSO configuration and ensure that the user that you assign to the Eloqua app has an account in both Oracle Identity Cloud Service and Eloqua service with the same email address.Oracle Identity Cloud Service displays the message "You are not authorized to access the app. Contact your system administrator".Cause 1: The administrator revokes access for the user at the same time that the user tries to access the Eloqua app using Oracle Identity Cloud Service.Solution 1: Access the Oracle Identity Cloud Service administration console, select Applications, Eloqua, Users, and then click Assign to re-assign the user.Cause 2: The SAML 2.0 integration between

Email Metrics Retrieval with Eloqua API - Medium

Guest post from Victor Ho, Product Consultant. Victor and the product consulting team get involved when there are interesting business challenges to tackle, and creative configuration is needed.In this post, Victor looks at an advanced option for integrating with web forms and still maintaining full tracking when you must process, and alter, the form data on your own servers prior to Eloqua tracking.=================================We can’t emphasis enough the importance of integrating web forms with Eloqua.The obvious reason is to collect explicit data from the visitor to create/update a contact record in Eloqua for future marketing purposes. In the mean time, triggering automated processes such as a confirmation email or adding to a nurturing program.But more importantly, the form submission converts an “unknown” visitor on your website to a “known” visitor. This action allows Eloqua to tie all the online activities that we’ve been collecting to a contact record.This in turns increases your visibility into the online activities data as a whole.The goal here is to setup web forms where ever appropriate on your website to increase the population of known visitors.Why Repost?There are four types of front end forms:1) Created and hosted by Eloqua2) Created externally, hosted by Eloqua3) Hosted externally, pointed to Eloqua4) Hosted externally, reposted to EloquaIn scenario 1 – 3, the conversion from an unknown to known visitor (In Eloqua language, this is called “profile association”) is done automatically because the Eloqua communicates directly with the visitor’s browser when he/she hits the “submit” button.In scenario 4, this is typically done if data needs to be manipulated by a third party before entering the Eloqua database. Here are some examples:A) you have a demo of your software and will need to generate a demo key that you then want to add into the form submit to Eloqua.B) You are collecting sensitive data such as credit card information; your web server will repost only the necessary contact data to Eloqua for marketing purposes, omitting any sensitive data in the mix.Writing a repost script to relay form data to a destination may sound like a very simple task for your IT

Eloqua: API: How to check Email Subscription Status of a

Team; but the most important piece of information in this form integration is the GUID value that resides in the Eloqua cookie within the visitor’s browser.We can summarize the conversion process with this equation:Email Address + Eloqua GUID = Known visitorHow?You will need an IT or Web resource to assist you with executing this process.Here is a step-by-step guide on how to deploy a form repost process.Eloqua Backend Configuration1) Create a backend form in Eloqua to receive data.By clicking on the “Integration Details” button, you will find all the necessary technical information you need for this process.You will need to create all the necessary backend form fields as the receptor for each data point in the repost.To facilitate testing in step (6), create the following 2 hidden fields:elqCustomerGUIDelqCookieWriteFrontend Web form Configuration2) Ensure the 2 lines of Eloqua tracking Script are present on the web page(elqCfg.js and elqImg.js).The purpose is to drop the Eloqua cookie onto visitor’s browser.3) Insert the 2 required hidden fields within the form tag of the form that you want to integrate with:Place holder hidden field to store the GUID value retrieved from the Eloqua CookieCopy the “elqFormName” field from the “Form Integration Fields” section. The value of this field is based on the HTML Name of the Eloqua backend form.4) Insert JavaScripts to retrieve GUID value that is stored in the Eloqua cookie.This section of code must go after the 2 lines of Eloqua Tracking Scripts.Purpose: This JavaScript function will execute on page load and store the GUID value retrieved into the “elqCustomerGUID” hidden form field.You will find the above JavaScript in the “Forms Detail” area shown in (2).The version illustrated above has been modified to utilize field “IDs” as target reference instead of using field name attribute.Here is demo web page on how to successfully retrieve the GUID value stored in the Eloqua cookie via JavaScript. form submission your web server should receive the “elqCustomerGUID” value + “elqFormName” value, along with the rest of the form fields.Important Note: Test thoroughly to ensure your web server is indeed receiving the elqCustomerGUID value.5) Write Server Repost Script. Collect delivery event data for specific email using Eloqua API. 0. Unsubscribe in rxjs. 0. Override email exclusions in Eloqua. 0. Eloqua's update event API endpoint overwrites