Process Event - Liquid Tag Reference
On this page
The process_event block tag loads a CustomerEvent’s data into the template scope so you can handle it during template processing. Wrap your event-handling logic inside {% process_event event %}...{% endprocess_event %}.
Syntax
```liquid
{% process_event event %} {% endprocess_event %} ```
The tag takes a single argument: the event to process — typically an item from the global current_events collection.
| Property | Value |
|---|---|
| Tag Name | process_event |
| Type | Block tag |
| Source | Hydrofoil (core) |
Description
Inside the block, the event’s type and event_data are loaded into scope. If the event carries additional objects — for example, the purchase event carries the order object — those are loaded into scope as well. When the block finishes, the event is marked as handled so it is not processed again on the next page load.
For a complete walkthrough of reading events and firing analytics calls, see Tracking Customer Activity with Events.
Was this article helpful?
Thanks for your feedback! It helps us improve our docs.