Guest Identity gives the rest of your site a single, consistent picture of who the current visitor is, so personalized touches like greetings and “pick up where you left off” prompts can work without each feature figuring identity out on its own. It is a behind-the-scenes foundation for personalization, not a screen you configure.
What it does #
Different parts of a HomeRunner site each have a partial idea of who is visiting: whether they are logged in, whether they have a guest account, whether they have items saved, and what their browsing cookies say. Guest Identity pulls all of that together into one unified view of the visitor.
That unified view consolidates:
- Whether the visitor is a logged-in WordPress user.
- Whether they have a guest account record (the accounts created by Conversion Kit features).
- Their tracking cookies for the current session.
- Whether they currently have a wishlist or cart in progress.
Why it matters #
Personalization features work best when every piece of the site agrees on who the visitor is. Without a shared source of truth, one feature might greet a returning guest by name while another treats them as a stranger. Guest Identity removes that inconsistency by being the one place identity is resolved.
It is the groundwork for experiences such as:
- Personalized greeting copy for returning visitors.
- “Continue where you left off” prompts that resurface a saved search or property.
- Supplying context to the AI Concierge so its answers can account for who is asking.
Setup #
There is nothing to configure. Guest Identity is read-only: it reports who the visitor is and never changes their account, cart, or saved items. It simply needs to be active so the features that rely on it can read from a single, reliable source.
If the personalization features you expect are not behaving, the most common cause is the underlying guest-account feature being off rather than Guest Identity itself.
Guest Identity pairs naturally with Toolkit: Conversion Tracking for funnel measurement. For the full module list, see the Toolkit Overview.