This article explains what tests you should run before and after the mobile upgrade. This will help you make sure that your application is ready and you can upgrade successfully.
Before the upgrade: check the Accengage implementation
It is important to make sure that the Accengage SDK is correctly integrated into your application. This will help you to upgrade in the best conditions.
We listed a few steps to check the whole user process with Accengage, from opt-in to push reception.
1. Delete your application from your device.
If you are using an Android device, please delete the application via the device’s settings. This way you will also delete all your profile data.
Go to Settings > Apps & Notifications > Select your application > Storage & Cache > Clear Storage and Cleat Cache.
Back to your application > Uninstall
If you are using an iOS device, touch and hold the application > Delete App. This will automatically delete all your profile data.
2. Install the application again and enable notifications.
Note: If you implemented the GDPR methods, make sure you have opted into data collection.
3. Retrieve your Device ID, and make note of it.
If you need, please see our documentation explaining how to retrieve the Device ID:
4. Once you have your Device ID, enter it in the Test Tool
and check that:
you find your profile, with the install time matching when you reinstalled the application,
the value for the field Notification Enabled is Y,
the device Token is there.
Note: please keep note of your Device ID, you will need it after the upgrade, for the checks on Airship’s side.
5. If these 3 conditions are met, you can carry on and send yourself a test push
This video shows how to check your Device ID in the test tool and send yourself a push:
If you receive the push, the Accengage SDK was correctly implemented and you can start the upgrade.
If you don’t get the expected result for any of the steps listed above, please check your integration using our documentation iOS / Android, or contact your Technical Account Manager or our Support Team.
You can now start working on your application’s upgrade to Airship. Please see our documentation.
After the upgrade: check the Airship implementation
The unique device identifier in Airship is the Channel ID. When your audience is upgraded to Airship, for each device, a channel ID is created in Airship’s database with the same value as the Accengage’s Device ID.
1. Retrieve your Channel ID
Please see our documentation explaining how to retrieve a device’s channel ID.
Important: The channel ID in Airship must have the same value as the Device ID in Accengage before the upgrade.
2. Check your channel ID in the Airship Go dashboard
Go to Audience → Contact look-up. Search your channel ID and check it is present.
3. Check that your Channel ID is opted-in.
4. Check that your Channel ID has a token (called Push Address).
This token must the same as the one your profile had on Accengage.
5. You can now send your first message from Airship’s dashboard
See our documentation on how to send your first message.
Important: You should receive the notification only once.
6. Run the same tests as a new user
This will ensure you can engage with the new users installing your application with the Airship SDK.
You can either use another device to install the new version of your application for the first time or uninstall the application from your current device.
Note: if you remove the application from an Android device and reinstall it, Airship generates a new Channel ID.
On an iOS device, the channel ID remains the same. For this reason, we recommend using another device to install your application for the first time.
This video shows how to check your Channel ID with Contact Lookup and send yourself a push:
Important: we recommend that you also send a message to your upgraded device from the Accengage platform. This way you can make sure that you can still reach your device from Accengage, and that you receive the notification only once.
Note: if you used custom fields or Client IDs on Accengage, after the upgrade they will have been transferred to the Attributes and Named User IDs respectively in Airship. You can find them with Contact Lookup, under the Attributes tab for the custom fields, and the Tag Groups tab for the Named User ID (field NAMED_USER_ID).
If you could follow all the steps and get the expected result, the Airship SDK was correctly integrated into your application, and the upgrade was successful.
If you don’t get the expected result for any of the steps listed above, please don't release your app in production! Check your integration using our documentation iOS / Android, or contact your Technical Account Manager or our Support Team.