Skip to content
English
More support Sign in
Go to patchretention.com
  • There are no suggestions because the search field is empty.

Filter By Events Block

How this block works and when to use it.

What's in this article

 

 

Summary

The Filter By Events block looks at a contact’s event history (orders, check-ins, etc.) within a date range, then filters and aggregates results.

Important:  A Patch admin will need to add this block to your campaign. Reach out to your onboarding rep or customer success to learn more. Email: success@patchretention.com

 

 

When to use

  • Target customers who checkec-in in the last 7 days
  • Find people who purchased but never checked in
  • Identify repeat visitors and send a membership offer
  • One time retroactive tagging

 

 

Best practices

  • Use short date windows so messages stay relevant (7–30 days).
  • Pair with Throttle to avoid sending the same offer repeatedly.
  • Use Aggregation (event_count) to trigger “VIP” style paths.

 

 

Examples

  • Business: event_count ≥ 2 in last 30 days → send membership upgrade offer.
  • Programs: orders in last 14 days but 0 check-ins → send “need help booking?” message.

 

 

Tabs in this block

Editor

This is where you configure the block. After you change settings, save the block so the automation uses the updated configuration.

Stats

Stats populate after the block runs for at least one contact. For most blocks, Stats are mainly for quick troubleshooting (example: times triggered and last completed).

Task Log

The Task Log is the best place to troubleshoot a specific run. Each row is one task (usually one contact) that passed through this block.

  • Time: when the task ran
  • Run Duration: how long it took
  • Contact: click the person icon to open the contact profile
  • View Payload: click VIEW PAYLOAD to see all data passed through the automation for that task
  • Task ID: helpful for internal debugging and support

Warnings & Errors

  • Errors must be fixed before the automation can be enabled.
  • Warnings do not always block enabling, but they usually mean something is missing or risky.
  • If you see an error or warning banner, fix it in the Editor, then re-open the block to confirm it is cleared.