What are the main components of the 4Comply Eloqua Cloud App?

The app consists of Feeders (RTA, RTP, RTU, RTBF Email Confirmed), Actions (Send Requested Data, Create Consent), and Decision steps (Validate 4Comply Permission). These components work together to automate privacy request handling and consent management within Eloqua. [Documentation]

How does the app help with privacy compliance?

4Comply automates the process of managing consent, fulfilling privacy rights requests (such as access, rectification, erasure), and responding to regulatory inquiries. It centralizes preference management and provides an auditable trail for compliance with GDPR, CCPA, and other regulations. [Source]

What types of privacy rights requests does 4Comply support?

4Comply supports Right to Access (RTA), Right to Portability (RTP), Right to Update (RTU), and Right to Be Forgotten (RTBF) requests, automating the confirmation, fulfillment, and tracking of these requests within Eloqua. [Documentation]

How does 4Comply integrate with Oracle Eloqua?

4Comply integrates as a set of cloud apps within Eloqua's campaign and program canvas. Users can drag and drop Feeders, Actions, and Decision steps to automate privacy workflows. Configuration involves connecting your 4Comply Tenant ID and Secret Key to Eloqua. [Setup Guide]

What is the role of Feeders in 4Comply Eloqua Cloud App?

Feeders receive privacy rights requests (such as RTA, RTP, RTU, RTBF) after user identity confirmation via email. They trigger the subsequent actions in Eloqua to fulfill the request. [Documentation]

What do Actions do in the 4Comply Eloqua Cloud App?

Actions process the requests received by Feeders. They either send the requested data back to 4Comply for the user or create consent entries in 4Comply, updating permissions based on user input and regulatory requirements. [Documentation]

How does the Decision step work in 4Comply Eloqua Cloud App?

The Decision step, 'Validate 4Comply Permission,' checks if a contact in an Eloqua campaign has the required permission type and if the consent is still valid. This ensures only compliant contacts receive marketing communications. [Documentation]

Can I configure 4Comply for different privacy regulations?

Yes, 4Comply uses the Country Code field to determine which regulation (such as GDPR for France) applies to each consent entry, ensuring compliance with region-specific requirements. [Documentation]

What is required to install the 4Comply Eloqua Cloud App?

You need your 4Comply Tenant ID and Secret Key, which are available from your 4Comply Dashboard. These credentials are entered during the app configuration in Eloqua. [Setup Guide]

How do I configure Feeders and Actions for different privacy rights?

The configuration process is similar for all rights (RTA, RTP, RTU, RTBF). The main difference is the Trigger Action selected in 4Comply when setting up the webhook. Each right has a specific webhook action name. [Documentation]

What is the purpose of the 'Fulfillment Complete' field in Actions?

The 'Fulfillment Complete' field indicates whether the requested data can be sent to the user immediately. If checked, 4Comply sends the data right away; if not, it waits for an external process to complete fulfillment. [Documentation]

How does 4Comply handle consent creation and updates?

The '4Comply Create Consent' action creates a consent entry in 4Comply, with details such as Country Code, Permission Type, Consent Code, and Processing Purpose. This allows for granular, regulation-specific consent management. [Documentation]

How do I validate permissions before sending marketing emails?

Use the 'Validate 4Comply Permission' decision step in Eloqua to check if a contact has the necessary permission and if the consent is still valid before sending marketing communications. [Documentation]

What happens if the webhook configuration is not automatic?

If the webhook is not created automatically, you can manually copy the Webhook URL from Eloqua and add it to the Webhooks section in your 4Comply dashboard, specifying the correct action for each privacy right. [Documentation]

How do I map contact fields for privacy requests?

When configuring Feeders and Actions, you select the contact field to store the Request ID, which is used to track and fulfill the user's privacy request. [Documentation]

Can I use 4Comply with multiple privacy rights at once?

Yes, you can configure multiple Feeders and Actions for different rights (RTA, RTP, RTU, RTBF) within the same Eloqua campaign or program, automating the handling of various privacy requests. [Documentation]

How do I get support for the 4Comply Eloqua Cloud App?

You can contact 4Thought Marketing for support via their website or by using the contact information provided in the documentation. [Contact Us]

Who can benefit from using the 4Comply Eloqua Cloud App?

Organizations using Oracle Eloqua that need to comply with privacy regulations (GDPR, CCPA, etc.) benefit from 4Comply. This includes legal and compliance teams, marketing managers, and IT teams in industries such as financial services, healthcare, manufacturing, technology, and real estate. [Source]

What problems does 4Comply solve for Eloqua users?

4Comply addresses challenges such as managing consent and preferences, automating privacy rights fulfillment, ensuring regulatory compliance, and providing an auditable trail for privacy requests—all within Eloqua. [Source]

How does 4Comply help with GDPR and CCPA compliance?

4Comply centralizes preference management, automates consent and privacy rights handling, and provides documentation for regulatory audits, making it easier for organizations to comply with GDPR, CCPA, and similar laws. [Source]

