# Changelog of Website Contact Email Phone Scraper (`black_magic/public-contact-and-conversion-intelligence`) Actor

- **URL**: https://apify.com/black\_magic/public-contact-and-conversion-intelligence/changelog.md
- **Full Actor documentation**: https://apify.com/black\_magic/public-contact-and-conversion-intelligence.md

## Changelog

### 1.0.8 - 2026-07-25

- Define the chargeable unit as a safely processed dataset item, including valid zero-contact results; failed URLs remain uncharged.
- Align runtime and schema defaults at three pages and fully type nested page, social, and email-domain evidence.
- Publish a consumer-facing RapidAPI gateway/authentication contract with schema-valid examples and request-level quota language.

### 1.0.7 - 2026-07-25

- Clarify that returned emails are published public addresses and MX/SPF/DMARC are domain evidence, not mailbox verification.
- Add measured quality/economics boundaries, expanded output schema, readable 1080p/captioned video requirements, and RapidAPI schema parity.
- Package the reviewed root contact engine through `scripts/sync-apify-contact-engine.py` to prevent Actor drift.

### 1.0.6 - 2026-07-18

- Store discoverability: buyer-language SEO, default example `https://knightlogics.com`, maxPages default 3, failed-sites-uncharged trust note, RapidAPI cross-link.

### 1.0.5 - 2026-07-17

- Store README enrichment: live Store URL, knightlogics.com example, real JSON excerpt, SEO keywords, thumbnail/demo asset pointers.

### 1.0.4 - 2026-07-17

- Fix PPE billing: do not call `push_data(..., "apify-default-dataset-item")` manually (SDK rejects synthetic events). Successful results use plain `push_data` so Apify auto-charges the Console primary event; charge-limit checks still use `apify-default-dataset-item`. Failed sites are logged only (not dataset-pushed) so they stay uncharged.

### 1.0.3 - 2026-07-17

- Align pay-per-event charging with Console primary event `apify-default-dataset-item` (one charge per successful website dataset item). Failed sites push an error record and are not charged.
- Rebuild and redeploy so the cloud Actor matches local billing behavior.

### 1.0 - 2026-07-17

- Initial public-contact extraction, form/social/CTA signals, DNS evidence, scoring, evidence hashes, SSRF controls, and pay-per-event charging support.