Entry page filter
The Entry page filter matches visitors by the first page they ever landed on in your site, such as everyone who entered through a blog article or a specific landing page. The entry page is remembered (first-touch), so the visitor keeps matching on every later page and on later visits.
Available on: all platforms.
How it's evaluated
What's remembered
On the visitor's very first page view, Personizely saves that page's path, for example /blogs/news/linen-care. The domain, query string and # fragment are not saved. Paths longer than 255 characters are cut at 255.
When it's overwritten
Never. The entry page is saved once per visitor and doesn't change on later pages or visits, even when the visitor comes back weeks later through a different page. It's the entry page of their first visit, not of the current one.
It starts over only when Personizely sees the person as a new visitor: after they clear cookies and site data, in a private window, or on another browser or device. Visitor data is kept in a first-party cookie and browser storage; the cookie lasts 1 year by default.
Targeting the current page instead
- Widgets: use the Pages rule to show a widget on the page the visitor is on now.
- Campaigns: the campaign's pages decide which current URLs it runs on.
- Landing page of the current visit only: combine the Pages rule with the First page view filter (new visitors), or use Page view history with During this session to check pages viewed in this visit.
Options
The filter reads: Entry page operator value.
Option | What it does | Values / default |
|---|---|---|
Operator | How the saved path is compared | contains (default), is, is not, does not contain, is empty, is not empty |
Value | The path or part of a path, for example /blogs/ | Text. Not shown for is empty / is not empty |
Behavior details
- Path only, case-sensitive, no wildcards. is must match the whole path exactly: /pages/about doesn't equal /pages/about/. Use contains for sections: contains /blogs/ matches every blog article.
- Market and language prefixes are part of the path. On a Shopify store with /fr/ URLs, a French landing page is saved as /fr/products/linen-shirt. contains /products/ matches it; is /products/linen-shirt doesn't.
- Query strings aren't saved. You can't tell /?utm_source=x and / apart here. Use the UTM parameters or Query string filter for parameters.
- Homepage entries are saved as /. To match only them, use is /.
Examples
- Content readers: Entry page contains /blogs/, with a popup offering a buying guide to visitors who discovered you through your articles.
- Landing-page cohort: Entry page is /pages/summer-sale, to keep a summer-sale bar visible for those visitors on every page.