Sourcing disclosure
Where our traffic comes from
Marketplace partners should evaluate suppliers by source transparency—not by inflated “global panel” slogans. This page explains how Inso / Yingsheng describes supply for diligence.
Definitions
How we classify supply
We operate two primary supply lanes today, plus an optional river lane when a buyer or exchange explicitly requests it. Every live allocation states which lanes are in use.
- Owned community — Inso Insights recruitment brand: interest registration today, with profiled / recontactable membership expanding as verification is enabled. Never presented as another platform’s panel.
- Channel routes — Publisher / affiliate / media partners under contract. Traffic is disclosed as channel-sourced, quality-gated, and never marketed as another marketplace’s panel.
- River / offerwall (optional) — Used only when approved for a specific campaign. Off by default.
| Source type | Description | Geographies | Notes |
|---|---|---|---|
| Owned community | Inso Insights (join.insosample.com): interest registration and community growth; full profiling / double opt-in as member accounts are enabled. | Overseas-led (APAC core; selected EU / Americas) | Growing recontactable base; terms & privacy on join site |
| Channel / publisher routes | Contracted publisher and affiliate partners used with the community to improve coverage and incidence. | Confirmed per integration / campaign | Quality-gated before traffic is sent |
| River / offerwall (optional) | Optional intercept-style traffic when a buyer or exchange requests it for a defined study. | Confirmed per campaign | Disabled unless approved in writing |
Blend
How community and channels work together
Most projects use a blend of owned community and channel routes. Scalable volume is typically channel-supported; community is the branded recruitment lane. Exact share varies by country, incidence, device, and field window—and is confirmed per allocation (not a fixed public “70% proprietary” slogan).
For trackers or studies that need source stability, we can lock lane proportions for the life of the wave set and report lane labels on participant records when the marketplace workflow allows.
We do not present third-party marketplace panels as Inso / 螢盛 assets. Marketplaces remain independent; we participate as a disclosed sample supplier.
Capacity
Indicative combined monthly reach
Across owned community routes and disclosed channels, combined indicative monthly inviteable supply is about 2.0–2.6 million (midpoint ~2,300,000). This is an operating planning band for diligence—not a live CRM counter, not a certified panel census, and not a promise of completes in every market every month.
- How we count — Unique users who can be invited or routed in a typical month across disclosed supply lanes.
- What this is not — A guarantee of N completes/month in every market, or natural incidence for every target.
- How feasibility is set — Per project: target, LOI, IR, quotas, devices, languages, exclusions, source mix, and quality rules.
- Owned vs channel detail — Confirmed in writing / vendor pack for each allocation; public pages show the combined band plus country mix.
Coverage
Where we field today
Primary strength is overseas markets—especially Southeast Asia, India, Japan/Korea, with selected Europe and Americas. Mainland China is a smaller selective share. We confirm country list, languages, and sample mix before field start.
- Overseas APAC (core) — Southeast Asia, India, Japan, Korea, Australia, Hong Kong, Taiwan, among others.
- Europe — Selected markets via community growth and channel partners when allocated.
- Americas — Selected markets via community growth and channel partners when allocated.
- Mainland China & MEA — Selective share; opened when project demand and partner routes allow.
Operations
Routing and reconciliation
Traffic is sent through our fieldwork stack with unique session identifiers and status redirects (complete, terminate, overquota, and quality outcomes). Reconciliation follows the marketplace or buyer process agreed in onboarding. Technical detail is shared under NDA during integration.
Standard disclosure
Language we use with platforms
We supply online sample to research marketplaces and buyers. Traffic may include owned community members and/or disclosed channel routes, as stated per engagement. We do not represent marketplace panels as our own. Feasibility, geography, and source mix are confirmed per integration and campaign.