Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Personalization API

Retrieve up-to-date personalization data from DinMo using a business identifier.

Overview

The Personalization API lets your application retrieve a record from a dedicated DinMo model using a business identifier. Use it to deliver recommendations, personalization, decisioning, scoring, or enrichment data to a website, application, or trusted backend service.

An API record contains the lookup key and the fields that you selected in its activation. DinMo keeps those fields up to date as the source model is refreshed.

The Personalization API is a native DinMo destination. It must be enabled for your workspace before you can use it. Contact your DinMo representative if it is not available in the activation destination list.

Performance and freshness

The API is designed for low-latency, real-time use cases: in-region p99 latency is below 30 ms. It supports 500 requests per second on a sustained basis and bursts up to 1,000 requests per second.

Data is refreshed when the underlying model is refreshed. With a five-minute model refresh cadence, the maximum expected data staleness is under five minutes. If a record is no longer present in the model, subsequent requests return 404 Not Found.

Security

All traffic is encrypted with TLS and requests require a Personalization API key. API keys provide read access to the Personalization API records in the workspace.

Call the API from a trusted backend or edge function. Do not expose API keys in browser or mobile application code. Rotate keys regularly and delete keys that are no longer needed.

How it works

  1. Create an activation from the model that contains the data you want to serve.

  2. Select the Personalization API destination.

  3. Choose a lookup key and map the fields to return.

  4. Run the activation. DinMo creates an exposure and an endpoint for the activation.

  5. Create an API key, then call the endpoint with a record identifier.

The endpoint is specific to an exposure. Its response schema reflects the lookup key and fields configured in that activation.

Typical use cases

  • Display product recommendations or personalized content.

  • Enrich server-side events with customer attributes.

  • Provide a decisioning service with a score or eligibility flag.

  • Retrieve a compact, current customer context at request time.

Next steps

PreviousGDPR Customer Rights
NextSet up the Personalization API

Last updated