# NDJSON Data Structure for ADX

<table data-full-width="true"><thead><tr><th width="368.5">Field</th><th>Description</th></tr></thead><tbody><tr><td><code>id</code></td><td>The unique identifier of the event.</td></tr><tr><td><code>parent_event</code></td><td>Used to indicate if this event is part of a larger event. These types of events are called umbrella events in the system. For example, a large multi-day parent umbrella event may have individual child events for sessions on different days. This field only shows if a child event has a parent id. It does not indicate if a parent event has child events. For details see our <a href="../../../getting-started/guides/date-and-time-guides/working-with-multi-day-and-umbrella-events">Umbrella Events docs</a>.</td></tr><tr><td><code>title</code></td><td>The title of the event.</td></tr><tr><td><code>description</code></td><td>The description of the event.</td></tr><tr><td><code>category</code></td><td>The category of the event.</td></tr><tr><td><code>labels</code></td><td>The labels associated with the event. The <code>labels</code> field is representing PredictHQ's legacy labels, and it's suggested to use the <code>phq_labels</code> field instead where possible.<br><br>See also our <a href="../../../getting-started/predicthq-data/labels">Labels</a> docs.</td></tr><tr><td><code>rank</code></td><td><p>A log scale numerical value between 0 and 100 with a five-level hierarchical impact schema. It is designed to represent the potential impact of an event independent of its geographical location.</p><p>See also our <a href="../../../getting-started/predicthq-data/ranks/phq-rank">PHQ Rank docs</a>.</p></td></tr><tr><td><code>local_rank</code></td><td><p>Similar to PHQ Rank, this is a log scale numerical value between 0 and 100 with a five-level hierarchical impact schema. It is designed to represent the potential impact of an event on its local geographical area.</p><p>Local Rank is calculated for all events.</p><p>See also our <a href="../../../getting-started/predicthq-data/ranks/local-rank">Local Rank docs</a>.</p></td></tr><tr><td><code>aviation_rank</code></td><td><p>A log scale numerical value between 0 and 100 with a five-level hierarchical impact schema. Aviation Rank indicates how much an event will impact flight bookings by considering both domestic and international travel.</p><p></p><p>Aviation Rank has been deprecated.</p></td></tr><tr><td><code>phq_attendance</code></td><td><p>A numerical value that reflects the predicted attendance for supported attendance-based categories. Supported categories include concerts, performing arts, sports, expos, conferences, community, and festivals. Some academic and school holiday events may also include a phq_attendance value to indicate student numbers.</p><p>For multi-day events, phq_attendance represents total attendance across the entire duration, except for certain categories like conferences, where it reflects daily attendance.</p><p>For details see our <a href="../../../getting-started/predicthq-data/predicted-attendance">Predicted Attendance guide</a>.</p></td></tr><tr><td><code>entities</code></td><td>An array of entities linked to the event. This is a complex data type, please see <a href="https://app.gitbook.com/s/kEFs8urDbSJqBmXUI3Lv/events">Events API</a> for details.</td></tr><tr><td><code>duration</code></td><td>The difference in seconds between the event <code>start</code> and the event <code>end</code>.</td></tr><tr><td><code>start</code></td><td><p>The date and time the event starts, recorded in UTC. If the timezone is not considered relevant (e.g., Independence Day), the time is stored in UTC to represent the same relative time across all timezones, and the <code>timezone</code> field will be null.</p><p>Additionally, if an event has a start time of midnight in its local timezone, this may indicate that the actual time is unknown. You may wish to omit the time when displaying such events</p></td></tr><tr><td><code>end</code></td><td>The date and time the event ends, recorded in UTC. If the timezone is not considered relevant (e.g., Independence Day), the time is stored in UTC to represent the same relative time across all timezones, and the <code>timezone</code> field will be null.</td></tr><tr><td><code>updated</code></td><td>The date and time the event was last updated in UTC.</td></tr><tr><td><code>first_seen</code></td><td>The date and time the event was first seen by PredictHQ in UTC. Also called <code>first_seen</code> in the Events API.</td></tr><tr><td><code>timezone</code></td><td>The time zone of the event in TZ Database format. This is helpful so you know which time zone to convert the dates to (if needed). If the time zone is <code>null</code>, the start and end date should be regarded as time zone agnostic and already being in local time.</td></tr><tr><td><code>geo</code></td><td>The geographic details (location) of the event in GeoJSON format.<br><br>See <a href="../../../getting-started/guides/geolocation-guides">geolocation guides</a> for more information on handling <code>geo</code> data.</td></tr><tr><td><code>impact_patterns</code></td><td>Also known as “Predicted Impact Patterns”. This field shows impact for leading days (days before the event), lagging days (days after an event) and the days the event occurs. It contains details such as the industry vertical the impact pattern applies to, the type of impact shown in the impact pattern, and an array of objects for each day showing the date in the local timezone of the event and the value of the impact_type for that given day.<br><br>See also our <a href="../../../getting-started/predicthq-data/impact-patterns">Impact Patterns</a> docs.</td></tr><tr><td><code>scope</code></td><td><p>The geographical scope the events apply to. Possible values are:</p><ul><li><code>locality</code></li><li><code>localadmin</code></li><li><code>county</code></li><li><code>region</code></li><li><code>country</code></li></ul></td></tr><tr><td><code>placekey</code></td><td>The Placekey identifier for the physical address where the event takes place. See <a href="../../../getting-started/guides/geolocation-guides/searching-by-location/find-events-by-placekey">Placekey</a>. This field will be <code>null</code> if the "What" part or the "Where" part of the Placekey for the event address couldn't be retrieved.</td></tr><tr><td><code>country</code></td><td>The country code in ISO 3166-1 alpha 2 format. This value is typically present, but in some cases such as events occurring outside any country (e.g. an earthquake in the middle of the ocean), it may be empty.</td></tr><tr><td><code>place_hierarchies</code></td><td><p>An array of place hierarchies for the event. Each hierarchy is an array of place ids. The final place in a hierarchy is a specific place the event applies to. Each place is a sub-place of the place immediately preceding it in the hierarchy. An empty array is possible and valid.</p><p>See also the <a href="../../../getting-started/guides/geolocation-guides/understanding-place-hierarchies">Place Hierarchies guide</a>.</p></td></tr><tr><td><code>state</code></td><td><p>The publication state of the event.</p><p>Possible values:</p><ul><li><code>active</code> - The event is an active event.</li><li><code>postponed</code> - The event is a postponed event, and is expected to occur at a later date.</li><li><code>cancelled</code> - The event is a cancelled event and is not expected to occur at a later date.</li><li><code>predicted</code> - The event is a predicted event. For details, see our <a href="../../../getting-started/predicthq-data/predicted-events">Predicted Events page</a>.</li></ul></td></tr><tr><td><code>brand_safe</code></td><td>Whether or not this event is considered brand-safe. Examples of brand-unsafe events include content that promotes hate, violence, or discrimination, coarse language, content that is sexually suggestive or explicit, etc.</td></tr><tr><td><code>cancelled</code></td><td>The date and time the event was marked as cancelled, presented in the UTC timezone. This field will be null if <code>state</code> is not set to "cancelled" or if the cancellation date is unavailable.</td></tr><tr><td><code>postponed</code></td><td>The date and time the event was marked as postponed, presented in the UTC timezone. This field will be null if <code>state</code> is not set to "postponed" or if the postponement date is unavailable. Note that this field does not represent the new date and time of the postponed event.</td></tr><tr><td><code>predicted_event_spend</code></td><td>The total predicted event spend (USD) across all supported industries: accommodation, hospitality and transportation. This field will be <code>null</code> if the predicted event spend is not supported for this event.<br><br>See also our <a href="../../../getting-started/predicthq-data/predicted-event-spend">Predicted Event Spend</a> docs.</td></tr><tr><td><code>predicted_event_spend_industries</code></td><td>A breakdown of predicted event spend (USD) into the three supported industries: accommodation, hospitality, and transportation. This field will be <code>null</code> if the predicted event spend is not supported for this event.<br><br>See also our <a href="../../../getting-started/predicthq-data/predicted-event-spend">Predicted Event Spend</a> docs.</td></tr><tr><td><code>phq_labels</code></td><td>The PHQ Labels associated with the event. This field will be <code>null</code> if there are no PHQ Labels for this event.<br><br>See also our <a href="../../../getting-started/predicthq-data/labels">Labels</a> docs.</td></tr><tr><td><code>predicted_end</code></td><td>The date and time PredictHQ predicts the event will end, recorded in UTC. If the <code>timezone</code> field is null, the time represents the same relative time across all timezones. This value is present where an actual <code>timezone</code> is unknown.</td></tr><tr><td><code>alternate_ids</code></td><td>All alternate IDs for the event. Any event IDs that may have been used for this event in the past will be included here. It does not include the current event ID.</td></tr><tr><td><code>start_local</code></td><td>The date and time when the event begins, expressed in the event's local time zone.</td></tr><tr><td><code>end_local</code></td><td>The date and time when the event ends, expressed in the event's local time zone.</td></tr><tr><td><code>predicted_end_local</code></td><td>The date and time when the event is predicted to end, expressed in the event's local time zone.</td></tr><tr><td><code>region</code></td><td>The region in which the event will be occurring. This field can be <code>null</code> if the event covers more than a single region.</td></tr><tr><td><code>locality</code></td><td>The locality in which the event will be occurring. A locality is most commonly referred to as a city or town. This field can be <code>null</code> if the event covers more than a single locality.</td></tr><tr><td><code>postcode</code></td><td>The postal code or ZIP code in which the event will be occurring. This field can be <code>null</code> if the event covers more than a single post code.</td></tr><tr><td><code>formatted_address</code></td><td>A full formatted address which can include street addresses, locality, postcode, region, and country.</td></tr><tr><td><code>change_action</code></td><td><p>Indicates if the record has been updated, deleted or inserted. Use when processing the data file to keep your database updated.</p><p>Possible values:</p><ul><li><code>insert</code> - new record, not previously seen.</li><li><code>update</code> - existing record, updated values.</li><li><code>delete</code> - deleted record, remove from your dataset.</li></ul></td></tr></tbody></table>
