How do quirks work with scoring, persistence, and updates?

Quirks are a powerful feature in the Uniform Platform that allow you to track visitor behavior and preferences. Here's how they work with scoring, updates, and data persistence:

Score Re-evaluation

Yes, scores are re-evaluated whenever a quirk is updated. When you call context.update() with new quirk data, the system re-evaluates all signal criteria including quirk-based ones.

However, if the updated quirk value is the same as the previous value, the score will NOT be added again. The system checks if the value differs from the current value before applying any scoring changes.

Quirk Persistence

Quirks persist across both page views and browser sessions. They are stored in multiple locations:

• localStorage - as part of the visitor data structure

• Cookies - via CookieTransitionDataStore if experimental quirks are enabled (for server-side access)

• In-memory fallback - if consent is not given or localStorage is unavailable (doesn't persist across sessions)

Duration of Persistence

Quirks persist indefinitely, as long as the visitor data persists on the visitor's device. Keep in mind that visitor data doesn't leave the visitor's device, so it only persists locally.

Important: Without proper consent, quirks only persist in memory for the current page session and will not carry over to future sessions.