Native and display
We have little data here. This page says what we would try, and it is honest that most of it is untested. If you want to run a small paid test, we would like to hear from you.
Who just tapped, and what happens next
This is the lowest-intent traffic in this guide. They were curious about a headline and had no plan to sell.
The funnel we would try
This is a suggestion, not a tested recipe. It follows the Meta funnel with a story in front and stricter disqualifying.
Screen 1 of 6: a local news article with a card marked Sponsored by Your brand partway down.
The native ad Your ad
A card on a publisher's page. Say plainly who you are, and aim at the more densely covered areas on the coverage site.
An advertorial page, then stricter questions Your page
A short, honest article-style page that explains the offer and leads into the questions. Mark it clearly as an advertisement. The questions are the same as the Meta guide: do you own the home, is it listed, how soon would you sell. Send fewer people through. This traffic is cold, so let non-owners, listed homes and "just curious" leave on your side.
The address Your page
Collect the street address only, with autocomplete.
Show the house Your page
Display a picture of the home with one button: "Yes, this is my home". Only show details you can really source. Never show made-up bedroom or bathroom counts.
Hand-off Your page
Send the visitor to your tracking link with
street,city,stateandzipadded. Use the address, not personal details: see contact fields.Our page finishes the job SellHouseFast
It collects contact details under our consent text, verifies the phone with a text code, and sends the lead on.
The native advertorial kit has the article, the questions and the address steps. Write your own article copy.
What we know, and how sure we are
Not much. We would rather say so than guess.
| Tactic | How sure | What we know |
|---|---|---|
| Native traffic from the one network we tried | From our experience | It did not pay back, and we paused it. We tried only that one network, so this says little about native in general. |
| Advertorial-style pre-lander | Untested | It is the usual way to warm up cold readers. We have not tried it for this offer. |
| Stricter disqualifying than Meta | Untested | We expect cold readers to include more non-owners and browsers. We have not measured it. |
| Display banners | Untested | We have no result at all. |
| Start with a small paid test | Untested | Keep the first test small, aimed at the more densely covered areas, and tell us before you start so we can review your page. |
Tracking for native and display
- sub1
- The source. Use
native. - sub2
- Your own click ID.
- sub3
- The creative or placement, so we and you can see which ones earn and which to cut.
Contact fields: accepted, strongly discouraged
The hand-off link carries the address: street, city, state and zip (optional lat and lng). If you already hold the visitor's first name, last name, phone or email, our page accepts them in the link as firstName, lastName, phone and email.
We strongly discourage it. Links end up in browser history, server logs and analytics on both sides, so those details would sit there too. Our page collects them anyway, under our own consent text.
Use a token, not personal details, in links. When you send a visitor to one of your own pages, put a random token in the link, for example ?t=k3J9xQ2mP7vL8wRt. Your server looks the token up and finds the address. Make it random, single-use where you can, at least 16 characters, and let it expire after a few days. Never build it from the data itself.
The full list of events is on the tracking page.
Compliance must-haves for native pages
- The pre-lander is clearly marked as an advertisement.
- Terms and Privacy links that go to your own real policies, and a clear line saying who the visitor is dealing with.
- No fake news layouts, made-up testimonials or invented property details.
- No urgency or absolute claims such as "guaranteed", "no fees" or "no inspections".
- 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.
Not covered yet
These traffic types have no guide on this site. Talk to us before you run any of them.
- Push notifications
- We have no experience with push, so we cannot give advice yet.
- Pay-per-call
- We have paused calls for now, and calls come with separate rules and no partner terms yet.
- Co-registration
- We do not accept it, and we may refuse payment for it. See the line between a path and co-registration.
- Incentivized traffic
- We may refuse payment for traffic where the visitor was rewarded for clicking or signing up, and we have no guide for it.
- Messenger and direct messages
- We have set this aside for now and have no guide for it.