Earnings Calendar Change Monitor

Compare two earnings calendars and return company-level additions, removals, date shifts, market-session changes, confirmation changes, estimate updates, and webcast-link updates.

Supported Sources

Each comparison can use:

• CSV, TSV, semicolon-delimited, or pipe-delimited calendar text
• JSON arrays or objects containing events, earnings, results, or data
• Structured previousEvents and currentEvents arrays
• Simple text statements containing a ticker and ISO date
• A public current-calendar URL when fetchUrls is enabled

The actor normalizes common aliases for ticker, company, date, session, timezone, confirmation status, fiscal period, EPS estimate, revenue estimate, and webcast URL. Events are keyed by ticker and fiscal period, then deduplicated before comparison.

Example Input

{
  "targets": [
    {
      "sourceId": "technology-earnings",
      "sourceUrl": "https://example.com/calendars/earnings.csv",
      "previousSnapshot": "Ticker,Company,Earnings Date,Session,Status,Fiscal Quarter\nACME,Acme Cloud,2026-07-20,AMC,estimated,Q2 2026\nBRIO,Brio Retail,2026-07-22,BMO,estimated,Q2 2026",
      "currentSnapshot": "Ticker,Company,Earnings Date,Session,Status,Fiscal Quarter\nACME,Acme Cloud,2026-07-23,AMC,confirmed,Q2 2026\nBRIO,Brio Retail,2026-07-22,BMO,confirmed,Q2 2026\nNOVA,Nova AI,2026-07-25,AMC,estimated,Q2 2026"
    }
  ],
  "maxTargets": 1,
  "maxEventsPerTarget": 500,
  "includeUnchanged": false,
  "includeReport": true
}

Output

Each dataset row contains:

• Source and billing fields: rowId, sourceId, sourceUrl, sourceType, checkedAt, pricingEventName
• Event identity: eventKey, ticker, companyName, fiscalQuarter
• Schedule comparison: oldEarningsDate, newEarningsDate, dateShiftDays, old/new market session, and old/new timezone
• Detail comparison: old/new confirmation status, EPS estimate, revenue estimate, and webcast URL
• Decision fields: changeType, status, severity, score, summary, and recommendation

changeType is added, removed, date-shifted, time-shifted, status-changed, details-changed, or unchanged.

Failed fetches and calendars with no valid events produce an explicit diagnostic row through diagnosticCode and sourceError.

Example Output

{
  "ticker": "ACME",
  "companyName": "Acme Cloud",
  "fiscalQuarter": "Q2 2026",
  "oldEarningsDate": "2026-07-20",
  "newEarningsDate": "2026-07-23",
  "dateShiftDays": 3,
  "oldTimeOfDay": "after-market-close",
  "newTimeOfDay": "after-market-close",
  "oldStatus": "estimated",
  "newStatus": "confirmed",
  "changeType": "date-shifted"
}

PPE Pricing

Event prices include Apify platform usage for the configured fixed-inclusive model.

• actor-start: $0.02000 once per paid run
• target-checked: $0.00650 per calendar target
• snapshot-compared: $0.00650 per comparison
• change-detected: $0.01300 per emitted change
• digest-generated: $0.05000 when digest artifacts are written
• executive-report-generated: $0.10000 when the Markdown report is written

The actor stops before additional output when the charge limit cannot cover the next paid event.

Limits

• Up to 50 calendar targets and 5,000 events per side per target.
• Plain-text parsing intentionally supports only clear ticker plus ISO-date statements. Use CSV, JSON, or structured records for richer sources.
• A fetched current calendar still needs a supplied previous calendar for comparison.
• Calendar data can change quickly. Confirm material changes against current issuer announcements.