> For the complete documentation index, see [llms.txt](https://help.recart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.recart.com/list-growth/popups/visitor-targeting.md).
# Visitor Targeting
Explains Visitor Targeting, which lets you show a different popup to new visitors versus existing subscribers.
Show the Right Popup to the Right Visitor — Every Time
Until now, every visitor saw the same popup regardless of whether they'd already subscribed.
That changes today. **Visitor targeting** lets you control exactly who sees each popup — based on whether Recart can identify them as a Klaviyo subscriber, a Recart SMS subscriber, or a brand new visitor.
### What you can do with it
* Show your welcome discount **only to new visitors**
* Show a loyalty or winback offer **only to existing subscribers**
* Run both popups at the same time — each visitor sees only the relevant one
* Exclude Klaviyo email subscribers, Klaviyo SMS subscribers, or Recart subscribers independently
* Show a popup **only to visitors in a Klaviyo segment** — see [Target Popups by Klaviyo Segment](/list-growth/popups/target-popups-by-klaviyo-segment.md)
### Main use cases
* **Parallel popups** — run a discount popup for new visitors and a loyalty, upsell, or winback popup for known subscribers simultaneously, with no overlap
* **Stop showing popups to visitors who already subscribed** — exclude existing subscribers entirely so they never see an acquisition offer again
Visitor targeting works with any trigger type and is fully independent of Pages, Geotargeting, and A/B testing.
### Where to find it
Visitor targeting is configured at the **individual popup level** — find it under **Display rules** in the popup editor. It's disabled by default, so you turn it on per popup and uncheck the visitor groups you want to exclude.
Klaviyo targeting requires an active Klaviyo integration under [Settings → Integrations](https://app.recart.com/integrations/klaviyo). For more information and the full capabilities of the Klaviyo integration, visit our [help article here](/integrations/email-and-sms-platforms/klaviyo-recart-integration.md).
If you have any questions, do not hesitate to [contact the Recart Support team.](/contact-recart-support.md) We'd be happy to help!
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.recart.com/list-growth/popups/visitor-targeting.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
