AdStack logo
WhatsApp Talk to an expert
Solutions Integrations Platform Contact Talk to an expert Chat on WhatsApp

Integrations

Fits into your ad-tech chain, beside the tools you already run.

AdStack is designed for compatibility with common ad-tech integrations and wrappers. This page sets out which workflows it supports, what each one depends on, and where the limits are.

Building blocks plugging into a central stack

Supported workflows

Five core platforms, five different jobs.

Each one sits at a different point in the chain, so the role AdStack plays beside it changes too. These are the workflows we are asked about most.

PlatformWhat the workflow involvesWhat it depends on

WorkflowVAST tag and wrapper workflows where Google Ad Manager is the ad server or a demand source. AdStack can host creative, track independently and apply delivery controls around the tag.

Depends onYour line-item and creative set-up in GAM, and Google's own policies.

WorkflowVideo and CTV ad-serving workflows, including tag-based and wrapper arrangements, with AdStack handling hosting, tracking or decisioning beside them.

Depends onYour SpringServe account configuration and the formats it supports.

WorkflowSupply-side workflows where Magnite demand or tags are part of the request chain, with AdStack tracking and controlling the delivery around them.

Depends onYour own agreement and set-up with Magnite.

WorkflowVideo player and wrapper workflows, where AdStack provides first-party hosting, independent tracking or allocation logic around the player's ad calls.

Depends onYour Aniview configuration and player implementation.

WorkflowPublisher video ad-serving workflows on FreeWheel, with AdStack acting alongside as a hosting, tracking or controls layer.

Depends onYour FreeWheel set-up and the platform's requirements.

More platforms we support

Exchanges, SSPs, ad servers and mobile mediation layers.

  • PubMaticSSP and exchange workflows
  • Index ExchangeExchange and supply workflows
  • OpenXExchange and supply workflows
  • EquativAd server and SSP workflows
  • TripleLiftCTV and native supply workflows
  • PublicaCTV ad-serving workflows
  • PrebidHeader-bidding workflows
  • Google AdMobMobile app monetisation workflows
  • AppLovin MAXMobile mediation workflows
  • Unity LevelPlayMobile mediation workflows
  • T
    Third-party VAST wrappersPassed through and tracked
  • C
    Custom integrationsBuilt around your stack
A plug and a wrench joining two blocks

Custom and bespoke integrations

Running a platform that is not listed, an in-house ad server, or a set-up that is entirely your own? Custom integrations are supported too, whether the other side speaks VAST, standard ad tags or its own endpoints. We map the workflow with your team and confirm the details during scoping.

Discuss your stack

VAST wrappers

Third-party wrappers pass through. Tracking does not get lost on the way.

A VAST wrapper hands the player on to another ad server, which may hand it on again. Every hop can drop an impression or report late, and the publisher sees only the final count.

AdStack supports third-party VAST wrappers and external ad-serving workflows. A wrapper can be passed through as received, with AdStack's own tracker kept beside the chain, so you hold a record that does not depend on each hop behaving.

  • Wrapper responses passed through as received
  • An independent tracker carried alongside the chain
  • First-party hosted creative mixed with external demand
VAST wrapper chain with an independent tracker A video player calls AdStack, which passes the request to a third-party VAST wrapper and then to the creative. An independent AdStack tracker records events alongside the chain. Player AdStack Third-partywrapper Creative Independent tracker Events recorded beside the chain, not only inside it

Third-party trackers

Bring your own trackers. We fire them with the ad.

Advertisers, agencies and publishers often need their own measurement in the chain. AdStack supports third-party trackers and carries them with the ad, so each fires at the right point in playback.

They sit beside AdStack's own signed trackers, not instead of them. When the two sets of counts disagree, the gap is the first thing to investigate.

  • Impression and click pixels supplied by an advertiser or agency.
  • VAST tracking URLs for start, quartile and completion events.
  • Viewability and verification tags run by a measurement vendor.
  • Attribution postbacks for mobile install and in-app events.
  • Your own endpoints, for teams that log events in their own systems.

Tracker, verification and measurement services

The measurement stack you already use, fired with the ad.

