Skip to main content
This page is the map: what happens, in what order, and who owns it. Every stage links to the page that carries the detail. Most of the calendar time is the commercial and attribution setup, not the build. Two stages run in parallel, which is what keeps it short.

​
The seven stages

1. Scope it — you and your account manager. Which experiences you want, and a check that your game is on Unity 2022.3 LTS or newer. See experiences. 2. Set up attribution — your growth or UA team. Start this now. It does not depend on anything below it, and it is the stage most likely to be waiting on someone else. See MMP setup. 3. Send what Almedia needs — you. App IDs, MMP events, and a deep link if you have one. The full list is on prerequisites. 4. Receive your keys — Almedia. Your campaign and offers are created, and your integration keys are issued. 5. Integrate — your engineers. About 15 minutes using the bundled UI. Building your own UI instead is measured in days rather than weeks. See the integration guide. 6. Test and review — your QA, with feedback from Almedia. The SDK ships an editor mock that drives every state from inside the Unity editor, so most testing needs no device build. See For QA. 7. Go live.
Stage 6 only means something after stage 4. Testing before the campaign exists and the keys are issued proves nothing, and it is where most “it doesn’t work” reports come from.

​
Where to go next

I am building the integration

Straight to the SDK and the integration guide.

I am getting us ready to launch

Accounts, attribution, and the decisions to settle before engineering starts.
Stuck at any stage? Your account manager is the route. They issue the keys, create the campaign, review your screenshots, and pull in Almedia engineers when the question is technical. Asking early is cheaper than testing against a campaign that does not exist yet.No account manager yet, or need a written record? Email [email protected].