Landing pages

Direct users to a landing page when they interact with your message.

View as Markdown

See also the Landing pages feature guide.

Choosing an editor

If your landing page content is hosted outside Airship, configure it using Creating content: Custom URL. You do not use the Interactive or Visual editors for that path.

When Airship hosts your landing page, choose an editor for creating content: Interactive or Visual. For information about each, see Content editors. See the sections below for access steps and links to configuration details: Creating content: Interactive editor or Creating content: Visual editor.

Creating content: Custom URL

In the Content step for a push notification or in-app message, select Landing Page from the ActionsA configurable behavior that occurs when a user interacts with your message, e.g., opening a web page. menu, then click Custom URL and enter an HTTPS URL.

Creating content: Interactive editor

In the Content step for a push notification or in-app message, select Landing Page from the ActionsA configurable behavior that occurs when a user interacts with your message, e.g., opening a web page. menu, then click Interactive editor » Add content » Edit. Now you can configure the landing page:

If your landing page includes HandlebarsHandlebars is Airship’s templating language for personalization. Handlebars expressions use double curly braces wrapped around a content template, ranging from a simple variable, e.g., {{first_name}}, to complex evaluations of personalization data., you can preview how the content will appear. See Previewing personalized content.

  1. Click Add .
  2. Click Done.
  3. Click Done to exit the editor.

Now you are ready to complete the remaining steps in the composer.

Creating content: Visual editor

You can access the Visual editor in the Content step when configuring a push notification or in-app message:

  1. Under Actions, select Landing page, then Visual editor.
  2. Under Rich Page, select Create.

Now you can configure the landing page. Follow the steps in The Visual editor.

Hosting and page size

This information applies to content created using Airship. However, we suggest following these guidelines for your self-hosted content as well.

Content is hosted in a CDN, ensuring responsive load times for your users globally. Hosted content — including embedded CSS, images and JavaScript — is limited to 1.5 MB, however the ideal page size is much smaller, given the potential for degraded download speeds on cellular networks. We recommend that you optimize your images and HTML to keep total page sizes under 100 KB.

If you have additional assets to load, you can host them in another location and link to them. Airship offers additional asset hosting options as a Professional Service. Contact Airship Sales for more information.

iOS developer notes

The default behavior in the iOS SDK is to not display the landing page when the corresponding push notification is received while the app is in the foreground state. The logic behind this behavior is that you may not wish to interrupt or distract a user who is currently occupied with the app, only to ask them to visit a different part of the app.

If you need to display a landing page while the app is in the foreground state, replace the registry predicate associated with that action with one that allows foreground execution.

In the Airship SDK, this relative state between what the app is doing now and how the action was invoked is known as a situation, or more properly, ActionSituation . Other examples of situations besides foreground state include background push and app launched from push notification.

See ActionArguments for more detail on the methods involved with this display behavior.