We support tracker, verification, attribution and measurement services through pixels, VAST tracking URLs, tags and postbacks. They run beside AdStack’s signed trackers, and anything not listed here is supported as a custom integration.

Verification and viewability

  • Integral Ad ScienceViewability and verification tags
  • DoubleVerifyVerification and brand-safety tags
  • ComscoreAudience and viewability measurement
  • NielsenAudience measurement tags
  • PixalateInvalid-traffic and quality tags
  • H
    HUMAN SecurityBot and fraud verification
  • P
    Protected MediaFraud-prevention tags
  • ZefrBrand-suitability measurement
  • AdlooxVerification and viewability tags

Mobile attribution

  • AppsFlyerAttribution postbacks
  • AdjustAttribution postbacks
  • BranchAttribution and deep-link postbacks
  • KochavaAttribution postbacks
  • SingularAttribution postbacks
  • AirbridgeAttribution postbacks

Ad-server and creative trackers

  • C
    Campaign Manager 360Ad-server tracking URLs
  • I
    InnovidCreative and VAST tracking
  • F
    FlashtalkingCreative and VAST tracking
  • Y
    Your own endpointsEvents logged in your systems

CTV measurement

  • iSpot.tvTV and CTV measurement
  • Samba TVCTV measurement
  • VideoAmpCross-screen measurement

CDN and tracking workflows

Two parts of the chain you can take on yourself.

You do not have to adopt everything. Many teams start with one of these and add the other later.

Hosted creative over CDN

AdStack hosts ad content first-party and delivers it through CDN infrastructure worldwide. Your ad server, SSP or player references stable URLs for the files, and creatives can be replaced without reissuing tags.

Signed, separate trackers

Delivery, impression, event and quality trackers can run beside the platforms you already use. Each tracking URL is HMAC-signed, giving you a second set of numbers to compare with the platform's own.

Getting started

What we will ask you for.

Support depends on set-up that only you can do inside your own platform accounts. Having the following ready makes the first conversation shorter.

  • Where the chain runs. Which ad server, SSP or wrapper handles requests today.
  • Placements. Apps, sites or CTV channels involved, with their formats.
  • Volume range. A rough monthly ad request figure, even if approximate.
  • Reconciliation method. Whose numbers you treat as the record, and how often you compare.
  • A test window. A limited slice of traffic where we can verify signatures and counts first.

Precise language

What support covers.

Plain definitions for the terms used on this page.

Supports
A workflow involving that platform can be implemented with AdStack, given the right set-up on your side.
Compatible with
It uses common standards such as VAST, so interoperation is expected. It is confirmed during scoping, not assumed.
Subject to your set-up
Platform accounts, tags, line items and policies sit with you. We build the workflow around the configuration you have.

Questions

Integration questions, answered plainly.

Which platforms does AdStack support?

AdStack supports workflows involving Google Ad Manager, SpringServe, Magnite, Aniview and FreeWheel, plus third-party VAST wrappers, CDN-hosted creative and independent tracking. Support is subject to client-side setup and each platform's own requirements.

Does AdStack replace my ad server or SSP?

No. It is designed to sit beside them and take on specific jobs, such as first-party hosting, weighted allocation, geography checks or independent tracking. Your existing platforms stay in your chain.

Do I need my own account with each platform?

Yes. Accounts, line items, tags and platform policies are yours. AdStack works with the set-up you have, which is why support is described as subject to client-side configuration.

Are custom integrations supported?

Yes. If your platform is not listed, or you run an in-house ad server, custom integrations are supported whether the other side speaks VAST, standard ad tags or its own endpoints. The details are mapped with your team and confirmed during scoping.

How are third-party VAST wrappers handled?

Wrappers can be passed through as received, with an AdStack tracker kept alongside the chain so you keep an independent record of events.

Does AdStack support third-party trackers?

Yes. Impression and click pixels, VAST tracking URLs, viewability and verification tags, attribution postbacks and your own endpoints can be carried with the ad. They are fired alongside AdStack's own signed trackers, so the two sets of counts can be compared.

Using a platform that is not listed here?

Tell us what sits in your chain. If it speaks VAST or standard tags, the conversation is usually short.

Talk to an AdStack Expert Explore the Platform
WhatsApp us