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.
-
Production: This environment is used for testing API integrations without affecting your live campaign data. 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 |
| Data blocking (skip objects and fields) | Yes |
| Resync (objects and Pipelines) | Yes |
| API configurable | Yes |
Prerequisites
-
An active Stackadapt account exists from which data is to be ingested.
-
A GraphQL API Token is available to provide Hevo access to your Stackadapt account data.
Obtain the API Token
To connect Hevo to your Stackadapt account, you must provide a GraphQL API Token. StackAdapt does not allow you to generate GraphQL API Tokens from the account UI. To obtain an API Token, contact your StackAdapt account manager or the StackAdapt Support team. Once your request is approved, they will provide the API Token required to authenticate your GraphQL API requests.
Use this API Token when configuring your Stackadapt Source in Hevo. If the API Token configured in the Pipeline is revoked manually from your Stackadapt account, Hevo cannot authenticate with the Source. As a result, all active jobs for the Pipeline fail, and no data is replicated. To resume data replication, modify the Source configuration in the Pipeline with a valid API Token. Once the updated token is saved, Hevo re-authenticates the Source, and data ingestion resumes from the last saved offset.
Configure Stackadapt as a Source in your Pipeline
Perform the following steps to configure your Stackadapt Source:
-
Click Pipelines in the Navigation Bar.
-
Click + Create Pipeline in the Pipelines List View.
-
On the Select Source Type page, select Stackadapt.
-
On the Select Destination Type page, select the type of Destination you want to use.
-
In the Configure Source screen, specify the following:
-
Source Name: A unique name for your Source, not exceeding 255 characters. For example, Stackadapt 2.
-
In the Connect to your Stackadapt account section, specify the following:
-
API Token: The API Token that you obtained from Stackadapt.
-
Use Sandbox: Enable this option to connect Hevo to a Sandbox environment instead of a Production environment.
-
Historical Sync Duration: The duration for which you want to ingest existing data from the Source. This cannot be changed after the Pipeline is created. Default duration: 365 days.
-
-
-
Click Test & Continue to test the connection to your Stackadapt Source. Once the test is successful, you can proceed to set up your Destination.
Data Replication
Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline.
Selecting a parent object automatically includes all its associated child objects for replication. Child objects cannot be selected or deselected individually.
Hevo ingests the following types of data from your Source objects:
-
Historical Data: The first run of the Pipeline ingests all available historical data for the selected objects and loads it into the Destination. For Insight and Delivery reports, historical data is ingested based on the historical sync duration selected when creating the Pipeline.
For the Insight Campaign Geo and Insight Campaign Group Geo objects, Hevo can ingest up to 30 days of historical data.
-
Incremental Data: Once the historical load is complete, new and updated records for objects are ingested as per the sync frequency.
For all objects, Hevo ingests the entire data during each Pipeline run.
Note: You can create a Pipeline with this Source only using the Merge load mode. The Append mode is not supported for this Source.
Stackadapt enforces a rate limit on its GraphQL API requests. If this limit is exceeded, a rate limit exception occurs. To understand how Hevo handles such scenarios, read Handling Rate Limit Exceptions.
Schema and Primary Keys
Hevo uses the following schema to upload the records to the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.
Data Model
The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:
| Object | Description |
|---|---|
| Advertiser | Contains details of the advertiser account, such as its name and description. An advertiser is the top-level account under which campaign groups and campaigns are managed. |
| Campaign Group | Contains details of campaign groups, including budget, daily cap, schedule, pacing settings, purchase order number, revenue type and value, and status. A campaign group organizes one or more campaigns under an advertiser. |
| Campaign | Contains details of individual campaigns, including targeting configuration (geography, device type, language, demographics, and custom segments), budget and pacing settings, optimization goals, day-parting rules, frequency caps, and status. |
| Ad | Contains details of ads (creatives) used in campaigns, including brand name, channel type, creative size, click URL, and impression tracking information, along with status flags indicating whether the ad is archived, in draft, rejected, or paused. |
| BYOD Deal | Contains details of Bring-Your-Own-Deal private marketplace deals, including the associated publisher, deal floor price, bid type, device type, supply type, and the deal’s start and end dates. |
| Inventory Package | Contains details of curated inventory packages, including available inventory volume, bid guidance, targeted countries, device types, and supply types. Inventory packages can be marked as private, deprecated, or associated with live events. |
| Brand Lift Study | Contains details of brand lift studies, including the study name, status, and the number of associated awareness campaigns. |
| Webhook | Contains details of webhooks configured in your Stackadapt account, including the webhook name, the event it is subscribed to, its active status, and the destination URL to which event notifications are sent. |
| User Vertical Strategy | Contains details of vertical strategy templates used to configure campaign groups, including the objective, performance goals, target vertical, product domains, and suggested campaign group budget. |
| Supply Source Option | Contains the list of supply source options available in Stackadapt, such as the different ad exchanges and marketplaces from which inventory can be sourced. Used as a reference lookup for the supply source dimension in insight reports. |
| Custom Segment Option | Contains the list of custom audience segment options configured in your Stackadapt account. Used as a reference lookup for custom segment targeting on campaigns. |
| Advertiser Delivery | Contains per-day delivery and performance metrics aggregated at the advertiser level, including impressions, clicks, conversions, video and audio completion rates, viewability, engagement, cost, and revenue. |
| Campaign Group Delivery | Contains per-day delivery and performance metrics aggregated at the campaign group level, including impressions, clicks, conversions, video and audio completion rates, viewability, engagement, cost, and revenue. |
| Campaign Delivery | Contains per-day delivery and performance metrics aggregated at the campaign level, including impressions, clicks, conversions, video and audio completion rates, viewability, engagement, cost, and revenue. |
| Ad Delivery | Contains per-day delivery and performance metrics aggregated at the ad level, including impressions, clicks, conversions, video and audio completion rates, viewability, engagement, cost, and revenue. |
| Insight Campaign Supply Source | Contains per-day performance metrics for each campaign, broken down by supply source, including impressions, clicks, cost, conversions, and engagement metrics. |
| Insight Campaign Demographic | Contains per-day performance metrics for each campaign, broken down by demographic segment. |
| Insight Campaign Deal | Contains per-day performance metrics for each campaign, broken down by programmatic deal. |
| Insight Campaign Creative Tactic | Contains per-day performance metrics for each campaign, broken down by creative tactic. |
| Insight Campaign Audience AB | Contains per-day performance metrics for each campaign, broken down by audience A/B test group. |
| Insight Campaign Geo | Contains per-day performance metrics for each campaign, broken down by geographic region. |
| Insight Campaign Category | Contains per-day performance metrics for each campaign, broken down by content category. |
| Insight Campaign Bid Factor | Contains per-day performance metrics for each campaign, broken down by bid factor. |
| Insight Campaign Device | Contains per-day performance metrics for each campaign, broken down by device type. |
| Insight Campaign Audience | Contains per-day performance metrics for each campaign, broken down by audience segment. |
| Insight Campaign Retargeting Segment | Contains per-day performance metrics for each campaign, broken down by retargeting segment. |
| Insight Campaign Group Category | Contains per-day performance metrics for each campaign group, broken down by content category. |
| Insight Campaign Group Device | Contains per-day performance metrics for each campaign group, broken down by device type. |
| Insight Campaign Group Supply Source | Contains per-day performance metrics for each campaign group, broken down by supply source. |
| Insight Campaign Group Bid Factor | Contains per-day performance metrics for each campaign group, broken down by bid factor. |
| Insight Campaign Group Creative Tactic | Contains per-day performance metrics for each campaign group, broken down by creative tactic. |
| Insight Campaign Group Geo | Contains per-day performance metrics for each campaign group, broken down by geographic region. |
| Insight Campaign Group Deal | Contains per-day performance metrics for each campaign group, broken down by programmatic deal. |
| Insight Campaign Group Retargeting Segment | Contains per-day performance metrics for each campaign group, broken down by retargeting segment. |
| Insight Campaign Group Audience AB | Contains per-day performance metrics for each campaign group, broken down by audience A/B test group. |
| Insight Campaign Group Audience | Contains per-day performance metrics for each campaign group, broken down by audience segment. |
| Insight Campaign Group Demographic | Contains per-day performance metrics for each campaign group, broken down by demographic segment. |
Additional Information
Read the detailed Hevo documentation for the following related topics:
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.