Path and survey traffic
The visitor is already moving through a question flow, and one of the questions was about selling their home. Your bridge page keeps that momentum for one short step, then hands them to our page with the address filled in.
Who just answered, and what happens next
They came for the question flow, not for us. They are in the habit of tapping answers, and that habit is the thing you are borrowing for one more short step.
The funnel, step by step
Short on purpose. The path does the first qualifying, your bridge page does the rest in one screen, and our page takes over.
Screen 1 of 4: a survey question on someone else's path site: Do you own a home you may sell?.
The path's question about selling a home The path
Somewhere in the flow the visitor is asked whether they own a home they may sell, and says yes. Only visitors who said yes should reach your bridge page. Everyone else stays in the path.
The bridge page Your page
One screen, three things: do you own the home, is it listed with an agent, and what is the address. Owners with an unlisted home go on. Non-owners and listed homes get a polite exit.
Hand-off Your page
Send the visitor to your tracking link with
street,city,stateandzipadded, plus the three sub IDs below. Build the link below.Our page finishes the job SellHouseFast
It shows the house, asks the last questions, collects name, phone and email under our consent text, verifies the phone with a text code, and sends the lead on. You do not build or host any of that.
The working example above is the path bridge kit. The one-step bridge is our recommendation, not something we have tested against a longer page.
What works, and how sure we are
Path traffic can be good, and it can change. Watch your own numbers every week.
| Tactic | How sure | What we know |
|---|---|---|
| Run path traffic, but only the compliant kind | From our experience | Path traffic has been strong for us when it is compliant. The word that matters is compliant: see the line below between a path and co-registration. |
| Watch the value of path traffic over time | Proven in our data | Revenue per click on path traffic has dropped over recent months. Do not assume last month's results hold. Check yours every week. |
Cut low-quality publishers by sub3 | From our experience our current practice | We already block weak publishers by their sub3 value on our side. Put the publisher in sub3 so you and we can both cut them quickly. |
| Keep the bridge page to one step | Untested | It is our plan, because every extra screen loses people who were only tapping along. We have not tested one step against several. |
Path is not co-registration
The line between them
The two look similar from outside, so we say it plainly.
In a path, the visitor knowingly answers a question about selling their own home and chooses to continue to our offer. Co-registration sells a visitor's details as a side effect of signing up for something else, which we do not accept.
The hand-off link
This is the only thing your bridge page sends to ours. Build it in JavaScript from the address the visitor confirmed. Try it here.
How to map your sub IDs
One standard for everyone. Your system may already use these fields for something else, so here is how to translate.
| If your system tracks | Put it in | Note |
|---|---|---|
| The site or domain that sent the click | sub1 | If you use the domain for something else, copy it into sub1 when you build the link. |
| Your own click or session ID | sub2 | Always the ID you can look up later. Never a campaign name. |
| The publisher, sub-publisher or traffic source ID | sub3 | This is what we cut by, so keep it as specific as you can. |
| The creative or path variant | sub3 | If you track both publisher and creative, join them in one value, for example PUBLISHER_CREATIVE. |
Your system puts the publisher in sub1 and the domain in sub3 | sub1 and sub3 | Swap them when you build our link, so sub1 is the domain and sub3 is the publisher. |
| Campaign, offer or placement IDs | sub3 | We have no separate field. Add it to the sub3 value, or keep it on your side against your click ID. |
What sub1, sub2 and sub3 mean
- sub1
- The source: the site or sending domain the traffic comes from.
- sub2
- Your own click ID, so you can match our results to your clicks.
- sub3
- The publisher or creative. This is the field we use to cut weak sources.
Events to fire from your page: prelander_view, qualified, address_confirmed, handoff. The full list is on the tracking page.
Compliance must-haves for path traffic
- The visitor knowingly answers a question about selling their own home, and chooses to continue to our offer.
- No details are sold, shared or passed on before the visitor reaches our page. You collect the address only, never name, phone or email.
- Terms and Privacy links that go to your own real policies, and a clear line saying who the visitor is dealing with.
- No urgency or absolute claims such as "guaranteed", "no fees" or "no inspections".
- No made-up qualification messages or invented property details.
- Send the publisher in
sub3on every click. Aim at the more densely covered areas on the coverage site, which lists the counties and ZIPs where we sell most reliably today. We take traffic from all fifty states, so nothing is blocked.
The full review list is on the compliance page. Ask us to review your bridge page before you spend.
Download the path bridge
The path bridge kit is the working example above: listed, address and a house confirm on one short screen, then the hand-off. Follow the back-end blueprint for the server side.