Quantcast

Agency Secrets: How much should a GDPR/CCPA/PECR-Compliant Cookie Banner really cost you?

Feb 1, 2025

Warning: Are You Being Overcharged by Your Marketing Automation Agency?

If you’ve been billed or quoted more than $1500, or if the work took more than 6-24 hours (2-3 working days) by a marketing automation agency, you might be paying far more than you should.

Contact me urgently—you’re likely being overcharged, and I can help.

At the bottom of this page, you’ll find a real-life scenario with a detailed breakdown of all tasks, exactly how long they should take, and the fair costs associated with them.

Save yourself significant budget by following this step-by-step guide for your Eloqua developer and web team. It explains how to stop Eloqua tracking for users who opt out of tracking cookies—without overpaying for unnecessary services.

As with all my guides, I’ve included the true resource costs and time estimates. If you need this work done, get in touch with me for a more competitive quote. Let me help you get the job done efficiently and affordably.

Greg Staunton

Why Should You Block Eloqua Cookies with a Cookie Opt-Out Feature?

 

With privacy regulations like GDPR, CCPA, and PECR, websites need to give users the ability to opt out of cookies—including marketing cookies like those set by Eloqua.

If your website uses Eloqua for marketing automation and data collection, you must have a cookie opt-out solution to stay compliant with privacy laws.

This post will explain three methods to block Eloqua cookies when users choose to opt out:

  1. JavaScript Method – Deletes Eloqua cookies when users opt out.
  2. Server-Side Method – Prevents Eloqua cookies from being stored in the first place.
  3. Google Tag Manager (GTM) Method – Uses GTM to block Eloqua scripts from loading based on user consent.

Each of these methods includes a cookie opt-out banner, giving users control over their cookie preferences.

1. JavaScript Method: Deleting Eloqua Cookies When Users Opt-Out

 

How the JavaScript Cookie Opt-Out Method Works

In this method, Eloqua cookies are deleted from the user’s browser when they opt out. While this approach is straightforward, it may not be fully compliant with privacy laws like GDPR because it doesn’t prevent cookies from being set initially. It only removes them after the fact.

 

Why This Method Might Be Ideal for Your Website
  • Easy to implement without needing server-side changes.
  • Users can immediately delete Eloqua cookies after opting out.
  • Great for small businesses or websites with simpler setups that don’t want to modify server-side configurations.

This method is particularly good for quick fixes when you need something fast and low-maintenance without diving into more complex configurations.

Pros: Easy to implement, does not require server changes.
Cons: Cookies may still be set before deletion, which is not fully GDPR-compliant.

Step-by-Step Guide for JavaScript Cookie Opt-Out Implementation

 

Steps for the Website Manager
  1. Add the Cookie Banner to your website before </body>.
  2. Test if the banner appears for new users.
  3. Verify that clicking “Opt-Out” deletes Eloqua cookies.

 

Steps for the Eloqua Developer
  1. Identify the Eloqua cookies used on the site.
  2. Ensure that the script is correctly deleting these cookies.
  3. Work with the website manager to confirm compliance with regulations.
JavaScript Cookie Opt-Out Banner for Eloqua Cookies



<div id=“cookie-banner-js” style=“position: fixed; bottom: 0; width: 100%; background: #222; color: #fff; padding: 10px; text-align: center; display: none;”> This site uses cookies to improve user experience.


 <button id=“accept-js” style=“background: green; color: white; padding: 5px 10px;”>Accept</button>


<button id=“optout-js” style=“background: red; color: white; padding: 5px 10px;”>Opt-Out</button>


</div>





document.addEventListener(“DOMContentLoaded”, function() {
let consent = localStorage.getItem(“cookieConsentJS”);


if (!consent) document.getElementById(“cookie-banner-js”).style.display = “block”;


document.getElementById(“accept-js”).addEventListener(“click”, function() {
localStorage.setItem(“cookieConsentJS”, “accepted”);
document.getElementById(“cookie-banner-js”).style.display = “none”;
});


document.getElementById(“optout-js”).addEventListener(“click”, function() {
localStorage.setItem(“cookieConsentJS”, “optout”);
document.getElementById(“cookie-banner-js”).style.display = “none”;
deleteEloquaCookies();
});


function deleteEloquaCookies() {
document.cookie.split(“;”).forEach(function(cookie) {
let cookieName = cookie.split(“=”)[0].trim();
if (cookieName.includes(“ELOQUA”)) {
document.cookie = cookieName + “=; expires=Thu, 01 Jan 1970 00:00:00 UTC; path=/; domain=” + window.location.hostname;
}
});
}
});

