# Salesforce Account Engagement

The c15t pardotTracking helper loads Salesforce Account Engagement only after visitors allow marketing in Inth. Withdrawal calls revokeConsent and reloads the page.

## Key facts

- **Tool:** Salesforce Account Engagement
- **Category:** Other
- **Consent categories:** Marketing
- **Setup method:** c15t package
- **Package:** @c15t/integrations

## Links

- [Documentation](https://c15t.com/docs/integrations/salesforce-pardot)
- [Salesforce Account Engagement](https://www.salesforce.com/marketing/b2b-automation/)

Track prospects in Salesforce Account Engagement, formerly Pardot, once visitors allow marketing. Until then, no Pardot global or tracker reaches the page.

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

[Start for free](/dashboard/sign-up)

## Before you start

You need an Inth project that connects to your app and c15t in that app. You also need piAId and piCId from your Account Engagement tracking snippet.

For the default consent mode, turn on the Tracking and Consent API in Account Engagement and use its verified tracker domain.

[Open the quickstart for your framework](https://c15t.com/docs/frameworks)

## How consent works with Account Engagement

Before marketing has permission, the c15t pardotTracking helper creates no Pardot globals and downloads nothing.

After consent, it hides the Salesforce consent banner and starts with setOptIn(false). Once the SDK loads, it calls setOptIn(true) and sends one page view.

On withdrawal, consent mode calls pdt('revokeConsent'). The helper does not clear tracking cookies, since that would also delete the cookie that holds the refusal.

In both modes, c15t then reloads the page, and the reload stops the tracker.

## Installation

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

### Wait for permission

No request goes to Account Engagement until the visitor accepts marketing. On withdrawal, the tracker gets revokeConsent and c15t reloads the page.

```ts
pardotTracking({ piAId, piCId, piDomain })
```

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

## Setup steps

#### Install the integration package

Add the helpers next to c15t. An import alone does not start the Account Engagement tracker.

```
pnpm add @c15t/integrations
```

#### Add your account and campaign IDs

Copy piAId and piCId as they appear in the snippet. They already include the Salesforce +1000 offset, and the helper does not add it again.

```
import { pardotTracking } from '@c15t/integrations/salesforce-pardot';

export const scripts = [
  pardotTracking({
    piAId: '123456',
    piCId: '654321',
    piDomain: 'pi.pardot.com',
  }),
];
```

Replace pi.pardot.com with your verified tracker domain. For the older pd.js snippet, set mode: 'classic', which has no revoke call.

### Register it with your existing setup

#### Next.js

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.

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

export default defineConsentConfig({ scripts });
```

#### TanStack Start

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

```
import { scripts } from '../consent-scripts';

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

#### React

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

```
import { scripts } from './consent-scripts';

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

#### Nuxt

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.

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

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

#### Vue

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

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

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

#### Astro

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.

```
import type { C15tClientOptionsExtension } from 'c15t/astro';
import { scripts } from './consent-scripts';

export default { scripts } satisfies C15tClientOptionsExtension;
```

#### Svelte

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

```
<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>
```

#### SvelteKit

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.

```
<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>
```

#### HTML: 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.

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

#### JavaScript

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

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

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

Remove the original tracking snippet. Keep reloadOnConsentRevoked on in both modes.

## Verify your setup

Filter DevTools Network by pdt.js. Then test the three states.

- **Before a choice**: Allow only another category. No pdt.js or pd.js request, pdt or piAId global, cookies or storage appear.

- **After you allow marketing**: The consent dispatcher loads and sends one page view with your account.

- **After you withdraw marketing**: The refusal cookie stays after the reload. Allow marketing again and look for one new page view.

Pardot can set visitor\_id, pi\_opt\_in, lpv and pardot cookies with an account suffix. The reload does not erase them.

[Open the full Account Engagement guide](https://c15t.com/docs/integrations/salesforce-pardot)

## Related guides

- [ActiveCampaign](/integrations/activecampaign)

- [Attentive](/integrations/attentive)

- [Customer.io](/integrations/customer-io)