# Visitor data mapping for targeting

Map integration data into named visitor context so operators and visitor events can use it.

*Release 3.3 · admin, developer, operator*

**Settings › Events › Visitor Data Mapping**

## What it is

**Visitor Data Mapping** gives agreed integration values names that operators and visitor events can use. You can choose which values appear when hovering over a visitor. Selected member values can also be saved with the visitor for later visits.

## Who uses it and why

- Administrators with the **Settings** or **Manager** role define mappings and decide what operators should see, subject to **View Only** restrictions.
- Developers supply the agreed values from the website or other supported context.
- Operators use mapped information to understand the visitor without asking for it again.

## Where to find it

Open **Settings › Events › Visitor Data Mapping**. The **Settings** or **Manager** role provides access, subject to **View Only** restrictions. Operators see values selected for **Show in hover** in visitor hover information.

## How it works

A mapping identifies a value from **Member**, **View**, **Order** or **Contact** data. Its **Name** is the display name, while **Variable** must agree with the integration's supplied value. The mapping also describes the data as **Number**, **String** or **Array**.

Member data describes the visitor or their website membership. View data describes the current page. These are separate sources; supplying a page value does not automatically create a saved member attribute.

For supplied member data, **Persist** selects values to save with the visitor. Unselected member values can still be available in current context without the same promise of continuity between visits.

## Configure it

1. Agree the source and variable with your developer.
2. Select **New**, enter **Variable** and a unique **Name**, then choose **Data Source** and **Data Type**.
3. Enable **Show in hover** if operators need the value there. Enable **Persist** for member values that should be retained.
4. Mark personal information with **This field contains PII**, set **Order** if needed, and save.
5. Test with a visitor whose integration supplies the value.

New mappings start with **Member** and **Number** selected. **Show in hover**, **Persist** and **This field contains PII** start off. A blank **Order** is saved as zero.

### Fields

| Field | Where | Required | What it is for |
|---|---|---|---|
| Variable | Settings › Events › Visitor Data Mapping | No | Identifies the agreed value supplied by the selected data source. |
| Name | Settings › Events › Visitor Data Mapping | Yes | Gives the mapping a unique display name. |
| Data Source | Settings › Events › Visitor Data Mapping | No | Selects Member, View, Order or Contact data. |
| Data Type | Settings › Events › Visitor Data Mapping | No | Describes the value as Number, String or Array. |
| Show in hover | Settings › Events › Visitor Data Mapping | No | Includes the mapped value in the visitor hover information. |
| Persist | Settings › Events › Visitor Data Mapping | No | Saves selected supplied member data with the visitor for later use. |
| This field contains PII | Settings › Events › Visitor Data Mapping | No | Marks the value as personal information for supported masking and display controls. |
| Order | Settings › Events › Visitor Data Mapping | No | Sets the mapping's display order. |

### Permissions

| Permission | Lets you |
|---|---|
| Settings | Manage visitor data mappings unless View Only is enabled. |
| Manager | Manage visitor data mappings unless View Only is enabled. |

## Limits and good to know

- A mapping does not generate a value that the integration has not supplied.
- Mapping names must be unique.
- **Persist** applies to selected member values, not every item of page metadata.
- Memory-only tracking omits supplied member data, but custom page data and page tags are still accepted. Keep personal information out of those payloads when it should not be collected.
- Marking a value as PII is separate from consent, retention and deletion controls.

## Depends on and works with

### This feature uses

- **Configured in** [Roles and permissions](ADM-008.md): Role access and View Only restrictions control mapping changes.
- **Configured in** [Customer identity and conversation visibility permissions](SEC-016.md): Personal-information permissions and masking affect displayed values.
- **Configured in** [Cookie consent and opting out](VIS-018.md): Restricted no-cookie tracking omits supplied member identity and member data.
- **Works better with** [Basket tracking](COM-019.md): Tracked order data provides order-context values for mappings.
- **Works better with** [Visitor and conversation information panels](CON-017.md): Visitor hover and context panels display selected mapped data.
- **Works better with** [Customer contact details](CRM-001.md): Contact information is another supported mapping source.
- **Works better with** [Visitor data mapping for customer identity](CRM-002.md): Supplied member information provides a source for visitor mappings.
- **Works better with** [Visitor event targeting conditions](ENG-002.md): Event targeting can use mapped values as conditions.
- **Works better with** [Visitor page and product tracking](VIS-003.md): Page tracking supplies current-page values for mappings that use View data.

### Used by

- **Configures** [Visitor and conversation information panels](CON-017.md): Visitor data mapping determines additional visitor information shown.
- **Configures** [Visitor event targeting conditions](ENG-002.md): Visitor Data Mapping defines the custom values available in event filters.
- **Configures** [Visitor data mapping for customer identity](CRM-002.md): Visitor Data Mapping selects which supplied member values are saved through Persist.
- **Enhances** [Visitor page and product tracking](VIS-003.md): Custom page data adds integration-defined context to tracked pages.
- **Enhances** [Browser language and device context](VIS-004.md): Mapped visitor information can contribute to language selection.
- **Enhances** [Visitor event updates to customer context](ENG-007.md): Supported custom visitor data can be changed by configured actions.
- **Enhances** [Customer contact details](CRM-001.md): Website-supplied visitor data can contribute contact information.

## FAQ and troubleshooting

### Why is a mapped value blank?

Check the selected source, variable spelling and value sent by the integration. Then confirm **Show in hover** if the missing value is in the hover display.

### Why does the value disappear on a later visit?

Check whether it is member data with **Persist** enabled. Page data is current-page context and may change with navigation.

### Why can I view mappings but not edit them?

Your **Settings** or **Manager** access may have **View Only** enabled. Ask someone with the **Settings** role to review your account permissions.

### Does PII marking encrypt the incoming data?

No. It identifies personal information for supported display controls. Ask Powerfront to review any separate encryption requirement for your integration.