I have some questions about Reverse ETL functionality and was wondering if additional documentation or guides exist on this topic.
 

Scenario:

A relative date query identifies users who requested quotes within the last 5 days with 10-day lead times before their arrival and do not have a confirmed booking. These users are flagged as TRUE via a trait (e.g., early_quote_user). From an initial group of 10 tagged users:

• 2 later convert to confirmed bookings (no longer meeting criteria).

• 3 new qualifying users are added as TRUE the next day

Key Questions:

1. Should the logic to mark converted users as FALSE be implemented directly in the SQL query?

2. If not explicitly handled, will those users' traits remain TRUE indefinitely?

3. Are there alternative methods to automatically transition users from TRUE to FALSE when they no longer meet criteria?