Ce contenu est également disponible en français.
The purpose of this article is to help you test the retrieval and validity of profiles following the upgrade of your Accengage web environment to Airship.
Accengage integration checkup before transitioning
First of all, it is important to check the integration of the Accengage SDK. This step will allow you to make your transition to Airship in the best conditions.
To validate this point, we recommend testing the entire opt-in process and the reception of push through Accengage.
For this, we invite you first to opt-out by deleting the data from your browser. For a step-by-step guide, see the article: How to get opt-out from web notifications?
When you have opted-out, go to your website to display the opt-in pop-up and accept the notifications.
Google Chrome :
In order to recover your new Device ID on Google Chrome, please follow one of the two methods:
-
From the Accengage platform: Go to the Accengage platform using the same browser (Target > Search > Want to find your Device ID?)
-
From your website: Right-click to display the menu, then click on Inspect item → Application → Storage → IndexedDB → ACC - "master domain" → settings → me → UDID
IMPORTANT: Please remember to check before the migration if you are using your own domain name or the master domain name Accengage. You will need this information to determine the tests to be completed following the upgrade (see below).
Check up after the Airship transition
If you were already opt-in on Accengage
If you were using your own domain name opt-in setup on Accengage
You can find all the details allowing the upgrade under your own domain name via the following Airship technical documentation: Accengage-upgrade-integration
It is important to follow the above implementation method before continuing with the next steps:
To test the migration of your Accengage environment you will need your Device ID (Accengage) as well as the Channel ID (Airship). This data can be retrieved using the same methods on the following browsers: Chrome, Firefox.
-
Go to your website to update your profile so that it can roll up on Airship.
-
Retrieve your Accengage Device ID by right-clicking to display the menu, then click on Inspect item → Application → Storage → IndexedDB → ACC - “master domain” → settings → me → UDID
-
Retrieve your Channel ID Airship from the site using the following method:
-
Apply the sdk.getChannel method in the console.
Important : Check that your Accengage Device ID and the Airship Channel ID are identical!
-
-
Check via the Airship’s Contact Look Up that the Device ID retrieved in step 2 is correct.
If this is the case, your profile has been successfully migrated. On the Airship side, your Device ID refers now to the Channel ID.
-
You can send a test push by targeting your Channel ID.
If you were using the Accengage master domain opt-in setup
You will be able to get all the indications allowing the Accengage master domain upgrade from the following Airship technical documentation:
https://docs.airship.com/platform/accengage-upgrade/#multiple-registration-domains
Make sure that you followed all the steps in the documentation above before you continue with the check-up that follows.
Go to your website, in order to allow your profile to get updated and retrieved by Airship.
Important: Make sure that the opt-in pop-up doesn’t get triggered on your website when using the sdk.register method on your browser’s console.
To test your upgrade compliance, you will need to retrieve your Device ID (Accengage) and your Channel ID (Airship).
-
Get your Accengage Device ID by right-clicking, then
Inspect element → Application → Storage → IndexedDB → ACC - “master domain” → settings → me → UDID
-
Get your Airship channel ID from your website via one of the two following methods :
-
Right-click to get the menu, then
Inspect element → Application → IndexedDB → X3..:db - domain → blob → channel → value → channel_id. -
Use the sdk.getChannel method within your browser’s console.
-
-
Note : With the Accengage Master Domain, you should have two databases “X3VhX3…..==:db” : (cf : screenshot above)
-
The first one includes your website url
-
The second one includes your Accengage Master Domain url https://your-hosted-domain-by.accengage.net.
This latter needs to include all your former Accengage profile information.Important: Make sure that your Accengage Device ID and your Airship Channel ID are similar!
-
-
Use the Airship Contact Lookup and check that the Device ID retrieved from step 2 rolls up properly.
In this case, your profile has been correctly migrated. Please note that on Airship side, this Device ID will now refer to the Channel ID.
-
Check the Named User and Attributes
If you were using custom fields, as well as customer IDs with Accengage after your transition, you will be able to retrieve this data directly in the Contact Lookup tool from the "Tag Groups" and "Attributes" sections.
-
Your customer ID will appear as Named_User_ID in the "Tag Groups" tab.
The named user must be sent the first time the application is opened after the combined SDK integration. This will allow this information to move to Airship and be used for your segments and campaigns. It will appear in the Contact Lookup in the Tag Group tab.
-
Your custom fields will keep their names in the "Attributes" tab.
Via the combined SDK, all attributes collected on Accengage and tagged on Airship will go back into the Airship database. However, these attributes will only be visible in the Contact Lookup if the call to the attribute method was made by the Airship SDK. Please find below a concrete example:
The "favorite product" field exists on Accengage, and your profile pulls up a value for this field on Test Tools from Accengage. This field is populated every time a product is added to your “favorite” basket. Following the install of the application with the combined SDK, your profile moves to Airship and is visible in the Contact Lookup tool. Until then, it is normal that the attribute is not visible in the Contact Lookup tool. For the attribute to be visible in the Contact Lookup, you need to add a product to your favorites or send the information the first time you open the application following the combined SDK integration.
The field will be populated on Airship and will be taken into account for segmentation.
If you want to make sure that the value is collected on Airship, you can create a segment with your Channel ID and the attribute. Via the audience estimator, you will be able to see if a profile meets the selected criterias.
-
-
You can now send yourself a test push from the Airship platform.
Please note that your profile is still valid on Accengage side, which also allows you to send a test push from this UI.
You are a new user
Thanks to the following indications, you will be able to check that your Airship implementation runs for your new users, then making sure they roll up compliantly.
-
Go to your website and opt-in thanks to one of the two methods below :
-
The opt-in popup if available.
-
Use the sdk.register method in your browser’s console.
This method allows you to get opt-in easily on any page that includes our SDK, in case you have a specific scenario to trigger your popup (purchase, login, etc)
-
-
Get your Airship channel ID from your website via one of the two following methods :
-
Right-click to get the menu, then
Inspect element → Application → IndexedDB → X3..:db - domain → blob → channel → value → channel_id -
Use the sdk.getChannel method within your browser’s console.
-
-
Use the Airship Contact Look Up and check that the Channel ID rolls up as expected.
-
You can now send yourself a test push from the Airship platform.
WARNING: Do not release your upgraded website into production if you encounter any error or problem; contact our support team and they will help you.
Please visit the following technical documentation for further information about the Web push channel: Getting started
Contact our support team if you have any questions in regards to those tests or if you encounter any errors.