Oracle Eloqua

eloquaTracking waits for its mapped category and vendor consent before creating vendor globals or downloading Oracle Eloqua. The default category is marketing.

Configure Oracle Eloqua

Copy your site ID from Eloqua and remove the original asynchronous tracking snippet. Configure a first-party tracking hostname in Eloqua before setting firstPartyCookieDomain.

npm install @c15t/integrations

pnpm add @c15t/integrations

yarn add @c15t/integrations

bun add @c15t/integrations

import { eloquaTracking } from '@c15t/integrations/oracle-eloqua';

export const scripts = [eloquaTracking({ siteId: 'YOUR_SITE_ID' })];

Register the scripts

Complete your framework quickstart first. Keep its Inth endpoint, policy, styles and consent UI. Remove the vendor's original script, SDK initializer or tag-manager entry, so the vendor loads only through c15t.

The vendor pages put the helper in src/consent-scripts.ts. If your framework quickstart already has a scripts array, such as the one in c15t.config.ts in the Next.js guide, add the helper to that array instead of creating a second file. The scripts export is a configuration, not an initializer. Add it to the c15t provider you already have, at the registration point for your framework below. These are edits to that provider, not a second provider.

import { defineConsentConfig } from 'c15t/next';
import { scripts } from './src/consent-scripts';

export default defineConsentConfig({ scripts });

Options

Missing or blank required values log an error and never load.

Custom loaders must synchronously append one matching consent response script when elqOptIn or elqOptOut runs. Preserve pps=41 for opt-in, pps=42 for opt-out, and the installed account's siteid query parameter. The response itself can complete asynchronously. A deferred or unmatched custom response leaves consent indeterminate. The helper reports the problem and blocks tracking and further consent commands until reload.

A custom dispatcher that throws also blocks tracking and further consent commands until reload, even if it appended a matching response before throwing.

Loading and revocation

After consent, the helper creates _elqQ, sets the site ID and optional first-party cookie domain, and downloads the SDK. After loading, it queues elqOptIn and waits for its response script before elqTrackPageView. The page view uses the full current page URL, including its path, query and fragment, when the response completes.

The helper sends one consent request at a time. If consent changes while a response is pending, it waits for completion and then sends the latest choice. Withdrawal or disposal during opt-in sends elqOptOut after that response finishes and suppresses the page view only when the current owners no longer collectively permit tracking. Disposing one provider preserves the active lifecycle when at least one registered provider remains and every remaining provider still allows tracking. Regrant waits for any pending opt-out before opting in again. Failed responses do not trigger immediate retries or page views. A later consent update or remount can retry a failed request, including an opt-out that failed after disposal. Regrant and category changes preserve Eloqua's installed dispatcher while another provider retains its loader. If a surviving provider needs a new loader, the helper creates a fresh setup queue before loading another SDK. Each SDK execution receives its initial site and first-party settings, which the helper binds to its physical tag before loading. The helper keeps the resulting dispatcher with that tag. A detached download can still execute, so later provider adoption uses the tag's captured dispatcher.

Calling eloquaTracking again with equivalent options preserves the active consent lifecycle, including pending response handling across disposal and remount. Consent responses for the same site stay serialized when a provider is replaced, even if its category or loader URL changes. When providers share that configuration, every registered provider must allow the category and vendor before tracking starts. A denied provider that has never loaded still participates in this decision. SDK setup waits while a registered provider denies consent. Compatible providers can use different consent categories or loader URLs and still coordinate consent. Regranting either provider sends one page view after opt-in completes, provided every current owner allows tracking.

A provider can adopt an already-loaded compatible tag while another provider denies consent. Once the denying provider is removed or grants consent, the adopter can keep tracking after the original provider is disposed.

Use one site ID and first-party cookie domain per page. Hostname case and surrounding whitespace are normalized. An absent domain differs from a configured domain. Providers with a different site ID or domain conflict with the installed configuration. The helper reports the conflict, blocks the adopter's commands, and blocks tracking through the installed account while that provider remains registered, even if it starts denied. Withdrawal still targets the installed account and waits for its pending response. Removing the conflicting provider releases its blocker. Changing the installed site or domain requires reload, including after its script tag is removed.

If the stock SDK fails to append a consent response, the helper reports the dispatch failure without confirming the request. It sends no page view for a failed opt-in. A later explicit script reconciliation can retry that request; there is no automatic retry loop. A failed opt-out can leave Eloqua's previous opt-in cookie in place. The helper does not delete that cookie or claim withdrawal succeeded.

Keep reloadOnConsentRevoked enabled. Eloqua's opt-in and opt-out commands make asynchronous requests; opt-out does not disable every SDK request method or cancel requests already in flight. The helper orders its own consent requests and waits for the first-party opt-in response so a regrant page view does not run while the opt-in cookie still reads 0. A request that never completes can hold up a later choice until reload. The loader stays in the DOM for same-page regrant because Eloqua replaces its array queue with a dispatcher. Reload gives the next page a fresh tracking lifecycle. Removing a script tag cannot unload the SDK.

Eloqua can set ELOQUA, ELQSTATUS, ELQOPTOUT and first-party OPTIN cookies. Oracle documents 13-month tracking cookie lifetimes. Reload does not erase every vendor cookie.

Verify Oracle Eloqua

Use a clean browser profile for the initial-state checks.

Before consent and after unrelated consent, check for no elqCfg.min.js, _elqQ, Eloqua cookies or browser storage. Grant the mapped category, which defaults to marketing, and allow Oracle Eloqua as a vendor. Confirm the real dispatcher replaces the array, then revoke and inspect the opt-out request. Regrant with your configured account and verify page tracking after the asynchronous opt-in completes.

Sources: basic tracking, first-party tracking, and opt-in and opt-out commands.

Test in a private window with an opt-in policy. Open DevTools Network, disable the cache and filter by the vendor's domain:

1. Load the page. No request goes to the vendor before you choose.
2. Click Reject, then reload. There is still no vendor request.
3. Open Privacy settings and allow the helper's category. The vendor script loads without a page reload.
4. Turn the category off again and save. c15t reloads the page, and the new page makes no vendor request.

c15t reloads on revocation because removing a script element does not stop code that already ran. The vendor's listeners, timers and queued events stay alive until the page unloads. If you set reloadOnConsentRevoked: false, stop the vendor yourself. Register a callback-only script whose onConsentChange calls the vendor's opt-out API, as shown in custom integrations, and check the permission before each of your own event calls. The reload does not delete cookies the vendor already set; see clear on revocation for your framework.

The helper lists its vendor by name in the preference dialog, so a visitor can turn it off inside an allowed category. See vendor consent for your framework. The consent verification guide covers navigation, expiry and hosting checks.