Stackadapt (Edge)

Last updated on Aug 18, 2026

Stackadapt is an AI-powered programmatic advertising platform that connects advertisers, agencies, and brands to audiences across Connected TV, display, video, audio, native, digital-out-of-home, and other digital channels. It enables businesses to plan, execute, optimize, and report on multi-channel ad campaigns using machine learning-driven targeting, bidding, and creative delivery.

Hevo uses Stackadapt’s GraphQL API to replicate data from your Stackadapt account to the Destination of your choice. To ingest data, you must provide Hevo with a Stackadapt GraphQL API Token to authenticate to your Stackadapt account.

Stackadapt Environments

Stackadapt provides separate environments for testing and production use:

  • Sandbox: This environment is used for testing API integrations without affecting your live campaign data. A sandbox environment is accessed using URLs that include the sandbox identifier, such as sandbox.stackadapt.com/public.

  • Production: This environment contains your live Stackadapt account data and is used for actual campaign management and reporting. A production environment is accessed using standard Stackadapt URLs, such as api.stackadapt.com.

Hevo supports replicating data from both the production and sandbox environments. By default, Hevo connects to the Production environment. To ingest data from the Sandbox environment instead, enable the Use Sandbox option while configuring your Stackadapt Source.


Supported Features

Feature Name Supported
Capture deletes Yes
History mode No
Custom data (user-configured tables & fields) No
Data blocking (skip objects and fields) Yes
Resync (objects and Pipelines) Yes
API configurable No

Handling of Deletes

Stackadapt does not explicitly mark records as deleted in its GraphQL API responses. When a record is deleted, it is no longer returned in subsequent API responses.

Hevo uses a full data refresh approach to capture delete actions. During each Pipeline run, Hevo compares the data fetched from the Source object with the data present in the Destination table. If a record exists in the Destination but is no longer returned by the Source, the record is marked as deleted by setting the value of the metadata column __hevo__marked_deleted to True. This applies to all objects.


Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Aug-18-2026 NA New document.

Tell us what went wrong