Skip to content

Gift Transaction Feeds

General Information

VertiyData’s Gifts database consists of “G” code transactions disclosed on Form 4 and labeled as a Bona fide gift. The Gifts database provides valuable insight into insider behavior surrounding gift codes, allowing you to discover changes and patterns.

We began processing gift transactions in real-time in March 2023. Our historical data goes back to 1993. Point-in-Time files are available starting March 27, 2023. The point-in-time format allows you to build daily snapshots by ingesting daily delta (inserts/edits) files rather than reprocessing the entire history every day.

Notes on the point-in-time format:

  • Updates to company-related fields (ticker, cusip, company_name, etc.) do not trigger updates in the feed, only updates to event specific fields trigger an update.
  • Company-related fields are as of the asof field, not the original insert, meaning values such as ticker, cusip, etc. may change when comparing an initial insert to a later update for the same txnid. (e.g. a transaction with ticker "FOO" at insert will show as "BAR" on subsequent updates if the company's ticker changed between the two asof dates. The original insert will always show "FOO", however.)
  • Not all fields are available with point-in-time accuracy. Please see the Data Dictionary for more information.

Data Dictionary

COLUMN Description
ticker Ticker of the company. Tickers in [square brackets] indicate de-listed or inactive companies.
cusip CUSIP identifier of the company.
class_status Denotes the status of the company at the time of the lastupdate. Useful to exclude posthumous edits to inactive companies from your modeling / testing.
company_name Name of the company.
sector Sector of the company
mcap [Not Point In Time Data] Market Cap of the company as of the filing date.
insider_name Name of the insider.
rptcik SEC assigned unique identifier of the Insider.
position_type Position the insider held at the company, at the time of the transaction. Can be the following values “CEO”, “CFO”, “Officer”, Director”, “10% Owner”, or “Other”.
position_title Position title of the insider in the source filing. If the insider is CEO or CFO, this will show “CEO” or “CFO,” respectively.
age Age of the insider (calculated by using confirmed birthdate and the grants date).
gender Gender of the insider.
disclosure_date The date that the filing was filed at the SEC.
filed_time The exact date and time in YYYY-MM-DD hh:mm:ss the filing was filed at the SEC.
received_time The exact time in YYYY-MM-DD hh:mm:ss.ssssss that we received the filing, usually within seconds after the File_time above. The date and time listed is generated by our internal servers. This field is NULL for all transactions prior to 2008. NOTE: This field may read earlier than the File_Time field as our server time and the SEC's server time are not synced.
txn_date The date of the transaction. If an insider has multiple transactions which have been grouped together in a single transaction, we will show the latest date as the transaction date.
code Transaction Type: G= Gifts
gift_type Gifts can be classified as three different types:
A = Acquisition
N = Neutral
D = Disposition
shares Amount of shares transacted.
value Dollar value of the transaction.
avg_pps The average price per share of the transaction.
shares_owned The number of shares owned by the insider after the transaction. IMPORTANT - this value is often inaccurate and companies disclose this value inconsistently.
pct_chg The percentage change in shares owned. A value of 0 means it is a New position. IMPORTANT - this value is often inaccurate as it is reliant on the shares owned provided in the filing. Companies disclose the shares owned value inconsistently.
has_10b5 Returns TRUE if the transaction was made pursuant to Rule 10b5-1. Prior to April 1, 2023, this information was disclosed voluntarily via footnotes.
txnid Verity's unique numerical id given to each transaction, this should be considered your Primary Key.
last_update The date of the last update for this entry.
form4a_update Returns TRUE if the transaction had been edited or created due to a Form 4/A. A Form 4/A is filed by a company to fix an error or omission in a previously filed Form 4.
split_edit Returns TRUE if the edit was due to a split.
edit_action "U" for update, "D" for delete and "I" for new insert.
asof The date the record appeared in the feed