Chili Piper's Standard Data Fields List

Chili Piper automatically creates and manages several commonly used Data Fields to facilitate your initial setup and help you better understand where prospects come from, how they interact with your products, and how trustworthy inbound submissions are.

This article explains the most important Chili Piper–created data fields and how they’re commonly used across reporting, routing, and troubleshooting.

Table of Contents

• Mapping to CRM
• Default Person Data Field List
  • Chat Data Fields
  • UTM Tracking Fields
  • Spam Score Data Field
  • Additional Person Data Fields
• Default Company Data Fields List

Mapping to CRM

Some of these Data Fields created by Chili Piper are not mapped to a Salesforce field or HubSpot property. Mapping Chili Piper Data Fields to your CRM must be completed by a Chili Piper Admin. These fields are created by Chili Piper, but the prospect-provided data will not populate in your CRM unless they are properly mapped.

To map to a CRM field or property, expand the Mapping to (...) setting after opening a Data Field, then click Add Mapping

There, select the Object and Field or Property you want to map it to. Note that we will display the fields or properties that match your Data Field type. 

For example, if your Data Field is a picklist, we will show the picklist fields or properties from your CRM.

Toggle the Overwrite button to set if Chili Piper should overwrite any fields or properties that already have existing data:

Default Person Data Fields List

We will cover the default Person Data Fields list in Chili Piper in more detail. Information related to People/Contacts is stored in Person Data Fields.

Chat Data Fields

These fields are populated when using Chili Piper Chat and are especially helpful for understanding user intent and engagement context.
 

Chat Widget Recent Targeted URL

The most recent webpage URL where the Chat Widget was displayed or targeted to the visitor. This field shows where the chat experience was initiated, even if the visitor did not actively respond.

Common use cases:

• Understanding which pages are driving chat visibility
• Creating routing rules based on high-intent pages (for example, pricing or demo pages)
• Analyzing page-level engagement for chat campaigns

Example: https://www.chilipiper.com/pricing

Think of this field as: “Where did we show the chat?”

Chat Widget Recent Responded URL

The webpage URL where the visitor actively responded to the Chat Widget, such as by typing a message or clicking an option. This captures true engagement intent and is often more meaningful than merely displaying the chat.

Common use cases:

• Routing conversations based on page-level intent
• Prioritizing chats that originate from bottom-of-funnel pages
• Improving attribution for chat-driven meetings

Example: https://www.chilipiper.com/request-a-demo

Think of this field as: “Where did the user actually engage?”

UTM Tracking Fields

UTM Tracking Data Fields can be used across ChiliCal Scheduling Links (with Smart Parameters), Concierge, and Chat. They can also be used in your Rules setup.

Chili Piper automatically captures UTM parameters when they are present in the URL. These fields help attribute meetings, chats, and conversions to the correct campaign and channel. These fields preserve the initial acquisition source, even if the visitor returns later through a different channel.
 

Original UTM Fields

Original UTM fields store the first UTM values ever captured for a visitor.

• Original UTM Source
• Original UTM Medium
• Original UTM Campaign
• Original UTM Content
• Original UTM Term

Common use cases:

• Long-term attribution and ROI analysis
• Understanding first-touch marketing performance
• CRM lifecycle and cohort reporting

Note: Normally, these fields won't change in the future. Instead, Recent UTM-related ones (right below) will be updated.

Recent UTM Fields

Recent UTM fields store the most recent UTM values captured before a Chili Piper interaction. They show the last-touch attribution before a meeting, chat, or routing event.

• Recent UTM Source
• Recent UTM Medium
• Recent UTM Campaign
• Recent UTM Content
• Recent UTM Term

Common use cases:

• Identifying which campaigns are currently converting
• Comparing first-touch versus last-touch attribution
• Optimizing active marketing spend

Spam Score Data Field

Mostly used when the Spam Checker node is added to a Concierge Router. A numeric score generated by Chili Piper that indicates how likely a submission is to be spam.

This field helps protect your team from spending time on low-quality or automated submissions.

Please check this article for more details on the Spam Checker functionality.

Common use cases:

• Blocking/redirecting potential high-risk submissions
• Routing suspected spam to a separate workflow

Additional Person Data Fields

The following fields are also created and managed by Chili Piper but were not covered in the sections above. While many of these fields are self-explanatory, they are commonly used for routing, reporting, enrichment, and troubleshooting.

• Site Session Count
• Domain
• Company Name
• First Name
• Last Name
• Email
• Phone
• Industry
• Job Title
• Seniority
• Country
• City
• US State
• LinkedIn URL

Default Company Data Fields List

You can also find Data Fields already created by Chili Piper in the Company Data Fields page, which you can select in the header. Information related to Companies/Accounts is stored in Company Data Fields.

The list can be found below, with them being mostly self-explanatory:

• City
• Company Name
• Company Phone
• Company Size
• Company Size (Range)
• Country
• Description
• Domain
• Industry
• Latest Funding Amount
• Latest Funding Date
• LinkedIn URL
• Revenue
• Total Funding Amount
• Website