Review the following FAQs to help resolve any questions about your real-time attribute deployments.
No. It will not resolve the configuration deployment. Treasure AI recommends that you request assistance from an administrator to troubleshoot the configuration failure.
Yes, the configuration status is available in both. The Audience Studio also includes existing journey states such as draft, live, and paused.
No. The Add Attributes button is disabled to prevent the interruption of the current configuration.
Counter attributes are not deleted when their events expire. Events within a counter are evicted from the real-time store once they exceed the counter's configured duration. When all events within the duration have been evicted and no Batch Backfill value has refreshed the base, the counter returns zero — but the attribute and its configuration remain intact.
You should delete an attribute when confident it is not used in any journeys or configurations; otherwise, a journey or configuration might fail if it is removed.
A Lookup Catalog attribute references external business data — such as product catalogs, coupon definitions, or sale schedules — keyed by a non-user dimension (for example, product_id). Unlike Single, List, Counter, and Import Batch attributes that store per-user values, Lookup Catalog data is uploaded from the cdp_lookup_catalog database via a Treasure Workflow sync workflow and queried at request time against that key.
The key difference is the lookup dimension: other attribute types answer "what do we know about this user?", while Lookup Catalog answers "what do we know about this product (or coupon, or item) for this user?".
Yes. In RT 2.0 (M2), Lookup Catalog attributes are first-class attributes and can be dragged and dropped into the Entry Criteria canvas in Audience Studio, just like Single or Counter attributes. This enables server-side gating — for example, returning a coupon section only when product_coupon.has_coupon == "true" — without requiring any conditional logic in the client.
Yes. Add the Lookup Catalog attribute columns to the Attribute Payload section of the Personalization configuration. The resolved values are returned under the attributes sub-section of the API response, alongside other attribute types.
Lookup Catalog data is batch-synced — it is not streaming. Changes to the cdp_lookup_catalog source table take effect only after the next Treasure Workflow sync workflow run. Check the workflow schedule and run it manually if an immediate update is needed.