Using Campaign Landers with the Tapstream iOS SDK
First, integrate the latest iOS SDK.
Tapstream Campaign Landers let you automatically display a landing page to your users in a customizable, in-app modal.
You can provide a custom URL, some custom HTML, or use our lander builder to produce landers on the fly. You can add new landers and associate existing landers with advertising or marketing campaigns, without having to release app updates.
Using the Lander Builder
In most cases, you will want to use Tapstream's in-dashboard lander builder for your landing pages. The builder provides a variety of options to create a mobile-optimized lander. Within the lander builder, you'll find a field to provide a form action; this is the address to which your lander form will POST when it is submitted. You will want to point this at a service or server you control to collect the data and use it how you like.
The builder includes automatic support for MailChimp forms. To use a MailChimp form, enable the "Use MailChimp" toggle and provide your form action, user ID and list ID, along with the styling options for the automatically-generated email collection field. You can add additional fields from your Mailchimp list as regular form fields, as long as you match the field names (likely "MERGE1", "MERGE2", etc.)
If the lander builder doesn't suit your needs, you can provide either custom HTML or a custom URL to your lander. Make sure that all assets are served via HTTPS with an App-Transport-Security (ATS) compliant certificate. iOS will reject by default any loading of insecure content.
You can use Campaign Landers on iOS by integrating Tapstream's SDK.
If you use CocoaPods and have a
'Tapstream/Core' dependency, you'll need to add one on
'Tapstream/InAppLanders' (if you just use
'Tapstream' you're good to go).
Wherever in your app flow you would like your lander to open, after Tapstream has been
initialized, insert a snippet such as the following:
[[TSTapstream instance] showLanderIfExistsWithDelegate:nil];
If a Lander exists for this user, it will be displayed in a full-screen WebView window. Navigating away from the lander will close it.
The lander cannot not be shown before the app has finished launching, or before Tapstream has finished
initializing. If you would like to display the lander on application start-up, the
lifecycle hook is a good place for this, presuming that Tapstream was initialized during
Remember that any given lander will only be shown once per user.
For more control, you can implement a delegate conforming to the
TSLanderDelegate protocol, which looks like this:
#import "TSInAppLanders.h" @protocol TSLanderDelegate <NSObject> - (void)showedLander:(NSUInteger)landerId; - (void)dismissedLander; - (void)submittedLander; @end
The first method,
showedLander, is called when a lander is displayed, with that lander's
numeric ID. The second,
dismissedLander, is called when the lander is dismissed via the
close button in the top right corner. The final method,
submittedLander is called when the form is submitted.