> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.beatapi.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.beatapi.io/_mcp/server.

# How do I use audience profiles and activity metrics to review Xiaohongshu creator fit?

> Choose profile or summary data for the collaboration brief, preserve definitions and original values, then combine recent work with selection reasons and open checks.

To check whether a Xiaohongshu creator's followers fit your intended audience, call `data:xiaohongshu.pgy.get_blogger_fans_profile` with the creator's `user_id`. For audience size and reported activity, call `data:xiaohongshu.pgy.get_blogger_fans_summary`. For changes over time, fetch [follower history](/faq/xiaohongshu-follower-history) separately.

For a local coffee event, start with the profile's city and interest distribution. If the summary reports an active-follower share, record the share's definition next to the value. To evaluate actual visits or conversions, use the event's signup or conversion records.

## Choose profile, summary or history

| Question                                     | Capability                                      | Use                                                                      |
| -------------------------------------------- | ----------------------------------------------- | ------------------------------------------------------------------------ |
| Audience age, gender, location and interests | `data:xiaohongshu.pgy.get_blogger_fans_profile` | Compare with the audience brief                                          |
| Follower summary and activity                | `data:xiaohongshu.pgy.get_blogger_fans_summary` | Preserve original activity values and definitions alongside content      |
| Recent follower changes                      | `data:xiaohongshu.pgy.get_blogger_fans_history` | Review dates using [matching windows](/faq/xiaohongshu-follower-history) |

Profiles and summaries take a verified `user_id`. Example profile request:

```bash
curl -sS https://api.beatapi.io/v1/social-data/call \
  -H "Authorization: Bearer $BEATAPI_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{"action":"xiaohongshu.pgy.get_blogger_fans_profile","params":{"user_id":"<user_id>"}}' \
  -o creator-audience-profile.json
```

## Read the relevant fields

The complete response keeps two `data` layers. The documented fields are under `data.data`:

| Material | Fields                                                                                   |
| -------- | ---------------------------------------------------------------------------------------- |
| Profile  | `ages`, `gender` (male/female), `provinces`, `cities`, `devices`, `interests`            |
| Summary  | `fansNum`, `fansIncreaseNum`, `fansGrowthRate`, `activeFansRate`, `activeFansBeyondRate` |

Record `activeFansRate` separately from `activeFansBeyondRate`, which compares the creator with peers. The current action description does not fix the scaling, the peer-group definition or a common observation window. Keep the original values and notes before you apply thresholds, and do not mix 0–1 and 0–100 representations.

## Review five candidates

1. **Fix the account roster.** Reuse the five verified IDs from the [candidate workflow](/guides/xiaohongshu-creator-shortlist) and keep each creator's content direction.
2. **Record the brief.** Write down the conditions, such as location, language and recent content format, and mark each condition as required or open.
3. **Retrieve the matching material.** For a geography question, fetch the profile first; for an activity question, fetch the summary first. Save the request, time, response and fields used for each creator.
4. **Review content fit.** For each candidate, keep relevant recent work, fit reasons, missing evidence and next steps. Record unavailable data as an open check, not as a zero score.

Give an assistant that has the BeatAPI tools configured a task like this one:

> Review these five candidates' returned geography and interests for a local coffee event, then inspect recent content. Keep actual fields and sources with fit reasons and open checks. Preserve unclear percentage units instead of automatically labeling followers fake.

For a tutorial campaign, check whether each candidate has published work about a comparable product, then compare reader or engagement signals that share the same definitions. If only one candidate has purchase-related data, mark the other candidates as pending. Record the metric name, period and source in the table.

## Distinguish followers, readers and buyers

The audience profile describes the creator's follower collection, not the readers of the next post or future buyers. The action's original description mentions reading and engagement shares without listing complete exact keys, and purchase-follower fields are unverified. Do not fill invented reading, engagement or purchase values into the review table.

For each candidate, deliver the ID, observation time, raw field values, audience conditions, content evidence and the manual decision. Fetch follower history only when a specific change needs checking, instead of buying all three data sets for every candidate.

Five creators with one action each means five planned requests; two actions each means ten. Estimate the cost with current [pricing](https://beatapi.io/pricing); reviewing saved material needs no new retrieval.

[Candidate and case review](/guides/xiaohongshu-creator-shortlist) · [Follower changes](/faq/xiaohongshu-follower-history)