Protected Pages protect the real destination route. Smart Links screen traffic on your own routing, redirect, tracking, or campaign domain before the real page opens.
Choose Protected Pages when the real destination should own the first traffic decision.
Choose Smart Links when the routing or campaign domain should screen traffic first.
Use this side-by-side view when deciding whether page-level control or Smart Link protection fits the click path better.
| Question | Protected Pages | Smart Links |
|---|---|---|
| Where does traffic arrive? | Real destination page | Routing/link domain first |
| Best for | Landing pages, forms, signup pages, sensitive routes | Campaign links, tracking domains, redirect flows, affiliate paths |
| Decision location | Page-level | Link-level before destination |
| Main proof | Traffic Log tied to the protected route | Traffic Log tied to the click path |
| Can use together? | Yes | Yes, pair with Protected Pages when both link and destination need checks |
Use both when the click path and final destination each need their own control. For example, a Smart Link can screen the first click on a campaign domain, while the Protected Page keeps local Protected Page rules on the final landing page.
Smart Link protection can screen the click first, then page-level policy can manage local country, referrer, schedule, or repeat-visit controls on the destination itself.
Choose the page or routing domain where fake click protection or invalid traffic control will be easiest to verify.
Safer redirect-first handling gives you proof before hard blocking becomes necessary.
Use traffic decision logs to confirm the first pattern before adding more routes.
Start with one Protected Page or one Smart Link, verify the first decisions, then scale once the path is clear.