2. Server-Side Method: Preventing Eloqua Cookies from Being Set

 

How the Server-Side Cookie Opt-Out Method Works

The server-side method ensures that Eloqua cookies are never set in the first place by blocking tracking requests before they reach the browser. This method offers the best solution for compliance with regulations like GDPR and CCPA because it prevents cookies from being set without consent.

 

Why This Method Might Be Ideal for Your Website
  • Fully compliant with privacy regulations like GDPR and CCPA.
  • Prevents Eloqua cookies from being set at all, instead of removing them later.
  • Ideal for websites that want full control over cookie management and are willing to modify server configurations.

This method is best for enterprises or websites that require the highest level of compliance and control.

Pros: Fully compliant with GDPR.
Cons: Requires changes to the server.

Step-by-Step Implementation

 

Steps for the Website Manager
  1. Add the Cookie Banner to your website.
  2. Test if it correctly blocks Eloqua when users opt out.
  3. Work with the Eloqua developer to ensure the server respects opt-out requests.

 

Steps for the Eloqua Developer
  1. Modify the server configuration to prevent Eloqua cookies from being set when cookieConsentServer = optout.
  2. Ensure API requests that track users are disabled for opted-out users.
  3. Test the setup using different browsers and devices.

Cookie Opt-Out Banner for Server-Side Method



<div id=“cookie-banner-server” style=“position: fixed; bottom: 0; width: 100%; background: #222; color: #fff; padding: 10px; text-align: center; display: none;”> This site uses cookies to improve user experience. <button id=“accept-server” style=“background: green; color: white; padding: 5px 10px;”>Accept</button> <button id=“optout-server” style=“background: red; color: white; padding: 5px 10px;”>Opt-Out</button> </div>





document.addEventListener(“DOMContentLoaded”, function() {
let consent = localStorage.getItem(“cookieConsentServer”);


if (!consent) document.getElementById(“cookie-banner-server”).style.display = “block”;


document.getElementById(“optout-server”).addEventListener(“click”, function() {
localStorage.setItem(“cookieConsentServer”, “optout”);
document.getElementById(“cookie-banner-server”).style.display = “none”;
fetch(‘/disable-tracking’, { method: ‘POST’ });
});
});

3. Google Tag Manager (GTM) Method: Preventing Eloqua Scripts from Loading

 

How the GTM Method for Cookie Opt-Out Works

The GTM method utilizes Google Tag Manager to block Eloqua scripts from loading if users have not given consent. This prevents Eloqua tracking altogether, making it the most effective way to comply with GDPR and CCPA.

 

Why This Method Might Be Ideal for Your Website
  • Best for GDPR compliance by preventing tracking altogether.
  • Easy to implement if you are already using Google Tag Manager (GTM).
  • Centralized control over all tags, making it easy to manage tracking across the website.

This method is perfect for businesses using GTM who want to block Eloqua cookies proactively, ensuring compliance without needing to modify server-side code.

Pros: Best for compliance, easy to manage.
Cons: Requires GTM knowledge.

Step-by-Step Implementation

 

Steps for the Website Manager
  1. Add the Cookie Banner to your website.
  2. Test if GTM prevents Eloqua scripts from loading when users opt out.
  3. Ensure GTM reads the cookieConsentGTM value from localStorage.

 

Steps for the Eloqua Developer
  1. Modify GTM triggers to check for cookieConsentGTM.
  2. Ensure Eloqua scripts only load when consent is accepted.
  3. Test using GTM Preview Mode.

GTM Cookie Opt-Out Banner



<div id=“cookie-banner-gtm” style=“position: fixed; bottom: 0; width: 100%; background: #222; color: #fff; padding: 10px; text-align: center; display: none;”> This site uses cookies to improve user experience. <button id=“accept-gtm” style=“background: green; color: white; padding: 5px 10px;”>Accept</button> <button id=“optout-gtm” style=“background: red; color: white; padding: 5px 10px;”>Opt-Out</button> </div>





