US Equities Daily Cumulative Adjustment Factors

How to use it

Rows are effective-dated. Answer point-in-time questions with the row in force on the as-of date, never the latest row. SecId and ASID are both durable AlgoSeek security keys but different values (the ASID lookup links them); tickers are reused across companies, so resolve a ticker to a key with a trade date.

Typical use

Point-in-time security identity, corporate-action adjustment, and universe construction for US equities.

Limitations

Vendor-curated reference data: rows can be restated when AlgoSeek learns of a late or corrected event, so land each delivery as a snapshot rather than overwriting history. Apply (guide): price on date D x CumulativeFactorPrice(D); volume on date D / CumulativeFactorVolume(D). Join on SecId + TradeDate; no gap handling needed because every trading day has a row. Derived and verified on guide Table 5 and the sample: CumulativeFactor(D) = product of the AdjustmentFactors of all events with EffectiveDate later than D (strictly). On an event date the factor already excludes that event (AAPL 20140609: price 0.032233144343822 -> 0.225632010406754, ratio 0.142857; sample 20220805: 0.992723673605374 -> 0.994102623025167, ratio 0.99861287 = that day's AdjustmentFactor). Volume factor is a divisor and changes only on volume-affecting events (BonusSame, CapReduct, Cons, ScriptDiv, SecSwap, Reclass, Subdiv); sample value 1 throughout for AAPL in 2022. AdjustmentFactor, AdjustmentReason and EventType are populated only on event dates (blank elsewhere); with several events on one date AdjustmentFactor is the cumulative product for that date and reason/type strings are joined with 'and'. This gives one row per SecId+TradeDate.

Coverage

All US exchange-listed equities, backward-adjustment factors for any date from 2007 to present. Sample is AAPL only (100 consecutive trading days 20220802-20221221).

Usage constraints

• Licensed vendor data: never export raw rows to a tenant-local destination or include them verbatim in a public artifact; serve only through entitlement-checked platform reads.
• Do not treat the vendor's `Ticker` as a stable identity across time; join on an AlgoSeek security key (SecId or ASID, which are distinct) or the platform symbol mapping.

Known issues (6)

• Primary key is inferred; AlgoSeek's guide does not name one.
• Documentation discrepancyColumn order: guide Tables 1 and 2 list SecId, Ticker, TradeDate, AdjustmentFactor, ...; the sample header (and JSON preview) put TradeDate first: TradeDate, SecId, Ticker, ...
• Documentation discrepancyGuide Table 5 (AAPL, text extraction) shows a row dated '20140206' between 20140605 and 20140606 and a '0610' fragment for the 20140610 row - apparent typos in the guide table (probably 20140604 and 20140610); the factor values in those rows are consistent with their neighbours.
• Documentation discrepancyGuide text names the data 'Equity Cumulative Backward Adjustment Factors CSV file' and calls the buckets us-equity-cumulative-backward-adjustment-secid-year in one place and -secid-yyyy in another.
• Documentation discrepancyGuide Table 5 values (CumulativeFactorVolume 0.0357142857142858 before 20140609, 0.25 after) include the later 20200831 4-for-1 split, i.e. a more recent snapshot than the 2014 date range suggests; confirms the series is restated retroactively.
• Documentation discrepancyGuide's Table 3 reasons list is garbled in plain text extraction; table-aware extraction gives the same 18 reasons and Yes/No price/volume flags as the other adjustment guides.