Migrate to the New Unity Dashboard using Manage API v2
Migrate your Manage API v1 integration to Manage API v2 to move your production account to the New Unity Dashboard without losing programmatic capability.
阅读时间3 分钟最后更新于 20 天前
Manage API v2 is a new version of the Manage API. It gives you a supported path to migrate from the legacy Unity dashboards to the new Unity Monetization or Unity User Acquisition dashboards without losing any programmatic capability you rely on.
If you use the Manage API to manage your endpoints programmatically, update to Manage API v2 before you move to the New Unity Dashboard. For Monetization, the update applies to end points like apps, placements, or test devices for publishers. For User Acquisition, the update applies to endpoints like attribution, campaigns, campaign management, creative packs, or creatives for advertisers.
This article covers how to to do the following:
- Set up a test organization
- Validate your Manage API v2 integration
- Migrate your production account to the New Unity Dashboard
- Complete post-migration configurations
Set up a test organization
Create a new organization to test your Manage API v2 integration. To create a new organization, do the following in the Unity Dashboard.
- Create a test organization separate from your production account.
- Go to the Development dashboard > Manage organization > Service Accounts > Add (+) New to create a service account in the test organization. Doing so allows you to authenticate your API calls during testing.
- Add all Monetize or User Acquisition service account roles to your integration or match the current permissions your production service account currently has.
- Create your API key in the Keys section of your service accounts. You will use this key to authenticate requests from your test organization.
Validate your Manage API v2 integration
Replicate your existing Manage API workflows in the test organization to confirm that Manage API v2 supports your current workflows.
Where possible, duplicate your current production setup and configurations (including apps, placements, campaigns) inside your test organization. Mirroring your live environment makes it easier to confirm parity, so you can resolve any issues before migrating.
Refer to the following API reference to ensure you map your use cases correctly:
Migrate your production account to the New Unity Dashboard
Migrating your production account moves your existing configuration (for example, your apps, placements, campaigns, and other endpoints) and historical data to the New Unity Dashboard.
After you complete your test, migrate your production account to the New Unity Dashboard. Contact your account manager to schedule your migration. Alternatively, if you’re an Owner in your organization, select Join Migration Waitlist in the dashboard’s side navigation – this button is only visible to Owners and Account managers.
Migrations are scheduled for Wednesdays at Noon PST. If you join the waitlist, you’ll be scheduled for the week following your signup. If you join the waitlist by mistake, contact your account manager to avoid being migrated prematurely.
Complete post-migration configurations
After your migration is complete, create new service accounts and API keys for Manage API v2. Use them in your production API calls so your validated API workflows reflect your live organization. To complete these updates, follow these steps:
- Go to the Development dashboard > Manage organization > Service Accounts > Add (+) New to create a service account in your production organization used to authenticate your API calls. This service account is separate from the one you created in your test organization.
- Replace the test key and the test service account in your validated API workflows with the new key and the new service account tied to your live organization.
- Verify your API calls return correct data for your live apps, placements, campaigns, and other endpoints. Make any needed changes so your API calls align with your real, active organization.
If you notice any gaps or unexpected behavior in your API calls after migration, contact your account manager for assistance.