Landing page editor.
One per recipient. One source of truth.
The landing pages your direct mail drives to should know who they’re talking to. The DirectMail.io landing page editor builds drag-and-drop pages with variable fields bound to the same recipient list that drove the mail piece — so the page the recipient lands on names them, references their context, and offers what aligns with their record. Forms route to your CRM with full recipient attribution. A/B tests run without reprinting the mail. The page and the mail piece become two surfaces for the same campaign — not two separate projects to keep in sync.
Five steps. One editor. Per-recipient pages.
- 01
Build the page from drag-and-drop blocks
Hero blocks, form blocks, video blocks, booking widgets, testimonial blocks, offer blocks, FAQ blocks. Drag, drop, configure. The editor produces a fast, mobile-first landing page on the platform CDN.
- 02
Bind variable fields to the same list as the mail
The page includes variable fields for any column on the recipient list. Hero headline, offer amount, account tier, nearest store, vehicle in inventory — whatever drove the variable mail piece flows into the matching landing page automatically.
- 03
Wire the dynamic QR or PURL to route per recipient
Each recipient on the campaign list gets a unique URL or QR code. Scanning or visiting the URL routes through the platform redirect, captures the visit event with recipient ID, and lands them on their personalized version of the page.
- 04
Convert through forms, calls, bookings, or e-commerce
Form submissions post to the platform with the recipient ID attached. Tracked phone numbers tie calls back to the recipient. Calendar bookings, e-commerce checkouts, and store-walkin redemptions all attribute back to the originating campaign.
- 05
Optimize without reprinting the mail
Page edits, A/B tests, and offer changes deploy instantly. The QR codes and PURLs on the printed mail keep working — they just route to the updated page. Mid-campaign optimization is a real workflow, not a "next time" plan.
Why the landing page lives in the same platform as the mail.
A landing page tool that doesn’t know about the mail piece can only render the same content to every visitor. Personalization stops at the URL parameter level — and most marketing teams stop using URL-parameter personalization within a quarter because the maintenance overhead exceeds the value. The personalized landing page that knows the recipient by record only exists if the page tool and the recipient list live in the same platform.
The compounding lift is on attribution. A scan event and a form submission tied to the same recipient ID, captured in the same platform, with the originating mail piece as the campaign source, ties revenue back to the variable that drove it. Generic landing-page tools require a stitching layer (UTM parameters, hidden fields, third-party identity matching) and the stitching breaks at scale. In-platform attribution does not.
The third structural advantage is mid-campaign optimization. The QR code on the mail piece is fixed once it prints. The destination behind that QR code is not — and the team can swap offers, fix bugs, run A/B tests, or redirect traffic to an entirely different page without touching the mail in transit. A "campaign post-mortem" stops being the moment to learn; mid-campaign becomes the moment to learn.
Where the editor earns its keep.
-
Form-fill lead capture
Mail drives the recipient to a personalized landing page with a pre-filled form. The form submits with full recipient context attached, and the lead routes to the right CRM owner with the campaign attribution intact.
-
Calendar booking
Service businesses (financial advisors, healthcare, professional services) drop mail with a personalized booking page. The recipient picks a slot; the appointment lands on the right calendar with recipient context and campaign source.
-
E-commerce promo redemption
Brands drive recipients to a personalized landing page with a pre-applied promo code (recipient-unique for fraud prevention). Checkout attribution ties revenue back to the mail piece and the originating recipient.
-
Video walkthrough + soft CTA
High-consideration verticals (B2B, real estate, automotive) use personalized video pages — the recipient lands on a page with a video addressing their specific situation, plus a low-friction next step (booking, callback, walkthrough request).
Questions teams ask before deploying.
Short answers. For implementation specifics on custom domains, CRM routing, or A/B test configuration, book a demo.
-
What is a personalized landing page (PURL)?
A personalized landing page composes per recipient from the same list that drove the mail piece. The recipient sees their name, their context, the offer that aligns with their record, and any variable imagery tied to their data. The page exists at a unique URL (the PURL — personalized URL) that ties scans, visits, and conversions back to the originating recipient. It is the digital twin of the variable mail piece — same data, same context, different surface.
-
How is this different from a generic landing page tool?
Generic landing-page tools (Unbounce, Instapage, Webflow) build the page but do not connect to the recipient list driving direct mail. The team has to maintain a parallel "static" landing page, then somehow stitch attribution between the mail piece and the digital conversion. The DirectMail.io landing page editor lives inside the same platform as the mail piece, the list, and the variable data — so personalization, attribution, and downstream automation all run automatically. There is no stitching layer to maintain.
-
What blocks are available in the editor?
Hero blocks (headline, subhead, CTA, hero image — all variable-aware), form blocks (custom fields, validation, post-to-CRM), video blocks (YouTube, Vimeo, self-hosted), booking blocks (Calendly, HubSpot Meetings, native calendar widget), e-commerce blocks (Shopify, BigCommerce, custom checkout), testimonial blocks, offer blocks with countdown timers, FAQ blocks, and embed blocks for arbitrary HTML or third-party widgets.
-
Can the page run on a custom domain?
Yes. Pages can serve from a campaign-specific subdomain on a customer's own domain (for example, offer.brand.com), or from the platform default short domain. The custom domain configuration is a one-time setup with DNS records the team adds; after that, every campaign launches under the brand-owned URL automatically.
-
How do form submissions and conversions get back to our CRM?
Form submissions post to the campaign with the recipient ID attached, and the platform routes them to downstream systems via REST API or webhook. Native CRM integrations exist for Salesforce, HubSpot, and the major automotive DMS platforms; custom destinations route through the webhook layer. Every form submission carries the originating recipient context — the CRM record updates with the campaign that drove the conversion, not just the form data.
-
How fast do the pages load and are they mobile-optimized?
Pages serve from the platform CDN with edge caching, optimized images, and minimal JavaScript. Typical load times are under one second on a modern smartphone connection. The editor enforces mobile-first responsive layouts by default — pages render correctly on phone, tablet, and desktop without per-device editing. Speed and mobile rendering are the conversion lever; the editor does not let teams ship pages that fail on either dimension.
-
Can we A/B test landing page variants?
Yes. Different recipient cohorts route to different page variants behind the same dynamic QR or PURL — same printed code, different destinations. The platform reports per-variant scan-to-conversion. The team can run offer tests, headline tests, hero-image tests, and form-field tests without changing the mail piece, the QR code, or anything in production.
Build a personalized landing page on a sample list.
Bring 50 records and a brief. We’ll build the page, bind the variable fields, configure the form-to-CRM route, and walk through the A/B test setup — in 30 minutes.