What are some real-world examples of 4Comply in action?

4Thought Marketing has delivered privacy compliance and consent management solutions for clients in real estate (W. P. Carey), financial services (Cetera Financial Group), and manufacturing (Endress+Hauser Infoserve GmbH), demonstrating the app's effectiveness across industries. [Case Studies]

What feedback have customers given about 4Comply and related tools?

Customers have praised 4Thought Marketing's tools for their automation and ease of use. For example, Catalent highlighted the Eloqua Upload Wizard's ability to automate pre-processing and enrichment tasks, and Endress+Hauser Infoserve GmbH confirmed that the Eloqua Cloud App met all their requirements. [Testimonials]

Which industries have used 4Comply and 4Thought Marketing solutions?

Industries represented in case studies include real estate (W. P. Carey), financial services (Cetera Financial Group), and manufacturing (Endress+Hauser Infoserve GmbH). [Case Studies]

What types of companies use 4Thought Marketing's solutions?

4Thought Marketing serves clients across North America, Europe, Latin America, Asia, and Australia, including companies like FT, Fluke, Arrow, JLL, Intuit, VISA, Cetera, Catalent Pharma, VIAVI Solutions, Vertiv, Brady Corp, Morningstar, and more. [Clients]

How does 4Comply compare to generic compliance tools?

4Comply offers centralized preference management, seamless Eloqua integration, and an auditable compliance trail, providing a more robust and tailored solution than generic compliance tools. [Source]

Why choose 4Thought Marketing for privacy compliance in Eloqua?

4Thought Marketing provides tailored solutions, innovative features, and seamless integrations for privacy compliance, advanced segmentation, and marketing automation optimization, with proven success across multiple industries. [Source]

What makes 4Comply unique for Eloqua users?

4Comply is designed specifically for Eloqua, offering deep integration, automated privacy workflows, and support for multiple privacy regulations, making it a comprehensive compliance solution for Eloqua users. [Source]

How does 4Comply support auditable compliance?

4Comply provides an auditable trail of consent and privacy rights requests, making it easier for organizations to demonstrate compliance during regulatory audits. [Source]

What are the steps to get started with 4Comply Eloqua Cloud App?

To get started, obtain your Tenant ID and Secret Key from the 4Comply Dashboard, install the app in Eloqua, and configure Feeders, Actions, and Decision steps as needed for your privacy workflows. [Setup Guide]

Where can I find more documentation and resources for 4Comply?

Comprehensive documentation and resources are available on the 4Thought Marketing website and the 4Comply Eloqua Cloud App documentation page. [Documentation]

4Comply Eloqua Cloud App Documentation

Table of Contents

Introduction

4Comply is a privacy compliance solution that enables companies to manage consent and permissions, fulfill privacy rights requests and respond to privacy inquiries from regulators. The 4Comply Eloqua Cloud apps seamlessly integrate with Eloqua on the campaign and program canvas.

The following document explains how each of the 4Comply apps works and how to implement them in Oracle Eloqua.

The suite of apps is composed of the following items:

Feeders:

• RTA Email Confirmed
• RTP Email Confirmed
• RTU Email Confirmed
• RTBF Email Confirmed

Actions:

• RTA Send Requested Data
• RTP Send Requested Data
• RTU Send Requested Data
• RTBF Send Requested Data
• 4Comply Create Consent

Decisions:

• Validate 4Comply Permission

Initial Configuration

Before installing the 4Comply Eloqua Cloud Apps, you must oobtain the Tenant ID and the Secret Key provided by your 4Comply Dashboard at https://dashboard.4comply.io

Get keys from 4Comply Dashboard

1) Go to the Settings section in the dashboard

2) Copy the Tenant ID and the Secret Key

After that, please follow these instructions to set up this cloud app in your Oracle Eloqua instance.

Log in to Oracle Eloqua.
Click on Get App below to install.

NOTE: If prompted to log again, please do so.

In the next screen, click “Accept and Install”

Configure 4Comply keys in Eloqua

1) Go to the Settings section in Eloqua

2) Go to Apps

3) Search for “4Comply Services” and click on it

4) Go to the Configure Section

5) Copy the 4Comply Tenant ID and the Secret Key in the corresponding fields and Save

Eloqua Feeders

Pre-Process

Every time a 4Comply form has been submitted for any of its rights (RTA, RTP, RTU or RTBF) an email is sent to the user who have requested any of the rights. Once the user confirms its identity by clicking on the email link provided by 4Comply, the request is sent to Eloqua, therefore Eloqua will provide the information requested to 4Comply and this one to the user.
Commonly the Feeders and the Actions are used together, the Feeder will receive the request and then the Action will provide the data to 4Comply, it could exist a process in between the user request and the time Eloqua provides the information required, but, for the guidance process Feeders and Actions will be one after the other.

Program example:

Feeder Configuration

Configure “RTA Email Confirmed” Feeder

Drag and drop the feeder in the canvas, double click on it and go to configure

