> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adriel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQs

> Common questions, expected behaviors, and troubleshooting for the StackAdapt data source.

## Why do I need separate credentials for StackAdapt?

StackAdapt runs two different APIs, and the credential that works for one does not work for the other. The Adriel connector reads reporting through StackAdapt's GraphQL API, which requires its own API key. A key issued for StackAdapt's REST API will not authenticate against the GraphQL API, so an existing REST key cannot be reused here.

The GraphQL API key is requested directly from StackAdapt. Once StackAdapt provides it, it is entered during connection setup. For the full connection walkthrough, see [How to connect StackAdapt to Adriel](/data-sources/o-z/stackadapt/how-to-connect).

## Why did my StackAdapt connection stop working after the key was revoked?

The StackAdapt API key is static. It is not rotated automatically, so a working connection keeps working as long as the key stays valid on StackAdapt's side. If StackAdapt revokes or regenerates the key, the connection can no longer authenticate and stops returning data.

The fix is to obtain a fresh GraphQL API key from StackAdapt and re-establish the connection with the new key. If the connection still fails after reconnecting with a confirmed-valid key, email `support@adriel.com` with the advertiser name and the affected dashboard URL.

## Why is each StackAdapt advertiser a separate data source?

A single StackAdapt API key can grant access to more than one advertiser. Adriel creates one data source per advertiser rather than combining them, so each advertiser's campaigns, ad groups, and creatives stay cleanly separated.

To report across advertisers, add each advertiser's data source to the same dashboard. Widgets aggregate across data sources at the dashboard layer, so cross-advertiser rollups happen there rather than inside a single source.

## Why are my StackAdapt spend totals in USD?

StackAdapt does not always send currency information with its data. When that metadata is missing, the data source falls back to USD, so spend, cost, and other monetary metrics are reported in USD by default.

A currency can be set for the advertiser during connection setup; when it is left blank, USD is used. Spend totals are worth reviewing for any advertiser that bills in a non-USD currency, since a mismatch between the reported currency and the advertiser's actual billing currency changes how monetary metrics read.

## Why does my StackAdapt connection show as deprecated?

StackAdapt has two connector variants in Adriel. The GraphQL variant documented here is the active one. An older REST-based variant is deprecated: existing widgets built on it continue to function, but the connector is flagged as deprecated in the connector picker.

New connections should use the GraphQL variant. Moving reporting off the deprecated REST variant means creating a StackAdapt data source with a GraphQL API key and rebuilding the affected widgets against it.

## Related

<CardGroup cols={2}>
  <Card title="How to connect StackAdapt to Adriel" href="/data-sources/o-z/stackadapt/how-to-connect">
    Step-by-step setup, including where the GraphQL API key goes.
  </Card>

  <Card title="StackAdapt data reference" href="/data-sources/o-z/stackadapt/data-reference">
    Metrics, breakdowns, refresh cadence, and limits for the data source.
  </Card>

  <Card title="The Trade Desk data reference" href="/data-sources/o-z/the-trade-desk/data-reference">
    Sibling DSP for programmatic media reporting.
  </Card>

  <Card title="Data history and retention" href="/data-sources/how-data-works/data-history-and-retention">
    How far back Adriel imports and stores connector data.
  </Card>
</CardGroup>