Skip to content
Start for free

Oracle Eloqua

Send page views to Oracle Eloqua only after visitors allow marketing and the Eloqua vendor. Before that, no Eloqua code or cookie reaches the page.

Inth keeps the consent record of each choice, with the visitor’s country and the policy that applied.

Start for free
pnpm add @c15t/integrations
Oracle EloquaWaiting for consent
Before a choice

Allow only another category. No elqCfg.min.js, _elqQ, Eloqua cookies or storage appear.

Turn the switch on, then off, to see what loads.

Before you start

You need an Inth project that connects to your app and c15t in that app. You also need your site ID from Eloqua.

To use firstPartyCookieDomain, set up a first party tracking hostname in Eloqua first.

Open the quickstart for your framework

How consent works with Eloqua

The c15t eloquaTracking helper waits for marketing and for vendor consent. Until both are in place, it creates no globals and downloads nothing.

After consent, the helper creates _elqQ, sets your site ID and downloads the SDK. It then queues elqOptIn and waits for its response before it sends a page view.

On withdrawal, the helper sends elqOptOut. It sends one consent request at a time, so a fast change of mind ends with the latest choice.

Opt out does not cancel every Eloqua request. So keep reloadOnConsentRevoked on, and the next page starts fresh.

Installation

Eloqua has one load mode in c15t. The helper waits for marketing permission.

Wait for permission. No request goes to Eloqua until the visitor accepts marketing and the Eloqua vendor. On withdrawal, the helper sends elqOptOut and c15t reloads the page.

eloquaTracking({ siteId })

An opt-out policy or no policy gives optional categories permission before a choice. Then Eloqua loads on the first page. This guide uses an opt-in policy.

Setup steps

  1. Install the integration package

    Add the helpers next to c15t. An import alone does not start Oracle Eloqua.

    pnpm add @c15t/integrations

  2. Add your site ID

    If a required value is blank or left out, the helper logs an error and never loads.

    src/consent-scripts.ts
    import { eloquaTracking } from '@c15t/integrations/oracle-eloqua';

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

    Use one site ID and one first party cookie domain per page. Other values conflict with the installed setup, and the helper blocks them.

  3. Register it with your existing setup

    Add scripts to the c15t configuration that you have now. Keep your Inth endpoint, mode, policy, styles and consent UI.

    Add scripts to c15t.config.ts, next to next.config.ts. Keep the rest of your config, such as mode, in the same call. App Router, Pages Router and static export read the same file.

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

export default defineConsentConfig({ scripts });

    Pass scripts to the ConsentRoot in your root route. Import helpers in the route module, not in a server function: script configurations carry callbacks.

    src/routes/__root.tsx
    import { scripts } from '../consent-scripts';

<ConsentRoot state={consent} scripts={scripts}>

    Add scripts to the options of your ConsentProvider, next to mode. Keep the banner, dialog and preferences link inside the provider.

    src/consent.tsx
    import { scripts } from './consent-scripts';

<ConsentProvider options={{ mode, scripts }}>

    Register scripts under the c15t key in app.config.ts. Keep them out of nuxt.config.ts, which reaches the browser as JSON and drops the helper callbacks.

    app/app.config.ts
    import { scripts } from '../src/consent-scripts';

export default defineAppConfig({
  c15t: { scripts },
});

    Pass scripts to the c15tVue plugin call you have now. The plugin starts one script loader when the app mounts.

    src/main.ts
    import { c15tVue, manifest } from 'c15t/vue/vue-plugin';
import { scripts } from './consent-scripts';

app.use(c15tVue, {
  mode: manifest(),
  scripts,
});

    Add scripts to the client entrypoint, which the integration finds on its own. Keep helpers out of astro.config.mjs: its options are serialized into the page.

    src/c15t.client.ts
    import type { C15tClientOptionsExtension } from 'c15t/astro';
import { scripts } from './consent-scripts';

export default { scripts } satisfies C15tClientOptionsExtension;

    Pass scripts as a prop to the ConsentProvider you have now. The provider owns the loader and disposes it on unmount.

    src/App.svelte
    <script lang="ts">
  import { ConsentProvider, manifest } from 'c15t/svelte';
  import { scripts } from './consent-scripts';
</script>

<ConsentProvider mode={manifest()} {scripts}>
  <!-- Your app and consent UI -->
</ConsentProvider>

    Add scripts to the ConsentRoot in the root layout. Import helpers in the layout component, not in +layout.server.ts: a server load cannot send functions to the browser.

    src/routes/+layout.svelte
    <script lang="ts">
  import { ConsentRoot } from 'c15t/svelte';
  import { scripts } from '../consent-scripts';

  let { children, data } = $props();
</script>

<ConsentRoot state={data.consent} {scripts}>
  {@render children()}
</ConsentRoot>

    Paste the vendor’s snippet behind consent

    The helpers need a bundler. On a page with the c15t script tag, paste the vendor’s own snippet instead and keep it inert until visitors allow its category. Helper options, such as loadMode, do not apply.

    index.html
    <script type="text/plain" data-c15t-category="marketing">
  // The vendor's snippet, unchanged
</script>

    Pass scripts to init() from @c15t/browser, next to your mode. With createConsentRuntime, pass scripts to it instead.

    src/consent.ts
    import { init, manifest } from '@c15t/browser';
import { scripts } from './consent-scripts';

const consent = init({
  mode: manifest(),
  scripts,
});
All frameworks

Remove the original asynchronous Eloqua tracking snippet, so it cannot load Eloqua without consent.

Verify your setup

Use a clean browser profile. Filter DevTools Network by elqCfg. Then test the three states.

  • Before a choice

    Allow only another category. No elqCfg.min.js, _elqQ, Eloqua cookies or storage appear.

  • After you allow marketing

    Allow Eloqua as a vendor too. The real dispatcher replaces the queue, and a page view follows the opt in.

  • After you withdraw marketing

    Check for the opt out request. Then allow marketing again and look for a new page view.

Eloqua can set ELOQUA, ELQSTATUS, ELQOPTOUT and OPTIN cookies, and Oracle lists a 13 month lifetime. The reload does not erase every one.

Open the full Oracle Eloqua guide