Greg’s straight answer
If you are being quoted thousands for a basic Eloqua cookie opt-out setup, slow down and ask what is actually being built. For a controlled implementation, the sensible range is usually around $1,500 to $2,800 depending on the website, GTM setup and testing requirements. The cleanest route is normally not deleting cookies after the fact. It is stopping Eloqua from loading until the visitor gives consent. That is the bit that matters.
Why Eloqua cookie opt-out is not just “adding a banner”
The banner is only the visible part. The actual job is deciding which tags require consent, preventing those tags from loading too early, preserving essential form behaviour and proving that the setup works for accepted, rejected and changed consent states.
For a controlled website and a reasonably tidy GTM container, I would expect the implementation to land between $1,500 and $2,800. The number moves with the number of domains, consent categories, existing tag quality, regional rules and the depth of browser and device testing.
This guide compares three practical approaches:
- JavaScript deletion - removes Eloqua cookies after opt-out.
- Server-side consent handling - blocks tracking requests before they reach the browser.
- GTM consent-gated loading - allows Eloqua tags to load only after the required consent.
Practical compliance note: This is implementation guidance, not legal advice. Your privacy or legal team should define the consent categories, regional requirements and lawful basis. The technical team’s job is to make the agreed policy work reliably.
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 straightforward, it does not prevent cookies or tracking requests from being created initially. It only removes browser cookies after the fact.
Where this method can fit
- Easy to implement without needing server side changes.
- Users can immediately delete Eloqua cookies after opting out.
- Useful as a temporary fallback while a proper consent-gated setup is prepared.
This is the weakest of the three routes because tracking may already have happened before deletion. Treat it as a pragmatic fallback, not the default design for a new implementation.
Pros: Easy to implement, does not require server changes.
Cons: Cookies may already have been set and tracking
requests may already have fired before deletion.
Step by step guide for JavaScript cookie opt out implementation
Steps for the website manager
- Add the cookie banner to your website before
</body>. - Test if the banner appears for new users.
- Verify that clicking “Opt Out” deletes Eloqua cookies.
Steps for the Eloqua developer
- Identify the Eloqua cookies used on the site.
- Ensure that the script is correctly deleting these cookies.
- Work with the website manager to confirm compliance with regulations.
JavaScript cookie opt out banner for Eloqua cookies
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.
Where this method can fit
- Provides stronger technical control by blocking tracking before it starts.
- 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: Strong control because tracking is prevented
before it reaches the browser.
Cons: More infrastructure-heavy and may require
server, application and privacy-platform changes.
Step by step implementation
Steps for the website manager
- Add the cookie banner to your website.
- Test if it correctly blocks Eloqua when users opt out.
- Work with the Eloqua developer to ensure the server respects opt out requests.
Steps for the Eloqua developer
- Modify the server configuration to prevent Eloqua cookies from being set when
cookieConsentServer = optout. - Ensure API requests that track users are disabled for opted out users.
- Test the setup using different browsers and devices.
Cookie opt out banner for server side method
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 is usually the practical route
- Best for GDPR compliance by preventing tracking altogether.
- Easy to implement if you are already using Google Tag Manager (GTM).
- Centralised control over all tags, making it easy to manage tracking across the website.
For a typical Eloqua website already using GTM, this is normally the cleanest option. It keeps consent logic visible in the tag-management layer and prevents Eloqua from loading until the required consent state exists.
Pros: Prevents Eloqua loading before consent and is
relatively easy to audit in GTM.
Cons: Requires disciplined GTM governance and proper
testing of consent updates.
Step by step implementation
Steps for the website manager
- Add the cookie banner to your website.
- Test if GTM prevents Eloqua scripts from loading when users opt out.
- Ensure GTM reads the
cookieConsentGTMvalue fromlocalStorage.
Steps for the Eloqua developer
- Modify GTM triggers to check for
cookieConsentGTM. - Ensure Eloqua scripts only load when consent is accepted.
- Test using GTM Preview Mode.
GTM cookie opt out banner
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 | Weakest consent-control pattern |
| Server Side Blocking | Medium (Requires server access) | High | Medium | Strong technical control |
| Google Tag Manager (GTM) | Easy (If already using GTM) | High (Prevents tracking entirely) | Low | Usually the practical preferred route |
For most controlled Eloqua implementations, I prefer the GTM route because it can prevent tracking from loading until the agreed consent state exists.
That gives the technical team a visible place to manage triggers, test consent states and show what happens before and after opt-in. Your legal or privacy team still needs to define the policy.
If you need assistance in configuring one of these solutions, feel free to reach out.
Greg Staunton
What a sensible $1,500 to $2,800 implementation looks like
Scenario, costs and time to complete
Jo is the marketing automation manager at ACME Inc. She is overseeing the migration to Eloqua and owns the relationship with their marketing automation agency. The web team has raised a concern that the current Eloqua tracking might not be compliant with GDPR, CCPA and PECR because cookies are being set before users have a chance to opt out.
Jo’s stakeholders have asked for a clear path to fix this. The requirement is simple to describe but often expensive in quotes: implement a cookie opt out solution that stops Eloqua tracking when users decline non essential cookies, and prove that the setup is compliant. The web team has reached out to their agency for advice and a quote on the time and costs involved.
Jo wants to know if the agency quote is realistic. The breakdown below shows what a fair estimate looks like in terms of tasks, hours and role based costs for implementing the GTM based Eloqua cookie opt out pattern.
| Role | Main work | Hours | Rate | Cost range |
|---|---|---|---|---|
| CTO oversight | Architecture review where genuinely needed | 1-2 | $200/hour | $200-$400 |
| Junior developer | Banner support, repeatable configuration and QA | 3-6 | $100/hour | $300-$600 |
| Senior developer | GTM triggers, Eloqua gating, debugging and testing | 5-8 | $150/hour | $750-$1,200 |
| Program manager | Requirements, coordination and sign-off | 2-4 | $150/hour | $300-$600 |
| Total | Controlled implementation and testing | Approximately 16-24 | Mixed | $1,500-$2,800 |
The exact staffing mix varies. A tidy GTM container may not need CTO involvement, while a complex consent platform or unusual deployment architecture may need more senior review.
What should push the cost up
- Multiple domains, brands or regional websites.
- A complex consent-management platform or several consent categories.
- Geo-specific rules, languages or different regional behaviour.
- A messy GTM container with duplicate or undocumented Eloqua tags.
- Server-side tagging, custom application work or unusual infrastructure.
- Extensive browser, device and regression testing.
What should not push the cost up
- Adding one agreed consent check to a tidy Eloqua tag.
- Using GTM Preview to verify accepted and rejected states.
- Documenting the trigger, variable and tag relationship.
- Basic testing on a controlled website with one consent banner.
- Explaining the implementation in language the client can support.
If the estimate is well above $2,800, ask what additional complexity is being solved and request the hours by role.