Scenario: A Helpdesk survey uses a 30-day touch filter.
Behavior: LoyaltyLoop skips the email if the contact received a Helpdesk survey in the last 30 days. If the contact received a different survey (such as a Decision Maker survey) 10 days ago, the Helpdesk survey will still be sent.
Cross filtering expands touch frequency logic to evaluate contact history across multiple designated survey campaigns. Here is an example a transactional business may encounter managing a Closed Transaction survey and a Quoted Prospect survey each with a 90 day Touch Frequency Filter.
Scenario: A 90-day touch filter is configured with cross filtering between the Closed Transaction survey and Quoted Prospect surveys.
Behavior: LoyaltyLoop checks if the contact received either a Closed Transaction survey or a Quoted Prospect survey in the last 90 days. If either occurred, the contact is skipped for that survey launch.
Configuration
Helpdesk Survey: 30-day touch frequency filter (cross-filtering with Decision Maker)
Decision Maker Survey: 90-day touch frequency filter (cross-filtering with Helpdesk)
Evaluation Logic
Helpdesk Trigger: Checks the past 30 days. The contact is skipped if they received either survey within 30 days.
Decision Maker Trigger: Checks the past 90 days. The contact is skipped if they received either survey within 90 days.
| Triggered Survey | Last Survey Sent | Days Elapsed | Result | Reason |
| Helpdesk | Decision Maker | 20 Days | Skipped | 20 days is within the Helpdesk 30-day lookback window, the contact is skipped. |
| Helpdesk | Decision Maker | 45 Days | Included | 45 days exceeds the Helpdesk 30-day lookback window, the contact is included. |
| Decision Maker | Helpdesk | 45 Days | Skipped | 45 days is still within the Decision Maker 90-day lookback window, the contact is skipped. |
| Decision Maker | Helpdesk | 95 Days | Included | 95 days exceeds the Decision Maker 90-day lookback window, the contact is included. |
Important Rule Cross filtering does not equalize the filter durations across surveys. The triggering survey's configured timeframe always dictates how far back LoyaltyLoop checks the combined survey history.