> ## 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.

# How to connect

> How to connect the Amazon Ad Server (Sizmek) data source to Adriel: enter API credentials, select an ad account, and verify data.

Amazon Ad Server (formerly Sizmek) is a third-party display ad-serving platform used to deliver, measure, and verify display, video, and rich-media creatives across the open web. Connecting it brings the ad account, campaign, ad set, and ad hierarchy into Adriel dashboards alongside delivery, engagement, video, cost, and conversion metrics.

## Before you connect

The following are required:

* An Amazon Ad Server (Sizmek) account with API access enabled.
* An **API Key** issued from the Sizmek admin. Refer to the Amazon Ad Server (Sizmek) API authentication documentation to retrieve it.
* An API **Username** and **Password** for the Amazon Ad Server account, which are exchanged for a short-lived session token.

Amazon Ad Server is distinct from Amazon DSP (the programmatic buying platform) and Amazon Ads (Sponsored Products, Brands, and Display on Amazon's retail surface). It is the ad-serving and creative management platform used alongside any DSP.

## Connect Amazon Ad Server

<Steps>
  <Step title="Authorize access to the account">
    On the **Data Sources** page, search for **Amazon Ad Server** and select it. Fill in the four required fields: **Connection Name** (an identifiable name for the connection), **API Key** (the key retrieved during preparation), **Username** (the ID of the Amazon Ad Server account), and **Password** (the password of the Amazon Ad Server account). Click **Submit** to authenticate.
  </Step>

  <Step title="Select the ad account">
    On the data source settings, choose the **Ad Account** to connect from the list.
  </Step>

  <Step title="Submit">
    Click **Submit** to complete the connection. Initial data availability can take up to one business day, after which the 365-day historical backfill is available.
  </Step>
</Steps>

## What gets imported

The connector imports the full campaign hierarchy (ad account → campaign → ad set → ad), performance metrics such as impressions, clicks, CTR, CPM, CPC, and spend, video metrics, and conversion events. Conversion events configured in Sizmek are fetched through a separate report and merged with the basic performance data, producing count, value, CPA, ROAS, and CVR variants per event. Breakdowns include creative type (display, video, rich media), placement label, geographic region, status, and flight dates.

For the complete list of metrics, breakdowns, refresh cadence, and limits, see the [Amazon Ad Server data reference](/data-sources/a-f/amazon-ad-server-sizmek/data-reference).

## Troubleshooting

<AccordionGroup>
  <Accordion title="Connection breaks despite a valid login">
    Authentication uses a static API key plus an auto-refreshed session token. If the API key is revoked on the Sizmek side, the connection fails even when the username and password remain valid. Reissue the API key in the Sizmek admin and reconnect.
  </Accordion>

  <Accordion title="Dashboard data lags recent activity">
    Reports are served from a cache and refresh on a fixed schedule rather than on demand, so the most recent hours may not appear until the next scheduled refresh. For the exact schedule, see the [Amazon Ad Server data reference](/data-sources/a-f/amazon-ad-server-sizmek/data-reference).
  </Accordion>

  <Accordion title="Conversions are missing while performance metrics are present">
    Performance and conversion data are fetched in two parallel reports and merged. If the conversion report fails while the basic report succeeds, only performance metrics appear on the most recent refresh. Subsequent refreshes typically reconcile the two.
  </Accordion>

  <Accordion title="Reach across long date ranges looks inflated">
    Cache-only delivery aggregates uniqueness-based metrics across daily snapshots, which can overvalue reach over multi-day ranges. This is expected behavior. Narrow the widget's date range to one day for a single-day view.
  </Accordion>

  <Accordion title="Authentication expired">
    Re-establish the connection from **Connections > Amazon Ad Server > Reconnect** using refreshed credentials.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Amazon Ad Server data reference" href="/data-sources/a-f/amazon-ad-server-sizmek/data-reference">
    Metrics, breakdowns, refresh cadence, and limits for Amazon Ad Server.
  </Card>

  <Card title="Amazon Ad Server FAQs" href="/data-sources/a-f/amazon-ad-server-sizmek/faqs">
    Common questions and expected behaviors for the Amazon Ad Server data source.
  </Card>

  <Card title="How to connect Amazon DSP" href="/data-sources/a-f/amazon-dsp/how-to-connect">
    Connect Amazon's programmatic buying platform.
  </Card>

  <Card title="How to connect Amazon Ads" href="/data-sources/a-f/amazon-ads/how-to-connect">
    Connect Sponsored Products, Brands, and Display.
  </Card>
</CardGroup>