# Changelog of B2B Buying Signals: Hiring + Tech Stack Intent for Clay (`mambalabs/b2b-buying-signals-hiring-tech-stack-intent-for-clay`) Actor

- **URL**: https://apify.com/mambalabs/b2b-buying-signals-hiring-tech-stack-intent-for-clay/changelog.md
- **Full Actor documentation**: https://apify.com/mambalabs/b2b-buying-signals-hiring-tech-stack-intent-for-clay.md

## Changelog

All notable changes to this actor are documented here.

### \[0.2.0] - 2026-04-15

#### Breaking Changes

- `uses_linkedin_sales_nav` removed from output schema. If you have a Clay column filtering on this field, the filter will return empty after this update. This is an inherited removal from Actor 2 v0.2.0 - the field no longer exists in the upstream source. Remove any Clay filter conditions referencing this field.

#### Added

- `composite_score` integer field (0-100): numeric signal score derived from hiring and tech stack signals combined. Replaces string-only composite\_signal for Clay filter conditions that need precise threshold cutoffs. composite\_signal string (high / medium / low) is still included and now derived from the numeric score.
- `recommended_action` derived output field: "priority outreach" / "nurture" / "deprioritize" - derived from composite\_score. Removes one manual interpretation step in Clay workflows.
- `run_time_ms` output field: wall-clock milliseconds from API call start to dataset push. Documents speed advantage over multi-actor pipeline competitors.
- `explain_mode` boolean input (default: false): when true, gtm\_signal\_summary switches from a 1-2 sentence summary to a 3-5 sentence agent-ready briefing with full signal breakdown, composite score, recommended action, and a personalization hook. Suitable for passing directly to Claude, GPT-4, or any MCP-compatible agent as lead context.
- `uses_marketo` boolean field: inherited from Actor 2 v0.2.0. Marketo is now a first-class boolean in the merged output and contributes to downstream scoring.

#### Changed

- `composite_signal` derivation now uses the numeric composite\_score as its source (>= 60 = high, >= 30 = medium, < 30 = low). String values are unchanged. Clay filters on composite\_signal strings do not need updating.
- `gtm_signal_summary` now supports two modes: default (1-2 sentence) and explain\_mode (3-5 sentence agent briefing).

#### Removed

- `uses_linkedin_sales_nav` removed from merged output schema. Inherited removal from Actor 2 v0.2.0. Field produced false negatives in the upstream scraper and has been dropped entirely.

### \[0.1.0] - 2026-04-07

#### Added

- Initial release to Apify Store.
- Orchestrates Actor 1 (GTM Hiring Signal Scraper) and Actor 2 (GTM Tech Stack Signal Scraper) in parallel via Apify API.
- Merged flat output row combining all Actor 1 and Actor 2 fields.
- composite\_signal string: high / medium / low.
- gtm\_signal\_summary: plain-English 1-2 sentence summary of combined signals.
- actor1\_error and actor2\_error flags: partial row returned if one actor fails.
- include\_summary boolean input (default true).
- run\_date ISO timestamp.
- PPE monetization at $0.12/result.