A Gateway rule UUID is good correlation data but poor user-facing information.
When my custom block-page Worker receives cf_rule_id, I use it to retrieve the rule object and display the configured rule name.
The flow is:
cf_rule_id
↓
Gateway rules API
↓
configured rule name
↓
block page
If the API lookup succeeds, support gets a meaningful value such as:
Block Newly Registered Domains
If it fails, the Worker falls back to the original rule ID rather than failing the block page.
I also cache successful rule-name lookups briefly. Rule names change far less frequently than block events, so resolving the same ID for every request would add unnecessary API traffic.