Zalo OA Business Intelligence & Change Monitor

Extract public Zalo Official Account landing-page data and monitor what changes between runs. The Actor is designed for recurring brand/OA monitoring rather than private Zalo data access.

It works with logged-out public zalo.me/{oaId} and custom OA-slug pages. Current public pages may expose only metadata such as name, description, canonical identity hints, and QR URL. Richer fields such as verification, category, OA type, follower count, tier, avatar, cover, address, and working hours are returned only when the public page actually exposes them.

What you get

Each public OA snapshot can include:

• OA ID and/or custom slug
• public name and description
• canonical URL
• QR image URL
• avatar / cover when separately exposed
• verification, category, OA type, tier, follower count, address, and working hours when available
• dataLevel: META or STRUCTURED
• availablePublicFields and missingPublicFields
• deterministic profileHash
• parser diagnostics that explain which public signals were actually found

The Actor deliberately treats HTTP 200 as insufficient evidence of success. Login walls, block pages, not-found pages, rate limits, and parse failures are classified instead of silently emitted as valid OA profiles.

Why use this instead of a raw Zalo OA scraper?

The primary product is recurring monitoring:

• monitor public OA name and description changes
• detect verification/category/tier/follower changes when the page exposes those fields
• track address and business-hour changes when available
• detect availability transitions such as PUBLIC -> LOGIN_REQUIRED / NOT_FOUND
• detect RECOVERED when an OA becomes publicly accessible again
• maintain stable public OA directories with hashes and data-quality signals
• feed records into CRM, lead-enrichment, API, MCP, or scheduled automation workflows

Input

Use any combination of:

• startUrls: public https://zalo.me/... OA pages
• oaIds: numeric OA IDs
• slugs: public OA slugs
• oaText: bulk pasted URLs / IDs / slugs

The Actor normalizes and deduplicates targets before applying maxItems.

Minimal example

{
  "startUrls": [{"url": "https://zalo.me/officialaccount"}],
  "maxItems": 10,
  "monitorMode": false,
  "proxyConfiguration": {"useApifyProxy": false}
}

Monitoring example

{
  "oaIds": ["4462152339089565647"],
  "monitorMode": true,
  "emitChangesOnly": true,
  "stateNamespace": "my-brand-watchlist",
  "proxyConfiguration": {"useApifyProxy": false}
}

Output statuses

Snapshot rows use explicit statuses:

• PUBLIC
• LOGIN_REQUIRED
• NOT_FOUND
• ACCESS_DENIED
• RATE_LIMITED
• PARSE_ERROR
• ERROR
• INVALID

Only successfully parsed public OA pages trigger the custom PPE event. Invalid, blocked, login-required, not-found, rate-limited, and failed lookups are not charged by that custom event.

Data quality

dataLevel makes the source quality explicit:

• META — the public page exposed metadata only, typically name/description/QR and identity hints.
• STRUCTURED — a structured OA payload was found and richer fields may be available.

profileCompletenessScore is a 0-100 heuristic for useful business fields. It is not an official Zalo score. availablePublicFields and missingPublicFields make the result auditable.

The Actor does not infer or fabricate missing verification, category, follower, address, or working-hour values.

Monitoring behavior

When monitorMode=true, stable state is stored in a named Key-Value Store. The change engine can emit:

• NEW_OA
• PROFILE_CHANGED
• VERIFICATION_CHANGED
• ADDRESS_CHANGED
• HOURS_CHANGED
• CATEGORY_CHANGED
• TIER_CHANGED
• FOLLOWER_COUNT_CHANGED
• LOGIN_REQUIRED
• NOT_FOUND
• RECOVERED
• UNCHANGED

changeTypes can contain multiple simultaneous changes while changeType remains the primary event. fieldChanges contains previous/current values.

Transient ACCESS_DENIED, RATE_LIMITED, PARSE_ERROR, and network failures do not overwrite the previous healthy baseline.

QR image URLs are excluded from the deterministic profile-change fingerprint because Zalo may rotate QR image tokens without changing the OA business profile.

First run vs later runs

• First public run -> NEW_OA unless baselineOnly=true
• Same monitored profile later -> UNCHANGED
• Field changes -> field-level change event(s)
• Public page becomes login-required/not-found -> availability change
• It becomes public again -> RECOVERED
• emitChangesOnly=true suppresses snapshots and UNCHANGED, while operational errors remain visible

Public page vs official Zalo OA API

This Actor intentionally works without a Zalo login or OA token. Zalo's official OA management API can expose richer OA-management fields but requires an authorized OA access token and the relevant permissions. This Actor does not claim those private/account-scoped API fields when they are absent from the logged-out public page.

Access and proxy policy

The Actor uses an HTTP client with Chrome-style TLS impersonation. Direct access is the default. A proxy can be configured through Apify when legitimately needed for geography or network reliability.

The Actor is intentionally not built around CAPTCHA solving, private sessions, QR logins, or private account data. If public access becomes unavailable, it surfaces the access status rather than fabricating data.

Pricing model

The source defines one custom PPE event:

oa-profile-checked — one successfully fetched and parsed public OA page.

Current source price: $0.00249 per successful public OA check before any synthetic Actor-start event configured at publication. Failed/blocked/non-public lookups are not charged by this custom event.

Suggested Store task examples

1. Monitor Zalo OA profile changes
2. Build a public Zalo OA directory
3. Track Zalo OA availability and recovery
4. Use Zalo OA change events from an API or AI workflow

Scope and privacy

Public Official Account landing pages only. The Actor does not collect or attempt to access:

• private chats or message history
• contacts
• group members
• private personal profiles
• logged-in OA Manager data
• private follower identities
• QR/session authentication

Zalo and related marks belong to their respective owners. This is an independent tool and is not affiliated with or endorsed by Zalo/VNG. Users are responsible for lawful use and applicable terms.