Skip to content

docs(features): custom landing pages v1 guide with real screenshots (LIN-235) - #302

Merged
RathodDarshil merged 5 commits into
mainfrom
darshil/custom-landing-page-docs
Oct 21, 2026
Merged

RathodDarshil merged 5 commits into
mainfrom
darshil/custom-landing-page-docs

Conversation

@RathodDarshil

@RathodDarshil RathodDarshil commented Oct 20, 2026 •

Copy link
Copy Markdown
Collaborator

Rewrites the custom landing pages guide to the v1 scope: up to 50 pages per project, a check and fix flow, and a choice of which page each Meta campaign, ad set, ad or Linkrunner campaign link shows. Screenshots are now real dashboard states, and the page opens with a 46 second launch video. Draft: ships with LIN-235; do not merge or publish before the feature is live.

Related edge compression work: LIN-3886.

Changes

  • Launch video at the top of the page: a voiced walkthrough of a page per Linkrunner link, how it works and the five setup steps (no Meta in the video, on purpose). Hosted at media.assets.linkrunner.io/linkrunner-custom-landing-pages.mp4, with linkrunner-custom-landing-pages-thumbnail.jpg as the poster. Source: custom-landing-pages/ in video-workflow#1.
  • features/custom-landing-page.mdx now describes the v1 flow: library, upload (.zip with index.html or one .html, 10 MB), automatic check, Fix it for me (Required only or Everything), email when ready, review (before and after phones, slow network filmstrip, QR preview that does not count as a click), approve, then choose where it shows.
  • New "Choose where each page shows" section: default page, Meta web-to-app campaign, ad set or ad (most specific wins: ad, ad set, campaign, default, then the Linkrunner page), and Linkrunner campaign links, also from the Landing page field in the campaign form. Covers adset_id={{adset.id}} and ad_id={{ad.id}}, and the ad set fallback without ad_id.
  • Google web-to-app always keeps the Linkrunner page (removed from "when your pages are shown").
  • Removed the visitor results section and anything about a one-page-only setup. Kept the comparison table, "Before you upload", the fixes table, and updated troubleshooting. Added the "if you don't see Landing Pages in Settings, contact support" note.
  • Only checked pages can be picked, and a page in use cannot be deleted.
  • social-media-intermediary-page.mdx: one sentence updated to mention per-ad and per-campaign pages.
  • Images: 10 real light-mode dashboard screenshots (fictional app "Stride") from the dashboard PR evidence branch evidence/lin-235, cropped to the relevant panel, WebP, 27 to 89 KB each. The 10 old mock images are deleted.
Image Evidence state
library 01 library
upload 04 uploading
checking 05 checking
report 06 report
fixing 07 fixing
review, slow-network 08 review
approve 09 approve modal
where-they-show 12 where they show
campaign-picker 15 campaign form picker

Testing

  • Video: local mint dev preview plays it with the poster, not autoplaying, not muted, 46.6 s; both CDN files return 200 and match the local render byte for byte.

Custom landing pages page with the video under the title (local Mintlify preview)

  • npm run check:agents: 9 pass, 0 fail. npm run check:routes -- origin/main: 133 pages, valid.
  • mint broken-links: no findings for the two changed pages (it reports unrelated links in skills/).
  • mint dev renders /features/custom-landing-page (HTTP 200); all 10 image paths exist.
  • Not tested: the feature itself (not shipped), and the rest of the page visually after the final edit (only the top, with the video, was checked in a browser).

Risk / follow-ups

  • Re-check labels (for example Approve and go live, Where they show, Copy URL parameters) and the 50 page and 10 MB limits against the shipped UI before publishing.
  • Screenshots come from the evidence branch, not production.
  • The video files are already public on the CDN at unlisted URLs, so they can be found before launch. The video shows the fictional Stride app only.

🤖 Generated with Claude Code

RathodDarshil and others added 2 commits October 20, 2026 07:35
New page for uploading your own landing page in place of the Linkrunner
intermediary page: when it shows, how it differs, upload/check/fix/review/
go-live steps, what Linkrunner fixes vs what needs the customer, results and
troubleshooting. Screenshots use a fictional demo app (Stride). The
intermediary page's customisation section now points here.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…eenshots (LIN-235)

Up to 50 pages per project, choose where each page shows (Meta campaign, ad set,
ad, Linkrunner campaigns, default page), Google web-to-app keeps the Linkrunner
page, visitor results removed, screenshots replaced with real dashboard states.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@RathodDarshil RathodDarshil changed the title docs(features): custom landing page guide with screenshots docs(features): custom landing pages v1 guide with real screenshots (LIN-235) Oct 20, 2026
RathodDarshil and others added 3 commits October 20, 2026 13:25
…anding pages (LIN-235)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A 46 second voiced walkthrough at the top of the page, with its thumbnail as the
poster. Hosted on media.assets.linkrunner.io like the other docs videos.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@RathodDarshil
RathodDarshil marked this pull request as ready for review October 21, 2026 09:39
@RathodDarshil
RathodDarshil merged commit 0596870 into main Oct 21, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant