Profile
Profile is the attribute-serving half of personalization. You publish the attributes you want available on a live page — a loyalty tier, a last-viewed product, a predicted score — into a Store. Your site or app then asks for one customer’s attributes by their id and gets an answer back immediately, without querying your warehouse.
Profile is enabled per workspace. A platform administrator turns it on for your workspace — until they do, Personalize → Profile does not appear in your sidebar. If you cannot see it, ask a platform administrator to enable it. Within an enabled workspace, your role’s permissions still decide whether you can view or manage stores.
Where to find it
Navigate to Personalize → Profile in the left sidebar. The area has five tabs:
| Tab | What it is for |
|---|---|
| Overview | How to personalize using Stores, and the stores in this workspace |
| API | The read-by-id reference — the request to copy into your application |
| Playground | Run a live read against a real store without writing any code |
| API keys | Create and revoke the serving keys (svk_) your application authenticates with |
| Stores | The store list — create a store, or open one to manage its feeds |
Opening a store from the Stores tab takes you to that store’s own page, which has its own Overview, Feeds, and Refreshes tabs. The Profile tab row stays visible above it so you can get back.
How it fits together
- A warehouse Model produces the rows you want to serve.
- A feed attached to a Store copies a chosen set of that model’s columns into the store on a schedule, keyed by the model’s primary key.
- Your application calls the Profile API with that key and reads the attributes back as JSON.
The store is a cache: the warehouse remains the system of record, and the store holds a refreshable copy of only the fields you chose to publish.
Prerequisites
- A configured warehouse and at least one Model.
- A serving key, created on the API keys tab. It is a secret and belongs on your server — see Profile API.
Next Steps
- Stores — create a store and attach a feed to it.
- Profile API — the read-by-id endpoint reference.
- Playground — try a read before you write any code.
- Membership — the other surface: is-member verdicts rather than attributes.