Getting started · AI Ad Ops SDK

Set up the AI Ad Ops SDK

StackUp TeamUpdated July 20266 min read

Getting started with StackUp AI Ad Ops is a few clicks away. This guide walks you through the full setup: register your domain, create a collection configuration, drop one script tag into your pages, and verify that data is flowing.

✓

What you'll need: access to your StackUp console, and the ability to add a script tag to your site's page header. No callbacks, no attributes, no build steps.

Step 1 — Register and verify your domain

Before the SDK can collect anything, StackUp needs to know which domains it should listen to. In the console, go to Domains, add your site's domain, and complete verification. Verification activates the SDK on your pages, and unverified domains are ignored by the collection pipeline.

Step 2 — Add a collection configuration

A configuration controls signal collection for your SDK: what to collect, where, and when. Every configuration comes down to three decisions, and you can tune everything later:

Pick your signals. Choose which signal tiers to collect, from core page and viewability metrics up to 100% coverage of your entire ad stack.
Set cadence and triggers. Decide when signals fire: on page view, on ad render, on a schedule, or in real time.
Choose a sample rate. Control how much traffic is measured to balance fidelity against event volume and cost.

Fastest path: start from a preset

Presets are tested baselines that let you skip the blank page. Everything stays editable afterward.

Preset	What it collects
Full signal set	100% coverage of your entire ad stack. Real-time collection, 1M events. Recommended default for most publishers.
Performance	Adds latency and render-timing signals on top of the baseline.
Essentials Coming soon	Core page and viewability signals only.

Select a preset and click Use this preset. To build from scratch instead, click Create another configuration and follow the wizard below.

The configuration wizard, step by step

Creating a custom configuration takes six short steps:

1 Identity2 Signal packages3 Collection scope4 Volume & quota5 Review6 Embed

1 · Identify — name your configuration

Give the configuration a name (required) and an optional short description for your team. Use names your team will recognize later, for example Prod — all traffic or Mobile Safari test.

2 · What — select signal packages

Each package is a coherent group of signals. Toggle packages on or off as a single grant.

Package	Signals included
Prebid	Prebid auctions, adapter and bidder health, timeout rates.
Consent & privacy	CMP detection and consent signals.
Ad density	Viewable ad coverage, slot counts, page composition.
Performance	Page load impact, CPU and memory cost of the ad stack.
Geometry Coming soon	Slot dimensions, positioning, cumulative layout shift.
Presence Coming soon	Slot detection, lifecycle events, render confirmation.

3 · Where — define collection scope

Restrict collection to a subset of traffic across four dimensions: Geography, Browser, OS, and Device. Each dimension has an include list and an exclude list, and dimensions are composable. Leave a row blank to allow everything for that dimension.

💡

Tip: for your first configuration, leave scope wide open (include all, exclude none). You can narrow it later once you see where your traffic actually comes from.

4 · When — set volume and quota

Cap how many eligible sessions are collected per day with the daily session quota (required, for example 100,000). The SDK throttles automatically once the cap is reached, so quota overruns are never your problem to manage. Then choose a collection window: Always on (default) or a custom schedule.

5 · Activate — review and confirm

The review screen shows the configuration's name, version, packages, scope, and quota in one place. Check the summary and click Activate. Changes take effect on the next SDK heartbeat, so there is no deploy step on your side.

6 · Embed — connect the configuration to your site

Each configuration gets a unique config ID. Copy the generated script tag, which carries the config ID as a data attribute:

index.html

<!— StackUp AI signal SDK —>
<script
  src="https://cdn.stackup-ai.com/sdk/latest/stackup-sdk.min.js"
  data-config-id="YOUR_CONFIG_ID"
  async
></script>

⚠

Until the SDK is embedded on a verified domain, the configuration shows as pending. Signals begin on the next SDK heartbeat after embedding. You can re-open the embedding instructions anytime from the configuration's row.

Step 3 — Integrate the AI SDK

Initialize tracking with AI Auto-capture. Paste the snippet into your project's page header. One script tag, no configuration needed:

index.html

<script
  defer
  src="https://cdn.stackup-ai.com/sdk/latest/stackup-sdk.min.js"
></script>

That's it. No callbacks, no attributes, no build steps.

💡

Tip: place the snippet as high in <head> as possible for best signal fidelity.

Step 4 — Verify that your data is connected

Once StackUp detects traffic from your site, the integration shows a connected state and preview events appear in the console. Click Verify integration to confirm, then head to the dashboard to watch your first signals arrive.

Go to dashboard →

Troubleshooting

Configuration stuck on pending: confirm the script tag is live on a verified domain and includes the correct data-config-id. Signals begin on the next SDK heartbeat.
No events after embedding: check that your daily session quota is above 0 and the collection window is open.
Collecting too much: lower the sample rate or narrow the collection scope. Changes apply on the next heartbeat with no redeploy.

Was this article helpful?