# Amazon Ads

The c15t amazonAdsTag helper loads the Amazon Ads tag only after visitors allow marketing in Inth. With a visitor country, it also sends Amazon Consent Signal.

## Key facts

- **Tool:** Amazon Ads
- **Category:** Advertising
- **Consent categories:** Marketing
- **Setup method:** c15t package
- **Package:** @c15t/integrations

## Links

- [Documentation](https://c15t.com/docs/integrations/amazon-ads)
- [Amazon Ads](https://advertising.amazon.com/)

Load the Amazon Ads tag only after visitors allow marketing, and send ad storage and user data permission through Amazon Consent Signal.

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, c15t in that app and your Amazon Ads tag ID and account region.

New to c15t? Complete the quickstart for your framework first. Keep its Inth endpoint, policy, styles and consent UI.

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

## How consent gets to Amazon Ads

Before marketing has permission, the c15t amazonAdsTag helper creates no window.amzn, amzn.q or amznConsent. It loads neither Amazon library.

Pass countryCode with the real visitor country from your server. Then the helper also loads Amazon Consent Signal (ACS) and sends enableAdStorage and enableUserData. Without a country, only the main tag loads.

On withdrawal, the helper sets both ACS permissions to false. Amazon has no shutdown command for the tag, so keep the default reload of c15t on.

The helper creates no TCF consent string. Use your current IAB setup when Amazon needs TCF.

[Read the Amazon consent signal rules](https://advertising.amazon.com/resources/ad-policy/consent-signal-requirements)

## Installation

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

### Wait for permission

No request goes to Amazon until the visitor accepts marketing. With ACS, withdrawal sends both signals as denied.

```ts
amazonAdsTag({ region, tagId })
```

An opt-out policy or no policy gives optional categories permission before a choice. Then Amazon Ads 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 Amazon Ads tag.

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

#### Add your tag ID

region names the region of your Amazon Ads account. It does not name the visitor country, and the helper never assumes US.

```
import { amazonAdsTag } from '@c15t/integrations/amazon-ads';

export const scripts = [amazonAdsTag({ region: 'NA', tagId: 'YOUR_TAG_ID' })];
```

Amazon says that EEA traffic needs at least one of TCF, GPP or ACS. Check which signals your account and traffic need.

### 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 direct snippets and tag manager copies, so they cannot get around c15t. Check the current permission before each amzn event call of your own, because the function stays after withdrawal.

## Verify your setup

Use a private window with an opt-in policy. Open DevTools Network and filter by amazon-adsystem.com. Then test the three states.

- **Before a choice**: Neither Amazon library loads, and no Amazon event request appears. Reject, reload and check again.

- **After you allow marketing**: amzn.js loads one time with the first PageView. With a real countryCode, amzn-consent.js runs first and holds the granted signals.

- **After you withdraw marketing**: With ACS, both signals change to denied. c15t reloads the page, and neither Amazon library loads.

Use the tag ID of your account for an acceptance test. A fetched script does not prove that Amazon accepted the event.

[Open the full Amazon Ads guide](https://c15t.com/docs/integrations/amazon-ads)

## Related guides

- [LinkedIn Insight Tag](/integrations/linkedin-insights)

- [LiveIntent](/integrations/liveintent)

- [Meta Pixel](/integrations/meta-pixel)