How to use interstitial landing pages?
SUMMARY
- Redirecting interstitials, landing pages, and banner ads.
- Optimizing the compatibility of different redirect features.
- URL interstitials, landing pages, and banner ads.
1. An Interstitial is a midway stopping point
In the URL redirect (short URL > interstitial landing page > destination URL). Typically, marketers place various branding or banner ads on this page, disallowing visitors to click or continue navigating until the countdown timer runs its course. Thus, it's ideal for sending messages or notifications to short-link users, as the interstitial attracts their attention during the timer countdown. Here are the primary guidelines:
- Set "redirect delay" to 0 if you want URLs to immediately redirect and not display interstitial pages.
- Content is hosted off-site and called through the URL (with many platforms and options available for hosting single web pages).
- The "Interstitial URL" setting takes your off-site webpage URL and loads the content into the center of our interstitial page.
- We reserve the header portion of our interstitial pages for placing banner ads directly.
- TinyCC users who have subscribed to a plan that includes “retargeting” can add custom HTML code to tags.
- If the codes are for banners, the ads will display in the center of the interstitial page header, just left of the down "Continue" button.
YouTube tutorial about using interstitials
2. Compatibility of Redirect Features:
- Interstitial pages (delay>0)
- Landing pages (interstitial URL)
- Custom HTML code (pixels, banner ads)
- Use of the Override referer
- Custom HTTP codes (301, 302, etc.)
Use all these redirect features in any combination and simultaneously, except for Custom HTTP status codes (which can't be used concurrently with any of the other features).
Note: A landing page may fail to appear even though you correctly set up an Interstitial URL (google.com, for example). For security reasons, many sites instruct browsers to not display their site in an iframe and use HTTP headers to achieve this:
x-frame-options: SAMEORIGIN or X-Frame-Options: DENY