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

# Prerequisites

> What to have in place before engineering starts on an Almedia Link integration.

Engineering time for the SDK integration is short — about 15 minutes. The work worth doing
first is everything around it, so that a working integration can actually go live rather than
sitting behind a missing account or an unconfigured MMP.

## Accounts and access

<Info>
  **TODO(copy)** — which accounts a publisher needs, who issues them, and what they need to
  request. No account, portal or credential names appear in the source material for this site,
  so none are invented here.
</Info>

## Attribution

Almedia Link reports through your existing MMP. Pick yours and follow its setup page:

<CardGroup cols={3}>
  <Card title="Adjust" icon="chart-no-axes-column" href="/publisher/mmp/adjust">
    Configure Adjust for Link attribution.
  </Card>

  <Card title="AppsFlyer" icon="chart-no-axes-column" href="/publisher/mmp/appsflyer">
    Configure AppsFlyer for Link attribution.
  </Card>

  <Card title="Singular" icon="chart-no-axes-column" href="/publisher/mmp/singular">
    Configure Singular for Link attribution.
  </Card>
</CardGroup>

## Decisions to make before you build

<Info>
  **TODO(copy)** — the choices that are expensive to change later. Likely candidates, to be
  confirmed: where the entry point sits in the player journey, which rewarded experiences to
  enable, and which events matter for reporting.
</Info>

## Ready-to-launch checklist

<Info>
  **TODO(copy)** — a short checklist a publisher can work through and confirm. Best written
  last, once the pages above are settled, so it stays a summary rather than a second copy of
  them.
</Info>

<Note>
  Once these are in place, engineering can pick up the
  [integration guide](/technical/integration-guide).
</Note>