For the complete documentation index, see llms.txt. This page is also available as Markdown.

Visitor Properties

Define what Crobox remembers about each visitor, and how it personalizes products and Sagent for them.

A visitor property is something Crobox knows about a visitor, such as their preferred fit, skin type, or whether they're a VIP customer. Experiences can then use it: you can target campaigns at it, a Recommender can match products to it, and Sagent can take it into account in its advice.

Visitor properties get their values from:

Open Settings → Visitor Properties. Properties are grouped by category, and each shows its Key, Name, Value type, and Status: Active when an experience uses it, Inactive when none does. A Sagent Context label shows the property gives Sagent extra guidance.

Visitor Properties is available when it's included in your plan. Contact your Customer Success Manager to enable it.

Create a visitor property

1

Open the form

Click Add Property. The Shopper Property Settings panel opens.

2

Describe the property

  • Category - The categories to group it under. Optional.

  • Value Type - The kind of value it holds: String, List, Boolean, Number, Datetime, or Object (JSON). Use List when visitors choose from fixed values, such as Narrow, Regular, and Wide.

  • Property Name - A readable name, such as Preferred fit.

  • Property Key - The key experiences and your website use to refer to the property, such as preferred_fit. It's filled in from the name, and can't be changed after saving. For a property your website sends, use the same key as in the pageview.

  • A visitor can have multiple values - Switch on when a visitor can hold several values at once, such as several skin concerns.

3

Add Sagent context (optional)

In Sagent Context (general), write guidance Sagent should follow whenever the visitor has any value for this property. For example, This shopper has a stated fit preference; keep advice practical.

4

Add the values of a List property

For a List property, click Add Property Value for each value, and give it a Name and a Key. For each value, you can switch on Set for:

  • Product Filtering - Only include products that match a condition, for visitors with this value.

  • Product Ranking - Give extra points to products that match, so they rank higher.

  • Product Benefits - Show benefit lines on matching products.

  • Sagent Context - Guidance for Sagent when the visitor has this value, under Conversation context for the Sagent. For example, This visitor needs wide-fit; frame around comfort and support.

5

Save

Save the property. It's available to your experiences right away.

Use visitor properties

  • Targeting - Show an experience only to visitors with a value, such as a campaign for visitors where vip is true.

  • Analytics - Filter reports and dashboards by a visitor property.

  • Product Finder - Link a question to a visitor property so the answer is remembered beyond the Finder.

  • Recommenders - Match products to a visitor's value with {{visitor.property_key}}. See Creating a Recommender.

  • Sagent - Sagent receives the context you wrote for a property or value when the visitor has it.

Frequently asked questions

Can a visitor property's value change?

Yes. A newer value replaces the old one, for example when your website sends a different value in a later pageview.

My website sends a property, but I can't target on it. Why?

Create a visitor property here with the exact key your website sends, and a matching Value Type. Until then, Crobox ignores the value.

Can I change a property's key?

No. The Property Key is fixed once saved, because experiences and your website refer to it. Create a new property if you need a different key.

What's the difference between general and per-value Sagent context?

Sagent Context (general) applies whenever the visitor has any value for the property. A value's own Sagent context applies only when the visitor has that value. Use both to give general guidance plus value-specific advice.

Was this helpful?