Prelanding pages: connect and measure the funnel
A prelanding page is an intermediate page before the main offer. Its purpose should be clear to the visitor, and every transition should retain the connection to the original click.
What a prelanding page is for
A prelanding page explains an offer context before the visitor reaches the main landing page or offer. It may describe a problem, summarize terms or ask questions when these serve a real user journey. An additional page is not a goal in itself: decide what information it provides and why that information cannot fit conveniently on the next step. Avoid invented testimonials, results or earnings promises. A direct route may be clearer for a simple funnel. Evaluate the extra step through observed behavior and correct measurement rather than the number of pages. Map the complete journey before launch and ensure every button performs the action it promises.
Connect prelander, landing page and offer
In this sequence, the prelander introduces the offer, the landing page explains details and the offer accepts the target action. Step names should reflect the actual route: do not add another landing page solely to complete a diagram. inotrack supports funnels containing prelanding, quiz, landing, offer and external URL steps. Steps can be reordered or disabled, with {next_url} providing the next destination. Build a minimal sequence and test it in a normal browser before introducing page variants. Check reordering and disabling separately: the remaining chain should lead to the expected destination without hardcoded links to an old stage.
Keep parameters and clickid through buttons
The original clickid connects a visit to a later conversion. inotrack funnels support passing clickid, sub parameters, geography and device context through the chain, but custom HTML and external URLs still require verification. A hardcoded button URL may bypass a required step and lose parameters. Use the supported macros, inspect the resolved URL and avoid encoding the entire query string twice. If a receiving network expects the identifier under another parameter name, map the value correctly. Do not replace clickid with a campaign or page number. Follow the route to the offer and return a test event to verify the complete connection.
Measure each step separately
Treat entries to a step, onward transitions and final events as different quantities. The inotrack drop-off report shows how many visitors reached funnel stages. Compare equivalent periods and segments; do not reconcile visits today with conversions tied to earlier clicks without accounting for the delay. A prelander button click is not a sale, and a missing onward transition does not always indicate a technical failure. A visitor may read the terms and leave. Verify event correctness before evaluating the page content. When comparing landing page variants, account for audience composition so a difference in country or device is not mistaken for a content effect.
Common mistakes during setup
A copied button pointing to another flow is a common problem. An unresolved macro arriving at a network as literal text is another. Parameters can also disappear when a URL already containing a question mark is assembled incorrectly, encoded twice or sent through an intermediate external redirect. Inspect the final URL after each transition instead of checking only the template in the editor. Keep test events separate during financial reconciliation. If a report shows an unexpected drop-off, inspect page availability, buttons and parameters before rewriting content. Retain the page version that produced the result so comparisons before and after a change remain reproducible.
Launch and change the funnel systematically
Choose one flow and one short chain. Verify the landing page upload and version separately from transition logic. Test with known labels, follow clickid, return a conversion and inspect the step report. Then test a mobile screen, navigating back and reopening the page. Record expected results before connecting working traffic. Change either the step content or its position at a time so you can explain a measurement change. The landing page feature guide covers hosting and versions, the flow guide explains routing, and the macro reference helps construct links and pass parameters to the receiving side.
Questions
Does every funnel need a prelander?
No. Add a step when it has a clear purpose for the visitor and you can measure onward transitions.
Is checking the first URL enough?
No. Follow every button through to the offer and return a test conversion carrying the same clickid.
Read next
Run inotrack on your own server
One command on a clean VPS, 10–15 minutes. Get your key right after you pay on the site, or a free one for 7 days.
Questions? Message us on Telegram: @SmokeJung.