> ## 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 Basis data source.

## Why don't I see all my Basis fields, or why do I see extra ones?

Basis is a free-format source, so the fields available in Adriel mirror the columns Basis includes in the Snowflake data share or the Amazon S3 export. The connector never adds, removes, or renames fields on its own.

The [data reference](/data-sources/a-f/basis/data-reference) lists the standard delivery fields present in most Basis accounts. An individual account can expose more numeric and percentage fields than those listed, depending on what its export includes. If an expected field is missing, the first place to check is whether that column is present and consistently named in the Basis export itself. Keeping column names and types stable across exports is the account owner's responsibility, since a renamed column in the source reads as a new field in Adriel.

## Why did a conversion count change a few days after it first appeared?

This is expected. Basis restates some post-click and post-view conversions as late-arriving data settles, so a value recorded for a recent date can shift shortly after it first appears.

The connector re-fetches a rolling window of the most recent days on each scheduled refresh, so restated figures update in place without a manual reconnection. Older dates outside that window are stable once cached. For the exact size of the rolling window and the refresh schedule, see the [data reference](/data-sources/a-f/basis/data-reference).

## Why do the creative report and line-item report show different numbers?

Basis delivers two separate report types: a creative-level report (`CREATIVES_DAILY_DELIVERY`) and a line-item-level report (`LINE_ITEMS_DAILY_DELIVERY`). Each is fetched and cached independently, and each data source is created for one report type only. Small differences between the two are normal because they aggregate delivery at different levels of the hierarchy.

Each data source's report type is fixed when the data source is created and cannot be changed afterward. To report on the other report type, create a new Basis data source and select it during setup. Widgets that draw on both levels see them combined through the standard Advertiser → Campaign → Line item → Creative hierarchy.

## How do I rotate my Snowflake or AWS credentials?

Basis does not use an HTTP API key or an OAuth token. Access is handled at the SDK level: Snowflake key-pair (JWT) authentication for data-share accounts, or Amazon S3 request signing for export accounts. Because there is no token to refresh, rotating credentials means editing the connection with the new values rather than reauthorizing in place.

To rotate, open the Basis data source and update the affected credential fields, then save. If the stored credentials become invalid, Basis requests fail with an `Access Denied` error, which surfaces as an authorization failure and can disconnect the data source until valid credentials are supplied. For the full field list and connection steps, see [How to connect Basis to Adriel](/data-sources/a-f/basis/how-to-connect).

## Why is deleted Basis data missing from reports?

Once an element is deleted on the Basis side, Basis stops including it in the share or export, so its data is no longer provided to Adriel. Deleted elements therefore drop out of reports going forward rather than being retained separately. If historical delivery for a removed campaign, line item, or creative needs to be preserved, that data has to remain available in the Basis export.

## Common issues

<AccordionGroup>
  <Accordion title="Why is a specific period of Basis data missing?">
    Basis is an offline connector — the customer's platform pushes a CSV to Adriel's S3 bucket, and Adriel replaces its data with whatever the latest file contains. If a period looks empty:

    * The CSV for that period may not have been uploaded.
    * The export template on the Basis side may have been changed to a narrower scope (for example, a template limited to "last month" excludes anything earlier).

    Confirm the file was delivered and that the export template still covers the requested date range.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Basis data reference" href="/data-sources/a-f/basis/data-reference">
    Metrics, breakdowns, refresh cadence, and limits for the Basis data source.
  </Card>

  <Card title="How to connect Basis to Adriel" href="/data-sources/a-f/basis/how-to-connect">
    Snowflake and S3 connection steps and credential fields.
  </Card>

  <Card title="The Trade Desk data reference" href="/data-sources/o-z/the-trade-desk/data-reference">
    Reference for another programmatic (DSP) source.
  </Card>

  <Card title="Refresh strategies" href="/data-sources/how-data-works/refresh-strategies">
    How Adriel caches and refreshes daily-cache connectors.
  </Card>
</CardGroup>