Every known and anonymous visitor to a web page tagged using RPI Realtime’s JavaScript web client, and a call made directly to an RPI Realtime API method, results in the building up of a unique profile per discrete individual. Note that profiles are built up on a per-device basis, so if the same person views a web page in Chrome and also in Firefox, she or he will be treated as two visitors by RPI.
Visitor profiles are stored in an in-memory realtime cache. This means that latency is minimized when making decisions based on the information in the visitor profile.
A visitor’s profile can also be built up through the execution of realtime cache offers, and through database lookups using cached attribute lists.