This document contains frequently asked questions that arise when using the StackAdapt data source. You can quickly navigate to a particular FAQ by using the table of contents below.
What should I know about Domain data?
Why can't I see audio related metrics on any data views except Devices and Geo?
What if I need data from StackAdapt that TapClicks doesn’t quite support?
What fields are available for this data source?
What data can I assign to my Tap Client from this data source?
What should I know about Domain data?
Domain data from the StackAdapt API returns lifetime, snapshot data. This means that it's not possible to get data for each day in a date range. It will always return delivery metrics for each domain for the lifetime of the campaign.
TapClicks stores this data each day, and when you select a date range in your dashboard, the most recent data are shown on screen. For example, if you were to select Aug 1 to Aug 8, the Domain Delivery KPIs that we got from StackAdapt on Aug 8 would be shown on screen.
If you look at a specific period of time shorter than the lifetime of the campaign in StackAdapt's system, you may see that the data in TapClicks doesn't line up exactly. Let's assume that a campaign started on Jan 1 and ran through Aug 31. In StackAdapt you can run a report to see exactly the delivery KPIs for Aug 1 - Aug 8, but if you look at the same range in TapClicks, we will return the lifetime Domain delivery KPIs from the start date of the campaign (Jan 1) to the date the data were pulled (Aug 8).
Best practice is to review your Domain Delivery KPIs in StackAdapt from the start date of your campaign until your reporting date. Then compare that information against what is in TapClicks.
Additionally, you may see some strange behavior if you use TapClicks Comparison Date Ranges in your dashboard. If you have questions, please don't hesitate to reach out to your Customer Success Manager or customercare@tapclicks.com.
Why can't I see audio related metrics on any data views except Devices and Geo?
This is because audio fields are not supported by other types of API calls from StackAdapt. Remember, you can group the data on the Devices and Geo level to get to higher level summary visualization you may need. If you find that you can report on audio fields within your StackAdapt platform against other granularities, definitely submit this need to the Product Portal. For details about how to submit to the Product Portal, see this article.
What if I need data from StackAdapt that TapClicks doesn’t quite support?
There are a few ways to approach this situation.
1] Create a Smart Connector to bring this data into your dashboard.
- This will allow you to get to your data fast.
- This path could be used in the long term.
- Or you can use this path while waiting for an enhancement to the StackAdapt connector.
2] Submit a request to the product team to evaluate bringing this data into the Instant On connector.
- Make sure to include report extract examples so that we can review exactly the dimensions and metrics you’re looking for in your dashboard.
- If you need help with this process, feel free to reach out to your Customer Success Manager or customercare@tapclicks.com.
What fields are available for this data source?
After you connect a data source to TapClicks, you can use that data in your reports. These fields are organized into groups of similar types of data called Data Views. You can view all fields and data views for a given data source in the Connector Marketplace.
For StackAdapt, you will find a list of all dimensions and metrics available for use in TapClicks, organized by data view, here: StackAdapt fields in the Connector Marketplace.
What data can I assign to my Tap Client from this data source?
Level 1 - Advertiser
Level 2 - Line Item