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

# AppsFlyer

> Configure AppsFlyer to attribute and report on Almedia Link activity.

This page covers configuring **AppsFlyer** so that Almedia Link activity is attributed and shows
up in your reporting alongside everything else.

<Info>
  **TODO(copy)** — the AppsFlyer configuration steps.

  This page is intentionally empty rather than approximated. Attribution setup is exactly the
  kind of content where a plausible-looking guess causes real damage: a wrong event name or
  partner ID produces an integration that appears to work and silently misreports.

  Needed, from someone who has done a real AppsFlyer integration:

  * Where in AppsFlyer the configuration lives, and what permissions it needs.
  * The exact event names Almedia Link sends, taken from the SDK repository rather than
    written by hand.
  * The partner or channel identifier to use for Almedia Link.
  * How to verify attribution is working, and what a correct result looks like.
  * Anything AppsFlyer does differently from the other two MMPs.
</Info>

## Verifying it works

<Info>
  **TODO(copy)** — how a publisher confirms the setup is correct before launch, and what to
  check first when numbers look wrong.
</Info>

<Note>
  Event names are owned by the SDK, not by this guide. When this page is written, take them
  from the [API reference](/technical/api-reference) so the two can never disagree.
</Note>

<Card title="AppsFlyer documentation" icon="external-link" href="https://appsflyer.com" horizontal>
  AppsFlyer's own documentation, for anything specific to their platform.
</Card>