The exact names Tie uses in your Klaviyo account, so you can build segments, flows and reports on them.

Metrics Tie sends to Klaviyo

Tie sends each shopper action as one of two metrics. Tie metrics are shoppers you already know. Tie Prospect metrics are new shoppers Tie identified for you.

Shoppers you know	New shoppers Tie identified	What it means
`Tie Page View`	`Tie Prospect Page View`	Viewed a page
`Tie View Item`	`Tie Prospect View Item`	Viewed a product
`Tie Add to Cart`	`Tie Prospect Add to Cart`	Added a product to the cart
`Tie Started Checkout`	`Tie Prospect Started Checkout`	Started checkout

You may also see tie_enrich. It records Tie updating a profile's attributes rather than a shopper action, so do not trigger flows from it.

Purchases are not a Tie metric. Flows and reports use your store's own Placed Order metric.

Names can differ slightly on older accounts, which may still show an older RevRoll prefix. To find them, search your Klaviyo metrics list for Tie, or for RevRoll on an older account.

Event properties

Each event carries the properties that apply to it.

Property	What it holds
`ProductID`	Product ID
`ProductName`	Product name
`Price`	Price
`Quantity`	Quantity
`Brand`	Brand
`ImageURL`	Product image URL
`Categories`	Product categories
`Items`	Every item in the cart
`ItemNames`	The names of every item in the cart
`CheckoutURL`	A link back to the shopper's checkout
`cart_id`	Cart ID
`referer`	The page the shopper came from

tie_customEvent_1 through tie_customEvent_10 carry custom values when your Tie team has set them up for you.

Metrics Tie reads from Klaviyo

Tie does not write these. Our data pipeline reads them incrementally for analytics, attribution and consent enforcement. They are discovered through the metrics API and read through the events API.

Opened Email
Clicked Email
Unsubscribed
Spam Complaint
Bounced Email
Placed Order

Profile properties Tie sets

Tie sets a property only when it has a value, and never blanket-overwrites a profile. How many properties you see depends on your plan.

Standard Klaviyo fields. email, plus first_name and last_name when Tie creates a new profile.

Tie properties. These carry an rr_ or Tie_ prefix and fall into these groups.

Demographics and household, such as rr_age, rr_gender, rr_income_hh, rr_home_price and rr_median_home_value
Location and contact, such as rr_city, rr_state, rr_postal_code, rr_country, rr_address and rr_phone_number
Interests and purchase behavior, the rr_ affinity fields and the rr_recent_ purchase fields
Identity and verification, such as Tie_verified_score_Lite, Tie_double_verified_Lite, Tie_email_source_Lite, rr_party_source and rr_email_last_seen
Tie Predict scores if you use Tie Predict, Tie_Purchase_Score, Tie_Open_Score and Tie_Click_Score

Consent handling

Consent is enforced before any write to Klaviyo. Tie's tracker and backend follow the same rules.

Consent signal	Handling
Email opt-in	Required
SMS opt-in	Required
Unsubscribed	Hard block
Spam complaint	Hard block
Hard bounce	Hard block

Subscription state is synced through Klaviyo's subscription bulk endpoints. Tie never overrides consent.

Tie's tracker adds its own safeguards. Email storage is disabled, blind writes are not allowed, blocking triggers are enabled, and personal data is minimized.

Tie also reads consent and suppression signals back from Klaviyo and uses them to decide whether a profile is eligible for export, whether it can enter the identity graph, and whether it is eligible for Tie Predict scoring.

How Tie uses your Klaviyo data

Identity graph stitching. Connecting anonymous visitors to known profiles using _kx identifiers and email matching. Data used: profile ids, _kx exchange identifiers, email addresses, event timestamps.

Profile enrichment. Adding demographic and behavioral attributes to Klaviyo profiles. Data used: age, gender, marital status, income and home value, interest affinities, purchase propensities.

Attribution and reporting. Reports on flow performance, segment metrics and campaign effectiveness. Data used: flow configurations, campaign metrics, segment definitions, event tracking data.

Klaviyo endpoints Tie uses

Endpoint	Purpose
`POST` and `PATCH /profile-bulk-import-jobs`, `/profiles`	Bulk profile sync
`POST /events`, `PATCH /profiles`	Enrichment job writes
`GET /profiles`	Retrieve profile data including email, properties and identifiers. Supports `_kx` filtering (`equals(_kx,'{value}')`) for identity resolution. Returns id, email, phone, properties, `_kx`
`GET /flows`	Flow configurations for reporting and attribution
`GET /lists`	List metadata for segment management and reporting
`GET /segments`, `POST /flow-series-reports`	Advanced flow performance metrics
`GET /campaigns`, `/events`, `/metrics`	Campaign data, event tracking and metric definitions for reporting and identity graph stitching

Klaviyo data reference: what Tie sends and reads