In the following screen one contact field must be selected to store the Request Id, this field is used to store the Id of the request created by the user when the form was submitted, then the Request Id value will be used by the Cloud Action to send the requested data back to 4Comply

If the section Configure 4Comply keys in Eloqua has been configured the Webhook will be created automatically. In case it needs to be configured manually copy the Webhook URL and paste it in the Webhook configuration in 4Comply. The Webhooks option can be found on the left-hand side menu at the bottom, click on it and then select Add New as shown below

Once Add New has been clicked the URL copied from Eloqua must be placed in the Webhook URL field. Provide a name to the webhook and select the corresponding action, for this specific case, the action for RTA Email Confirmed must be RTAEmailConfirmedWebhook and finally click on submit.

Configure Additional Rights for Email Confirmed Feeders
The process to configure feeders and webhooks for other rights (RTP, RTU or RTBF) is exactly the same as the one shown for RTA in the previous reference. The unique difference in the process is the Trigger Action selected in 4Comply when the webhook is configured.
The following list of Trigger Actions can be used to configure webhooks for RTP, RTU or RTBF.
• RTP Trigger Action = RTPEmailConfirmedWebhook
• RTU Trigger Action = RTUEmailConfirmedWebhook
• RTU Fulfillment Trigger Action = RTUReadyToFulfillWebhook
• RTBF Trigger Action = RTBFEmailConfirmedWebhook

Eloqua Actions

Introduction

Eloqua has 2 different types of cloud actions to work with 4Comply:

• Type 1: Cloud Action to send the data requested by the user (RTA, RTP, RTU or RTBF)
• Type 2: Cloud Action to create consent from Eloqua

The first type is just to return to 4Comply the data that a user has requested via 4Comply, these actions usually work together with the feeders (previous topic).

The second type will create a consent entry in 4Comply and its corresponding permissions based on a combination of field values.

Action Configuration

Configure “RTA Send Requested Data” Action (Type 1)

- Drag and drop the action in the canvas, double click on it and go to configure

Select the contact field where the Request ID has been stored by the feeder (previous topic). This value will work to identify which user requested the information.

Then the fields to be sent to the user who requested the data must be selected

The last step is to determine if the Fulfillment Complete field should be checked. By checking this field 4Comply will know that the data can be sent to the user immediately, if this field is not checked then 4Comply will wait for an external process to determine when the fulfillment has been completed. Is recommended to mark the checkbox. Finally save the configuration.

Configure Additional Rights for Send Requested Data Actions

The process to configure actions other rights (RTP, RTU or RTBF) is exactly the same as the one shown for RTA in the previous reference. The unique difference is that the action for RTBF does not require a fulfillment field.

Configure “4Comply Create Consent” Action (Type 2)

This action will be in charge of creating a consent entry in 4Comply, each consent entry could have derived consent entries associated, this is dependent on the values sent in Country Code and Permission Type.

Country Code: Will determine the regulation to use, for example, France (FR) will use the GDPR regulation.

Permission Type: Will contain the explicit permission to be used in conjunction with the regulation determined by the Country Code.

Different combinations of the fields mentioned before will reflect different results in 4Comply.

A Country Code = “FR”, Permission Type = “Process Data”, Consent Code = “no” and Email Address = “[email protected]” and Processing Purpose = “CRM Record without consent” will generate the following entries in 4Comply.

Consent entries

The steps to configure this action are:

Drag and drop the action in the canvas, double click on it and go to configure

Drag and drop the action in the canvas, double click on it and go to configure

Using Decision Steps

Introduction
The decision step in Eloqua, will verify in 4Comply if the contact that is in the Eloqua campaign has the corresponding Permission Type and if the expiration date is still valid to receive a marketing email.
The Permission Type configured in the decision step must match the values in 4Comply.
Decision Configuration
Configure “Validate 4Comply Permission” Decision
- Drag and drop the action in the canvas, double click on it and go to configure

In the following screen it is required to configure 2 fields, the Webhook ID and the Permission Name. If the section Configure Configure 4Comply keys in Eloqua has been configured the Webhook will be created automatically. In case it needs to be configured manually copy the Webhook URL.

Then paste the Webhook URL in the Webhook configuration in 4Comply. The Webhooks option can be found on the left-hand side menu at the bottom, click on it and then select Add New as shown below.

Once Add New has been clicked the URL copied from Eloqua must be placed in the Webhook URL field. Provide a name to the webhook and select the corresponding action, for this specific case, the action for RTA Email Confirmed must be BulkRequestPermissionsDelivery and finally click on submit.

Copy the Webhook ID from the URL

Go back to Eloqua an open up the decision configuration screen. Copy the Webhook ID in the corresponding field and fill out the Permission Type.

Make sure the Permission Type matches the permissions in 4Comply. These can be found in the left-hand side menu under the Regulations option.

Frequently Asked Questions

Product Overview & Features

What is the 4Comply Eloqua Cloud App?