Skip to main content
This section is for whoever signs off that the integration actually works — QA, release management, or the engineer doing the last pass before a build goes out. It is deliberately separate from the engineering docs: those describe how to build the integration, these describe how to prove it behaves correctly for a real player.

​
The three passes

Set up a test build

Devices and OS versions, which build talks to which backend, and how to force any SDK state from the Unity editor.

Test checklist

What a successful link looks like end to end, what a failed one looks like, and the order to test the experiences in.

Verify attribution

Confirm events are reaching Almedia, and the three failures that account for almost every problem on a live integration.
Work through them in that order. The first is a one-time setup per project; the other two run on every build that touches Link.

​
Two references worth having open

  • The best practices guide states the rules the player-facing placement is judged against — timing, dismissal, CTA wording, reward wording. It also carries two AI audit prompts that will grade a screenshot of your pop-up or entry point against those rules and return a pass/fail scorecard.
  • The MMP Setup pages list the exact settings and event names your dashboard should show, which is the reference to check a live integration against.
Attribution problems are quiet — nothing errors, and the symptom is players earning less than they should. If the numbers disagree and the cause is not obvious, send what you are seeing to [email protected] rather than changing settings to make the totals match.