← All tables

gold_organization_events

Corporate events that change who owns or operates assets: acquisitions, mergers, name changes, scoped asset transfers, and identity corrections. One row per event with the organizations involved and the date it took effect. This drives ownership-over-time attribution: activity before the effective date stays with the original company, after it with the successor.

Access tier: public_aggregate Public. These rows are the public layer: aggregate series and reference records such as companies, formations and rig counts. Where a page publishes them you can read them on the website, and a free account can export the aggregate series behind a view (10 a month).
Primary key: event_id
Region codes: organizations

Columns

Column	Type	Nullable	Description
event_id	string	no	Stable event identifier.
event_type	string	no	`acquisition` = the source organization was taken over by the target; `merger` = the source merged into the target; `name_change` = same entity renamed to the target; `asset_transfer` = a scoped set of assets changed hands (see gold_organization_event_wells for the wells); `entity_correction` = a registry identity fix rather than a real-world event; `subsidiary_acquisition` = the target acquired the source, which continues to operate under its own name. Values: acquisition · merger · name_change · asset_transfer · entity_correction · subsidiary_acquisition.
effective_date	date	yes	Date the change took effect.
announced_date	date	yes	Announcement date, where known.
source_org_id	string	no	The organization the event happened to: the acquired, merging, or renamed party.
target_org_id	string	yes	The counterparty or continuing entity: the acquirer, the merged-into company, or the new name.
description	string	yes	Free-text summary of the event.
source	string	no	How the event record was created: `seed` = curated starting set, `enrichment` = automated research pipeline, `correction` = fix applied after the fact. Values: seed · enrichment · correction.
effective_date_precision	string	yes	How precisely the effective date is known: `day` = exact date from a primary source; `month` or `year` = the date is pinned only to that month or year. The stored date is always the best-evidenced boundary we have: a lower precision widens the uncertainty around that date, it never shifts the date to the start of a month or year. Blank = not yet classified. Values: day · month · year.

How these numbers are built is on methodology; the machine twin of this page is data-dictionary.json.