How and why our landing pages work

Stripo offers a quick way to create small, page-like layouts directly in the email editor. Instead, you work with email layouts that you can make wider, so they look closer to a simple web page and solve very specific tasks inside your email workflows.

This format grew from real use cases. Email teams needed a quick way to create a support page around a campaign without leaving the editor, waiting for designers, or opening another tool. Turning emails into lightweight, page-like layouts became a practical answer to that need.

Key takeaways

Before we go deeper, here is what matters about Stripo “landing pages” and how they work:

1. They are not standalone landing pages and are created in the same email editor you already use.
2. They help teams publish fallback pages for AMP or kinetic content when subscribers cannot see interactive elements in their inboxes.
3. They close a gap in email workflows where a quick, focused page is needed without help from designers or developers.
4. The goal is to support newsletters and interactive mechanics, not to replace full landing page builders.
5. Early use showed that the team often needs small, attractive pages that can be published quickly for campaigns.
6. Future updates will target better control over layout width and a simpler way to add third-party code.

What these pages actually are

These pages are created inside the same email editor you use for newsletters. There is no separate landing builder and no second tool to learn. You work with the familiar drag-n-drop structure, only with a wider canvas that helps the layout look closer to a small web page.

The page is still an email layout at its core. The default width remains 600 pixels, but you can extend it when needed, which gives more room for text, visuals, or interactive blocks. This format lets you go beyond standard email boundaries without aiming to replace full landing page platforms.

Why this format was needed

Email teams often run into the same problem. A newsletter includes AMP or kinetic elements, but some subscribers cannot view them. Their email service blocks interactive formats, so the marketer needs a fallback version that shows the same idea without AMP. This includes common inboxes such as Outlook desktop and Apple Mail, which do not support AMP or Kinetic elements.

Why these examples are safe:

• Outlook desktop has never supported AMP or interactive email formats;
• Apple Mail does not support AMP and blocks most scripted interactive formats;
• all three are widely recognized as clients that require a fallback.

Creating that fallback in an external landing tool takes extra time, and involving designers or developers slows the process even more. These pages also help when you want interactive behaviour without setting up AMP inside your ESP. You can use the same email for the campaign and as a landing page, since the interactive elements that do not work in the inbox will still work on the published page.

In Stripo, you can create this page at the same speed as building an email. You stay inside the editor, reuse the same modules, and publish a clean support page without switching tools or waiting for production resources.

How these pages support email campaigns

These pages work as supportive assets for your newsletters. They help you keep the idea of the email clear for every recipient, even when some inboxes block AMP or kinetic elements and require a simple fallback.

You can also use them to show specific elements related to a campaign without asking the website team to update the main site. When you need a small, focused page for a promotion, a demo, or a campaign test, this format is quick to publish and keeps the flow inside the editor.

Early versions and what changed

In the first version of this feature, the editor always displayed a device switcher bar at the top. You could not hide it, and the page looked more like an email preview than a small standalone layout.

After updates to the editor, this bar can be removed. The page layout looks cleaner and fits better when you want to use it as a simple campaign page.

What we learned from the first version

The first version showed one clear pattern. Teams need many of these pages, and they need them fast. Campaigns move quickly, and a classic design and development cycle cannot match this pace. Marketers want to publish small support pages on their own and not wait for production resources.

What needs improvement

The next steps are already clear. Marketers need an easier way to add third-party code and more control over layout width, since the current limit is 900 pixels. Support for a custom domain and custom page name is available on Medium plans and above, which is a useful option for teams that want branded pages. Beyond that, the editor will benefit from general updates that make this workflow smoother.

Focus on internal workflow clarity

If you plan to build pages inside a product, start by keeping the workflow simple. Pages like these should be easy to publish without extra tools or long approvals. When the page solves a small task, removing steps from the process matters more than adding features.

Wrapping up

These pages cover a practical gap in email workflows. They help marketers create small support pages without switching tools or involving designers and developers. Their purpose is to complement newsletters and provide a fast way to publish fallback or campaign content, not to replace full landing page builders.