Data Fields - Auxia Docs

Data fields are variables containing user and behavioral information. They are the inputs that power personalization and targeting throughout Auxia — used in treatment content, guardrail rules, and decisioning.

Where Data Comes From

Data fields are populated from your data pipelines and integrations:

User profile data — ingested from your CRM or data warehouse (BigQuery, Snowflake, S3, etc.)
Event data — behavioral events sent via API or Pub/Sub
Contextual attribute data — delivered via Get Treatments API integration
Treatment interactions — automatically tracked by Auxia when users receive and engage with treatments

See the Data Ingestion section for how to connect your data sources.

Types of Data Fields

Type	What It Represents	Examples
User attributes	Properties of the user	`first_name`, `email`, `subscription_tier`, `country`
Event data	Clickstream data and user events with timestamps, automatically aggregated by Auxia into fields such as `days_since_last`, and counts of events in the last n days	`purchase_completed`, `page_view`, `signup_completed`
Contextual attributes	Real-time data delivered via Get Treatments API	`is_logged_in`, `article_identifier`
Treatment interaction metrics	How users have engaged with treatments	`treatments_viewed_last7d`, `days_since_last_treatment_sent`
Other entity attributes	Properties of a non-user entity, such as SKU data or article-level data	`article_category`, `product_identifier`
Derived data fields	Combinations and permutations of other data fields	Mathematical and logical combinations of other data fields (contact your Auxia point of contact if you need to set up derived data fields)
Model-generated attributes	Model-generated or system-recommended values stored as fields	For example, `recommended_next_category`, or `image_link_recommended_product`. Requires setup by Auxia. Contact your Auxia point of contact to enable these fields.

How Data Fields Are Used

Personalization

Dynamic variables in treatment content resolve to a user’s actual field value at serve-time:

"Hi ${first_name}, you have ${cart_count} items in your cart."

Guardrails (Eligibility Rules)

Data fields are the basis for treatment guardrails:

subscription_tier = "premium"
days_since_signup >= 30
last_purchase_date < 90_days_ago

Only users who satisfy the conditions receive the treatment.

Decisioning

Data fields are used by our algorithms to drive decisioning.

Analytics

Data fields are used to feed Auxia’s reports and display the impact of the platform.

Data Field Properties

Each data field has:

Property	Description
Name	Field identifier used in templates and rules (e.g., `first_name`)
Type	String, Number, Boolean, Timestamp
Source	Where the data comes from (user attribute, event, treatment interaction)
Description	What the field represents

Viewing Data Fields

Browse available data fields in Configuration > Data Management > Data Fields. This shows all fields available for use in treatments and guardrails.

Treatments — data fields power personalization and guardrails
Goals — value events are a type of event data field
Analytics — data fields power Auxia’s reports

How-to guides: Configuration · Data Ingestion Overview

​Where Data Comes From

​Types of Data Fields

​How Data Fields Are Used

​Personalization

​Guardrails (Eligibility Rules)

​Decisioning

​Analytics

​Data Field Properties

​Viewing Data Fields

​Related Concepts