# Changelog of Naver Blog Brand Monitor — sponsored vs organic posts · $4/1k (`leoworks/naver-blog-brand-monitor`) Actor

- **URL**: https://apify.com/leoworks/naver-blog-brand-monitor/changelog.md
- **Full Actor documentation**: https://apify.com/leoworks/naver-blog-brand-monitor.md

## Changelog

### 0.1 (2026-10-06 listing)

- Store listing refresh: title with price, AGENTS category, README restructured (output sample from real runs, input example, pricing per 1,000, Works with, MCP setup for Claude / Cursor / Claude Code, review request). A review-request line at the end of the run log. No functional or price change.

### 0.1 (2026-10-04 engagement)

- `likeCount` (all reactions, as shown under the post), `reactions` breakdown and `commentCount` per post. Checked against the blog page. No extra charge; existing fields unchanged.

### 0.1 (2026-10-04 summary)

- Input form starts at 8 posts per query for a quick, low-cost first run (raise up to 1,000). API default unchanged (50).
- Summary by keyword and brand: each run saves a REPORT record (sponsored / self-paid / unclear split, affiliate share, sentiment of all and of self-paid posts, posts per month, 3 latest negative non-sponsored posts). No extra charge; dataset rows unchanged.

### 0.1 (2026-10-03 README)

- README: FAQ explains that judgments come from Jev (TypeSafe's decision model, pinned version) and which text is sent to it.

### 0.1 (2026-10-02 update)

- Sponsored detection: disclosure phrases that the writer denies ("협찬을 받지 않고", "업체로부터 어떠한 지원도 받지 않고", "광고글 아닙니다") no longer count as sponsorship evidence; a blog's "협찬문의" contact line is ignored.
- Up to 10 brands per run; post discovery stops at what the run's maximum cost can pay for.

### 0.1

- First version: Naver Blog post discovery by keyword (web search, or your own NAVER API Hub key), post metadata and text, sponsored/self-paid detection with evidence (rules + model), affiliate flag, sentiment and brand mentions; per-run cost cap support.