Skip to main content
Airship logo
Mobile Engagement integration

Airship + CaptiFi

Tag opted-in WiFi guests into your Airship audience as Named Users, ready to target in a push, in-app or email campaign. Included on Growth and above.

Overview

What does the Airship integration do?

The Airship integration is on the CaptiFi roadmap and is not yet live. When it lands it will sync the guest profiles captured on your WiFi splash page into Airship audiences for push notifications, in-app messages and SMS journeys. It is aimed at larger or multi-site operators who already run their own branded mobile app. Like every integration in the directory it will be included on the Growth plan and above.

The Airship integration tags the guests who opt in on your WiFi into your Airship audience. When a guest connects and accepts marketing, CaptiFi tags that person in Airship as a Named User, inside a tag group called captifi, with two tags. A site tag carries the venue ID, so you can target the venue they connected at, and source:captifi keeps WiFi-sourced people separable from the rest of your audience.

The Named User ID is derived from the guest's email address, as captifi- followed by a hash, so the same person stays stable across visits and their email address never travels in a URL. No name, email address or phone number is sent to Airship: only the derived Named User ID and the two tags. Guests without an email address are skipped, and only opted-in guests are synced.

CaptiFi tags people who already exist in Airship. It does not create a push channel or register a device, so a WiFi guest who has never installed your app has nothing to receive yet and the tags wait until they do. For this to line up, your app associates its channels with the same Named User ID scheme: captifi- plus the SHA-1 of the user's lowercased email, truncated to 24 characters. To reach WiFi guests directly by email or SMS instead, use Klaviyo, Mailchimp or Twilio SMS, or CaptiFi's own campaigns.

What you get

Why connect Airship to CaptiFi

Target the venue they connected at

Every tagged guest carries a site tag per venue they connected at, in the captifi tag group, so an Airship segment can cover one venue or every WiFi guest you have.

Nothing personal leaves CaptiFi

Airship receives the derived Named User ID and two tags. No name, email address or phone number is sent, and the Master Secret is stored write-only in CaptiFi.

Consent first

Only guests who accept marketing are synced. The sync runs within minutes of the sign-in and retries three times over roughly 20 minutes if Airship is unreachable.

One project per venue if you want it

Each venue holds its own App Key, Master Secret and data centre, so venues can point at different Airship projects. Test connection validates all three together and names the app it reached.

What data flows to Airship

Named User ID: captifi- plus a 24 character hash of the lowercased email
A site tag with the venue ID, in tag group captifi, one per venue the guest connected at
A source:captifi tag, in tag group captifi, on every guest CaptiFi sends
No name, email address or phone number
How it works

Up and running in minutes

1

Copy your App Key and Master Secret

In Airship open Settings, then APIs & Integrations, then Tokens or App Credentials. The App Key identifies the project and the Master Secret authorises tag changes. Note whether your project is on the US cloud (go.urbanairship.com) or the EU cloud (go.airship.eu): credentials are not interchangeable between them.

2

Configure the Airship card

Log in to my.captifi.io, open Integrations and click Configure on the Airship card. Enter the App Key, the Master Secret and the Data Center field, US or EU. The secret is stored write-only: after saving you see a Secret saved confirmation and a Replace link.

3

Test the connection and switch the venue on

Test connection fetches your app from Airship, so it validates the key, the secret and the data centre together. The venue reads Connected and paused until you flip the toggle to Enabled. Enabling applies to new guest connections from then on; guests already in your list are not back-filled.

4

Build a segment from the tags

Sign in as a guest with a fresh email address and accept marketing, then search the Named User ID in Airship under Audience. Create a segment on tag group captifi containing source:captifi for every WiFi guest, or the site tag for one venue, and use it as the audience of any campaign or journey.

Read the Airship setup guide

Step by step, with screenshots.

In the real world

How venues use Airship with CaptiFi

Hotel

A hotel group with a guest app builds an Airship segment on source:captifi and sends an in-app offer to guests who joined the lobby WiFi and already have the app installed.

Restaurant

A restaurant chain segments by site tag to send a push campaign to app users who connected at one branch, without the branch ever exporting a list.

Retail

A retailer running app loyalty targets WiFi-tagged Named Users in a journey, and the tags wait for shoppers who install the app later.

FAQs

Frequently asked questions

Is the Airship integration live?
Yes. Configure it from the Integrations page on my.captifi.io with your App Key, Master Secret and data centre. It is included on the Growth plan and above, alongside every other integration.
What does CaptiFi send to Airship?
A Named User ID derived from the guest's email address (captifi- plus a 24 character hash of the lowercased email) and two tags in the captifi tag group: a site tag with your venue ID and source:captifi. No name, email address or phone number is sent.
Does this create push channels or register devices?
No. CaptiFi tags a Named User who already exists in Airship. If a WiFi guest has never installed your app or subscribed to your Airship channels, tagging them gives you nothing to send to yet, and the tags wait until they do. Your app needs to associate its channels with the same Named User ID scheme.
Which guests are synced?
Only guests who accept marketing and give an email address. Guests without an email are skipped because the Named User ID is derived from it. CaptiFi sends a guest when they are first recorded at your venue, so a returning email does not produce a new sync, and enabling the integration is not retrospective.
Why does Test connection return 401 or 404?
A 401 means the App Key and Master Secret do not match, or belong to the other data centre. A 404 means the credentials are valid but the App Key is not a project on that cloud, almost always a US project configured as EU or the reverse. Getting the data centre wrong is the most common cause of a failed test.
Can different venues use different Airship projects?
Yes. Each venue holds its own App Key, Master Secret and data centre. Tags are only ever added, never removed, so a guest who visits two of your venues accumulates a site tag for each. Disconnecting a venue clears the stored credentials from CaptiFi and tags already applied in Airship stay where they are.

Start using Airship with CaptiFi today

30-day free trial. Cancel anytime.

Google, Gmail, Mailchimp, Klaviyo, HubSpot, Salesforce, Facebook, Meta Pixel, Slack, Zapier, Twilio, Tripadvisor, Yelp, Trustpilot, Untappd, Feefo, REVIEWS.io, Yotpo, Toast, Square, SumUp, Airship, Revinate, Leat, Pepper, EmailOctopus, MailerLite and Incentivio are trade marks of their respective owners and appear here only to identify the services CaptiFi connects to. CaptiFi is independent of these companies and is not sponsored, certified or endorsed by them. An integration marked coming soon is on our roadmap and is not yet available. Twilio and all related logos are trademarks of Twilio Inc. or its affiliates. Salesforce is a trademark of Salesforce, Inc. Slack is a trademark and service mark of Slack Technologies, Inc., registered in the U.S. and in other countries.

CaptiFi is a guest WiFi marketing and captive portal platform for restaurants, bars, pubs, cafes, hotels, gyms, salons, retail and short-term rentals, built by CaptiFi Ltd in the UK and sold in GBP, USD, EUR, CAD, AUD and NZD to venues worldwide.