document.addEventListener(“DOMContentLoaded”, function() { let consent = localStorage.getItem(“cookieConsentGTM”); if (!consent) document.getElementById(“cookie-banner-gtm”).style.display = “block”; document.getElementById(“accept-gtm”).addEventListener(“click”, function() { localStorage.setItem(“cookieConsentGTM”, “accepted”); document.getElementById(“cookie-banner-gtm”).style.display = “none”; }); document.getElementById(“optout-gtm”).addEventListener(“click”, function() { localStorage.setItem(“cookieConsentGTM”, “optout”); document.getElementById(“cookie-banner-gtm”).style.display = “none”; }); });

Comparison Table: Which Cookie Opt-Out Method is Right for Your Website?
 

Method Ease of Implementation Effectiveness Maintenance Compliance (GDPR, CCPA)
JavaScript (Deleting Cookies) Easy Moderate (Cookies may already be set) Low Not fully compliant
Server-Side Blocking Medium (Requires server access) High Medium Strong compliance
Google Tag Manager (GTM) Easy (If already using GTM) High (Prevents tracking entirely) Low Best compliance option

I recommend using the GTM method because it prevents tracking altogether, ensuring full compliance with privacy laws like GDPR and CCPA.

By incorporating the right cookie opt-out method for your website, you’ll ensure Eloqua cookies are blocked and your website remains compliant with the latest privacy laws.

If you need assistance in configuring one of these solutions, feel free to reach out!

Greg Staunton

Scenario Vs what your Eloqua agency should be doing with hours & costs
Scenario:

Jo, the marketing automation manager at ACME Inc., is overseeing the migration to Eloqua. The web team wants to implement a cookie opt-out solution to ensure compliance and better manage user consent. They’ve reached out to their marketing agency for advice and a quote on the time and costs involved.

Task Breakdown and Time Estimate:
  1. Website Manager Tasks (Not your Eloqua Agency):
    • Add the Cookie Banner to the website: 4-6 hours
    • Test if GTM prevents Eloqua scripts when users opt out: 2-4 hours
  2. Eloqua Developer Tasks:
    • Modify GTM triggers to check for cookieConsentGTM: 3-5 hours
    • Ensure Eloqua scripts load only when consent is accepted: 2-3 hours
    • Test using GTM Preview Mode: 3-4 hours
  3. Additional Management:
    • Program Manager Coordination and Oversight: 2-4 hours
Cost Breakdown:
  • CTO (at $200/hour): 1-2 hours → $200 – $400
  • Junior Developer (at $100/hour): 3-6 hours → $300 – $600
  • Senior Developer (at $150/hour): 5-8 hours → $750 – $1,200
  • Program Manager (at $150/hour): 2-4 hours → $300 – $600
Total Estimated Cost:
  • Low Estimate: $1,550
  • High Estimate: $2,800

These costs are based on the total hours estimated for each role, and they provide Jo with a clear idea of the budget and timeline for the cookie opt-out implementation.

Website Manager Tasks:
  • Add the Cookie Banner to your website:
    This step involves designing and implementing the cookie consent banner, which could take between 4-6 hours, depending on the design and any custom functionality needed (like geolocation targeting or language options).
  • Test if GTM prevents Eloqua scripts when users opt out:
    Testing the integration with GTM would take around 2-4 hours, given the need to ensure everything works as expected.
Eloqua Developer Tasks:
  • Modify GTM triggers to check for cookieConsentGTM:
    The senior or junior developer would need to modify and implement the GTM trigger. This could take between 3-5 hours, depending on familiarity with the system.
  • Ensure Eloqua scripts load only when consent is accepted:
    This will involve adjusting Eloqua’s implementation in GTM, which could take around 2-3 hours.
  • Test using GTM Preview Mode:
    Testing to ensure the trigger functions properly in preview mode and correcting any issues would take around 3-4 hours.
Additional Management:
  • Program Manager Tasks:
    Coordinating, monitoring progress, ensuring the project stays on track, and handling communication with other stakeholders may take about 2-4 hours, spread over multiple meetings or status updates.
Total Estimated Time:
  • Junior Developer: 3-6 hours
  • Senior Developer: 5-8 hours
  • Program Manager: 2-4 hours
  • CTO (if needed for oversight): 1-2 hours

Total: Around 16-24 hours (2-3 full workdays), considering typical development time, testing, and project management.

These estimates could change based on the specifics of the website, testing complexity, and the team’s familiarity with GTM and Eloqua.

Looking for some Eloqua help?

Schedule a call 📅

Submit a Comment

Your email address will not be published. Required fields are marked *

error: Content is protected !!