Airship allows you to create a single customer view from multiple channels of data. The Airship connector can be set up at customer, group, or venue level, and pushes users’ data into Airship to create or update a contact, once they have authenticated into your Wi-Fi.
Set Up the Airship Connector
The connector can be set up at a customer, group or venue level.
Step-by-Step Setup Guide:
Step 1. Obtain your Airship Personal Access Token (PAT)
The first step is to obtain your Airship Personal Access Token (PAT). To connect to the Airship API you need to request the Account ID and Source Name from Airship Support: success@airship.co.uk.
The Personal Access Token (PAT) is found by logging into your Airship account and navigating to Users > Personal Access Tokens.
Click into Settings > API access, then through to access the token manager interface. Select ‘Create token’:
If any of the steps listed above aren’t available, it means the feature isn't yet enabled on your account. Contact success@airship.co.uk to have it enabled.
Select both ‘read’ and ‘write’, then give the token a descriptive name so it’s easily recognizable:
Your new token will be shown on the screen. Make sure you copy this before closing:
Step 2. Access the Portal WiFi Platform
Log in to your Portal WiFi account and navigate to the ‘Management’ section from the dashboard and select ‘Connectors’.
Find the Airship Connector from the list of available integrations.
Click on the ‘Add’ button to start the integration process.
Step 3. Set up your connector
After obtaining your Airship Personal Access Token (PAT) you can then create the connector in the WiFi Portal.
Input these details on the platform along with a name for the connector and the name of the group that data will be pushed to:
You will also need to decide which user levels will have access to use this connector:
If you select the customer level, then all venues within the customer will have access. If you select a group, then only venues within that group will have access.
Once you have completed the required fields, select ‘Verify’.
If you have set up custom fields at Airship and in the WiFi Portal then you can also set up a mapping for these after verifying your connector:
When you have finished configuring your connector then select ‘Save’.
Step 4. Test the integration
Complete an access journey through your WiFi and you should be able to see data coming through from access journey visits into Airship.
You’re connected!
Data Sent to Airship
The following data is sent to Airship to create or update a contact:
|
Data Type |
Data |
Description |
|
(integer) |
user ID |
The user's ID |
|
(string) |
firstName |
The user's forename |
|
(string) |
lastName |
The user's surname |
|
(string) |
|
The user's email address |
|
(string) |
postcode |
The user's postcode |
|
(string) |
mobile |
The user's mobile telephone number |
|
(string) |
gender |
The user's gender |
|
(string) |
title |
The user's title |
|
(string) |
dateOfBirth |
The user's date of birth in YYYY-mm-dd format |
|
(string) |
marketing status |
Whether the user has agreed to receive marketing |
|
(string) |
custom fields |
Custom fields and values |
The following consent status is sent to Airship for the contact:
|
Consent Type |
Data |
Description |
|
|
marketing status |
Whether the user has agreed to receive marketing |
|
SMS |
marketing status |
Whether the user has agreed to receive marketing |
|
Third party |
marketing status |
Whether the user has agreed to receive marketing |
The following data is sent to the Airship API for the Wi-Fi interaction data for the contact:
|
Data Type |
Data |
Description |
|
String |
venue name |
The venue name |
|
String |
device MAC |
SHA256 hashed MAC address of |
|
String |
venue name |
The venue name suffixed with 'Wi-Fi Splashpage' |