---
title: "Real-time attributes | Snowplow Signals"
description: "Define what you want to know about a customer once. Signals computes it from live behavior, keeps it current and serves it to your app in milliseconds."
source: https://signals.snowplow.io/products/real-time-attributes
---

[Product](https://signals.snowplow.io/products) / Live attributes 

# What your customer is doing right now. 

Signals computes attributes such as categories viewed from each event and serves them to your app in milliseconds, in region.

[Start free](https://signals.snowplow.io/start) [Talk to an engineer](https://signals.snowplow.io/start?intent=engineer) 

What you see below is your own visit to this page, computed by Signals as you read. 

## Signals, about you 

connecting 

What Signals knows about your visit, right now 

Signals is computing your first attributes from the events this page just sent.

Every highlighted part is an attribute Signals computed from the behavioral data your browser sent during this visit. Open the Product menu above and watch the sentence change.

Show me how Signals knows this

Keyed on an anonymous session id. Signals drops these values a day after your last event. 

The problem

## What the customer is viewing reaches your product too late. 

Most customer data reaches your product as counts and scores, such as a propensity to purchase.

How it works

## An event becomes an attribute your app reads. 

We host it, or it runs in your own AWS or GCP account. Signals collects events with its own SDKs, updates what it knows within a second of each event, and answers a read in 6ms at the median and 10ms at p95, in-region.

1 definition 

Live from the stream, history from your warehouse

any key 

user · session · basket · listing · store

product\_view 

From your app, via SDK 

name **"Trail runner"** 

category **"trail"** 

price **64.00** 

Schema validated 

01 · Event in 

### A product\_view event on a pair of trail shoes arrives from your app via our SDK.

Signals validates each event against its schema on the way in, so an event that fails validation does not update the attribute.

product\_viewTrail runner 

<1s 

categories\_viewed Stream "road" \+ "trail" Window: last 10 minutes 

02 · Recomputed 

### An attribute named categories\_viewed gains trail, inside the 10-minute window.

<1s from the event arriving to the attribute being current. Windowing, late events and hot keys are handled in the engine, not in your code.

categories\_viewed **\[_"road"_, _"trail"_\]** 

Recommended for you Reranked this session 

Trail runner $64 trail 

Ridge trail shoe $96 trail 

Road racer $72 road 

1 2 3 

03 · Read back 

### Your ranker reads the attribute and reorders the shoe recommendations, in the same session.

Or a real-time trigger fires when a condition you set is met and sends it to your app or to a tool such as Braze.

Your app or model reads every attribute in a service with one call, from the Python or Node.js SDK or the REST API 

Your CI/CD deploys attribute groups defined in code, and each version keeps serving until you retire it 

Snowflake, BigQuery or Databricks backfills a new attribute's history on publish, from the same definition 

Works with 
* Snowflake
* BigQuery
* Databricks
* Vertex AI
* Amazon Bedrock

Capabilities

## Attributes that describe the moment, kept current for you. 

DEFINE IT ONCE 

attributes.py 

1 `_from_ snowplow_signals _import_ Attribute_,_ Event_,_ EntityProperty` 

2 `` 

3 `last_cart_value = _Attribute_ _(_ ` 

4 `name=_"lastcartvalue"_ _,_ ` 

5 `type=_"double"_ _,_ ` 

6 `events=_[Event(_ name=_"snowplowecommerceaction"_ _)]_ _,_ ` 

7 `aggregation=_"last"_ _,_ ` 

8 `property=_EntityProperty(_ ` 

9 `vendor=_"com.snowplowanalytics.snowplow.ecommerce"_ _,_ ` 

10 `name=_"cart"_ _,_ ` 

11 `major_version=1_,_ ` 

12 `path=_"totalvalue"_ _,_ ` 

13 `_),_ ` 

14 `)` 

<1s 

LIVE ON THE PROFILE 

**Shopper profile** domain\_userid 8c9104e3... 

shopper\_activity Stream 

product\_views\_last\_10\_min **2** 

last\_cart\_value **78.00** 

last\_category **"running"** 

KEY ON ANY ENTITY 

**User** u\_48213 

Stream 

product\_views\_last\_10\_min **4 5** 

categories\_viewed **\["trail", "road"\]** 

**Session** c41e7b0a... 

Stream 

product\_views\_last\_10\_min **2 3** 

last\_category **"trail"** 

**Basket** cart\_9f2a 

Stream 

adds\_last\_10\_min **1 2** 

basket\_value **78.00** 

**Store** denver\_04 

Stream 

product\_views\_last\_10\_min **1,283 1,284** 

top\_category **"trail"** 

ONE SHOPPER, ROLLING WINDOW 

**product\_view events** domain\_userid 8c9104e3... 

Older: fell out 10-minute window: counted 

camp 

camp 

road 

trail 

trail 

10:00 10:05 10:10 10:15 10:20 now 

<1s 

ATTRIBUTE VALUES NOW 

**Shopper profile** domain\_userid 8c9104e3... 

shopper\_activity Stream 

product\_views\_last\_10\_min **2 3** 

categories\_viewed **\["road", "trail"\]** 

ONE DEFINITION 

**categories\_viewed\_30d** 

events **product\_view** 

aggregation **unique\_list** 

property **category** 

period **30 days** 

version **1** 

**Streaming engine** Every new event, as it arrives 

Stream Now, <1s 

**Warehouse backfill** Runs on publish, so there is history on day one 

Snowflake BigQuery Databricks 

THE SAME ATTRIBUTE 

**Shopper profile** user\_id u\_48213 

categories\_viewed\_30d **\["trail", "road", "camp"\]** 

History from the warehouse Live from the stream 

**ML training set** Built from the same definition 

user\_id categories\_viewed\_30d bought u\_48213 **\["trail", "road"\]** 1 u\_51907 **\["camp"\]** 0 

01 

### Counts, recency, order and custom logic

How often, how recently, in what sequence. Or your own function, versioned like the rest.

DEFINE IT ONCE 

attributes.py 

1 `_from_ snowplow_signals _import_ Attribute_,_ Event_,_ EntityProperty` 

2 `` 

3 `last_cart_value = _Attribute_ _(_ ` 

4 `name=_"lastcartvalue"_ _,_ ` 

5 `type=_"double"_ _,_ ` 

6 `events=_[Event(_ name=_"snowplowecommerceaction"_ _)]_ _,_ ` 

7 `aggregation=_"last"_ _,_ ` 

8 `property=_EntityProperty(_ ` 

9 `vendor=_"com.snowplowanalytics.snowplow.ecommerce"_ _,_ ` 

10 `name=_"cart"_ _,_ ` 

11 `major_version=1_,_ ` 

12 `path=_"totalvalue"_ _,_ ` 

13 `_),_ ` 

14 `)` 

<1s 

LIVE ON THE PROFILE 

**Shopper profile** domain\_userid 8c9104e3... 

shopper\_activity Stream 

product\_views\_last\_10\_min **2** 

last\_cart\_value **78.00** 

last\_category **"running"** 

02 

### Key on any entity

user · session · account · basket · listing · store. A profile is whatever you say it is.

KEY ON ANY ENTITY 

**User** u\_48213 

Stream 

product\_views\_last\_10\_min **4 5** 

categories\_viewed **\["trail", "road"\]** 

**Session** c41e7b0a... 

Stream 

product\_views\_last\_10\_min **2 3** 

last\_category **"trail"** 

**Basket** cart\_9f2a 

Stream 

adds\_last\_10\_min **1 2** 

basket\_value **78.00** 

**Store** denver\_04 

Stream 

product\_views\_last\_10\_min **1,283 1,284** 

top\_category **"trail"** 

03 

### Windows and TTLs you choose

Ten minutes, this session, or since the last purchase. A value drops out when its window or TTL ends.

ONE SHOPPER, ROLLING WINDOW 

**product\_view events** domain\_userid 8c9104e3... 

Older: fell out 10-minute window: counted 

camp 

camp 

road 

trail 

trail 

10:00 10:05 10:10 10:15 10:20 now 

<1s 

ATTRIBUTE VALUES NOW 

**Shopper profile** domain\_userid 8c9104e3... 

shopper\_activity Stream 

product\_views\_last\_10\_min **2 3** 

categories\_viewed **\["road", "trail"\]** 

04 

### One definition, two engines

The streaming engine keeps it current, and on publish Signals backfills it from Snowflake, BigQuery or Databricks, so a new attribute has history on day one. The dataset builder makes a point-in-time correct training set from the same definition.

ONE DEFINITION 

**categories\_viewed\_30d** 

events **product\_view** 

aggregation **unique\_list** 

property **category** 

period **30 days** 

version **1** 

**Streaming engine** Every new event, as it arrives 

Stream Now, <1s 

**Warehouse backfill** Runs on publish, so there is history on day one 

Snowflake BigQuery Databricks 

THE SAME ATTRIBUTE 

**Shopper profile** user\_id u\_48213 

categories\_viewed\_30d **\["trail", "road", "camp"\]** 

History from the warehouse Live from the stream 

**ML training set** Built from the same definition 

user\_id categories\_viewed\_30d bought u\_48213 **\["trail", "road"\]** 1 u\_51907 **\["camp"\]** 0 

[Defining attributes →](https://docs.snowplow.io/docs/signals/attributes/) [See it in Snowplow Console →](https://signals.snowplow.io/products#console) 

What you can build

## Your app reads the visit as it changes. 

session 7f3a · one visit

1. [ 0:40 Searches three times, opens nothing searches\_session **3** result\_clicks\_session **0** Your search loosens the match. Search inputs → ](https://signals.snowplow.io/solutions/retail/search#dead-end)
2. [ 2:15 Opens one shoe three times product\_views\_session **{shoe: 3}** adds\_session **0** Your offer rules show a code. Offer targeting → ](https://signals.snowplow.io/solutions/retail/offers#hesitating)
3. [ 4:50 Adds it in two sizes product\_views\_session **{shoe: 3}** adds\_session **2** cart\_skus\_session **\[shoe-m, shoe-l\]** Your cart offers the fit guide. Fit prompts → ](https://signals.snowplow.io/solutions/retail/sizing#bracket)

Real-time attributes

## Frequently asked questions. 

### We already have a feature store. Why add this?

Keep it if it serves you. A feature store starts from features and assumes the events already arrive, and a live feature is only as current as the streaming job you run into it. Signals collects the events with its own SDKs, validates them against your schemas, and updates each attribute <1s after the event arrives. Signals calls each feature an attribute, and one definition serves the live value and builds the training set.

### How is this different from the profile in our CDP?

A CDP builds audiences around a person from past behavior and syncs them on its own schedule, often minutes to hours later. Signals computes what a customer is doing in this visit, keyed on whatever you choose, such as a session or a basket, and serves it to your app on request. It sits underneath the CDP rather than replacing it, and a real-time trigger can send the moments it notices to your other tools.

### What happens to an attribute when we change its definition?

You publish a new version of its attribute group, and every version is kept. A service pinned to the old version keeps serving it until you retire it, so an app reading the old version does not change under you. Definitions live in the Console or in code, so a change can ship through the CI/CD you have.

### Do we have to move off our warehouse?

No. Snowflake, BigQuery or Databricks stays where it is. When you publish an attribute, Signals backfills its history from the warehouse with the same definition the streaming engine runs, so the live value and the history agree. If you have no warehouse, Signals also runs streaming-only.

### What if next-day data is fine for us?

Then a warehouse tool is cheaper and you should buy that instead. Signals is for the ranker, the offer or the model that has to respond while the customer is still on the page.

## Start with one attribute. 

Add the SDK, define one attribute, and watch it update as you browse and search your own product. The free tier runs on the real engine: no card, no sales call.

[Start free](https://signals.snowplow.io/start) [Talk to an engineer](https://signals.snowplow.io/start?intent=engineer) 

Next up: [Identity resolution →](https://signals.snowplow.io/products/identity-resolution) and [Warehouse attributes →](https://signals.snowplow.io/products/warehouse-attributes) and [Real-time triggers →](https://signals.snowplow.io/products/real-time-triggers).
