{"title":"Process Event - Liquid Tag Reference","slug":"process-event-tag-reference","url":"https://support.storeconnect.com/articles/process-event-tag-reference","url_markdown":"https://support.storeconnect.com/articles/process-event-tag-reference.md","subtitle":null,"summary":"The `process_event` block tag loads a Customer Event\u0026#39;s data into scope so you can handle it during template processing. Wrap event-handling logic inside `{% process_event event %}...{% endprocess_event %}`.","type":"Developer_Documentation","video_url":"","keywords":"liquid, tags, process_event, block tag, customer events, storeconnect","last_modified":"2026-08-21T07:12:35+0000","body_markdown":"The `process_event` block tag loads a [CustomerEvent](customer-event-liquid-object-reference)'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 %}`.\n\n## Syntax\n\n\n```liquid\n\n{% process_event event %}\n  \u003c!-- Content here --\u003e\n{% endprocess_event %}\n```\n\n\nThe tag takes a single argument: the event to process — typically an item from the global `current_events` collection.\n\n| Property | Value |\n|----------|-------|\n| **Tag Name** | `process_event` |\n| **Type** | Block tag |\n| **Source** | Hydrofoil (core) |\n\n## Description\n\nInside 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.\n\nFor a complete walkthrough of reading events and firing analytics calls, see [Tracking Customer Activity with Events](tracking-customer-activity-with-events)."}