How do I retrieve WeChat article reads, likes and recommendations separately from its text?
Request a WeChat article URL with standard statistics (wechat_mp.v2.fetch_article_stats) to get the article’s currently reported reads, likes, recommendations and other engagement counts. Make one request per article. Standard statistics do not return the article text, and you do not need the text to get the counts; request the text separately with wechat_mp.v2.fetch_article_detail_h5 only when you need it.
Pass a short article link or the full long link that contains __biz as url. Keep raw:true (the default) to retain the visibility flags and the retrieval status. Set raw:false for simplified counts only.
Fetch one article’s statistics
Use each count with its status
Check for status:succeeded, then read data and keep the request_id and the observation time. In a standard statistics response, read each count field together with its flag:
Retain retrieval flags such as get_data_succ when the response includes them. Keep display text such as “100k+” as a threshold, and keep the raw number when the response returns 100001. Record missing, hidden, null and failed values as four separate states. Record zero only when the response reports an available numeric zero.
For H5 comment counts, request wechat_mp.v2.fetch_article_stats_h5 to get comment_count and elected_comment_count. Pass comment_id if you have the article’s comment_id, and use raw:true to retain comment_raw. wechat_mp.v2.fetch_article_stats_h5 does not supply reads: the H5 response lists metrics it cannot return in unavailable, so request reads from standard statistics.
Compare articles from the same campaign
Choose the articles and the observation time first:
- For a day-seven comparison, save each article’s counts on the day the article is seven days old.
- To compare three articles published on different dates with one lookup made today, label the results “Totals observed today” and list each article’s publication date and promotion conditions.
- For unique readers or conversion, use an account report you have access to.
For each observation, keep the article URL, the statistics action, the raw value, the status, the collection time and the request ID. To add titles or text, join the saved article sources by verified article identity.
For example, you check one article on Monday and on Wednesday. Confirm that both rows refer to the same article URL and the same statistics action, and keep each row’s observation time and retrieval status. If the Wednesday row has no read count, keep Monday’s value and leave the change blank.
Export a small article review sheet without inventing values
For example, review five known campaign article URLs at a stated time and keep the exact source of each value. One standard statistics request per article is five calls at current pricing. Article text and comments are separate requests, added only where needed.
- Run the curl above with
--max-time 30for each article and record the actual HTTP status. A transport timeout does not prove the call was free, so do not retry a timed-out call automatically. - Record each actual request in stats-pages.json in the following format. The timestamp and URL below are placeholders, not a recorded response.
- Save the Python script below as wechat_metrics.py and run
python3 wechat_metrics.py stats-pages.json metric-review. wechat_metrics.py runs offline and makes no paid calls. The new metric-review directory contains metric rows, the original responses and their hashes.
Read the exported rows as follows:
H5 rows never fill a read count. The sheet keeps the raw visibility and retrieval flags and does not rank articles; review the flags and each article’s age at collection before comparing.
wechat_metrics.py stops without writing when a response is an HTTP 200 business failure, when a response is malformed or when the output directory already exists. Keep the original manifest and responses to investigate the stop. Keep the raw files private and share a reviewed or redacted copy. A before/after comparison needs the same article, the same action, the same metric scope and comparable collection times. Do not subtract H5 nulls from standard values, and do not infer sales from reads.
wechat_metrics.py accepts a short link with a nonempty token, or a long link with exactly one nonempty __biz, mid and idx each. The script rejects URLs that contain credentials and keeps the original URL unchanged.
What should a ten-article review contain?
A ten-article review contains the comparable observations, the articles still under review and the unresolved attempts:
- Plan ten standard statistics requests at the current price.
- After export, select the
metric=read_numrows inmetrics.csvand check each row against the saved response througharticle_urlandsource_index. - Record each interrupted request with no response body as an unresolved attempt.
- To add titles and article text, use the saved-source join. The saved-source join handles up to five pairs at a time, so split the ten articles into two batches and put each article in exactly one batch.

