# What does the event type `REENTRY_BLOCKED` mean?

This means the contact qualified for the journey, but was not entered because of the re-entry criteria (frequency capping) for this journey. These events are included in the journey history to bring transparency to re-entry decisions.



# Table Fields

🚧

Beta

The journey history schema is in beta and may change with little or no notice.

## `ADVANCEMENT_TIME`

• Included for all event types

• Contains details associated with time calculations.

Possible values include:



## `BRANCH_NAME`

• Included in the `BRANCHING_SPLIT` event type

• The branch to which a contact was assigned in a branching split.



## `CHANNEL_ACTION_NAME`

• Included in the `ACTION` event type

• [Channel Action](🔗) used in this step



## `CHANNEL_NAME`

• Included in the `ACTION` event type

• Channel used in this step (for example, Attentive)



## `ENTRY_ID`

• Included for all event types except `REENTRY_BLOCKED`

• An ID for the traversal by one contact through the journey: all the steps will share this ID for that contact's one traversal from exit through exit. Contacts that pass through the journey multiple times will have one `entry_id` for each time they do so.



## `EVENT_ID`

• Included for all event types

• Unique <<glossary:GUID>> for each row



## `EVENT_TYPE`

• Included for all event types

• The event type. Possible values are: `ENTRY`, `EXIT`, `REENTRY_BLOCKED`, `ACTION`, `BRANCHING_SPLIT`, `EXPERIMENT_SPLIT`



## `JOURNEY_ID`

• Included for all event types

• Journey ID (System ID for the journey, not displayed in the UI) ***

## `JOURNEY_NAME`

• Included for all event types

• The name of the journey this contact is traveling through



## `JOURNEY_VERSION_NUMBER`

• Included for all event types

• Monotonically increasing version number (starting at 1)



## `LOADED_AT`

• Included for all event types

• Timestamp for when this data was loaded into Snowflake



## `METADATA`

• Included in the ACTION even type (if metadata was included it in the journey creation)

• The fields and values for this step and contact, in a nested JSON format



## `OPERATION_ID`

• Included for all event types except `REENTRY_BLOCKED`

• A unique ID for a contact going through that step at that time. This value is also available in personalization as `simon.operation_id` and is useful for tying step activity to other data sources, e.g. engagement data.



## `SIMON_ID`

• Included for all event types

• Each contact that exists within Simon is assigned a unique ID called `simon_id`. This is a consistent ID that’s managed by Simon.



## `SKIPPED`

• Included for all event types

• Boolean to indicate if contact was skipped for this step



## `SKIPPED_CATEGORY`

• Include for the `ACTION` event type (only if skipped)

• A (text-based) classification for the skip reason (e.g. ‘channel_not_deliverable’).



## `SKIPPED_DESCRIPTION`

• Included for the `ACTION` event type (only if skipped)

• The skip reason description (e.g. 'Not deliverable to channel').



## `SKIPPED_SUB_CATEGORY`

• Include for the `ACTION` event type (only if skipped)

• A (text-based) detailed classification of the skip reason (e.g. ‘invalid_phone_number’)



## `STEP_ID`

• Included in all events except `REENTRY_BLOCKED`

• Unique ID for a journey step (note: this is version-specific). (This step ID is not displayed in the UI).



## `STEP_NAME`

• Included in all event types except `REENTRY_BLOCKED`

• The user-configured name of the step (the builder enforces that each step has a unique name within that version).



## `TIMESTAMP`

• Included in all event types

• Event timestamp



## `VARIANT_NAME`

• Included in the `EXPERIMENT_SPLIT` type

• The variant to which a contact was assigned in an experiment split.