Tagging Portal
ICON · Identity & Context Nexus

Know who the seller is, know what we know about them, and put it to work

ICON connects one verified seller Identity with governed seller Context (Attributes and Signals), and serves both to downstream teams through one Nexus. Find the data, pick the Fields, build an audience, and track your request, all in one place.

Identity+Context=Nexus

What ICON connects

Identity says who the seller is. Context says what we know. The Nexus makes both reusable for every downstream team.

I · Identity

One seller, one verified identity

Good Contact resolves WeChat UID, MCID and channel identifiers across touchpoints into a single persistent seller profile.

  • WeChat UID ↔ MCID identity resolution
  • 5 outreach paths plus cross-team referral
  • 20+ raw data sources, real-time and daily batch
C · Context

Governed Attributes and Signals

The Library organizes seller context into Attributes (what is true or observed) and Signals (what models and Gen AI infer), each Field in exactly one L3 or L4 node.

  • Attribute: Profile, Performance, Activity
  • Signals: Science Model, Gen AI
  • Fields carry Values, Single or Multi select
N · Nexus

One hub for downstream teams

Pick Fields in Mart, circle an audience in Selector, and request delivery. Downstream teams reuse instead of rebuilding.

  • Serve by API, MCP, Data Pipeline or Text2Data
  • Maven, CRM, Marketer Assistant, VoS and more
  • Request status tracked end to end

Context at a glance

Where today's Mart items and Library Fields sit. Click an L2 node to open the Library.

What do you want to do?

Pick a goal, ICON takes you to the right page.

Tagging Library

Browse the catalog tree. Every leaf is a Field; the number on each node is how many Fields sit under it.

Pick an L2, L3 or L4 brick to open its shelf. Pick a Field to see its values.

Governance

Is the Library ready to be reused? Library size by Object, L3 coverage, Field-level checks, and Selector coverage. All numbers are computed live from the current Library and Mart.

L3 coverage

Library = Fields placed in the L3 node. Mart = items already assigned to it. An L3 node with Mart items but no Field is the next to build.

Field checks

Structural checks only: names in both languages, Object and Source recorded, created date recorded, unique Value IDs, at least 2 Values. Content quality (accuracy, adoption, confidence) is not measured yet; it needs usage and feedback data.

Selector coverage

The Selector reads the Library directly: only Fields with Object = Seller and at least one Value can be used to build an audience. Fields of other Objects, and Fields without Values yet, are listed here as not selectable.

Mart

Every card is a Field. Pick an L3 or L4 node on the left; add the ones you need to the cart.

What are Metric and Tag? click to fold
Metric

Arrives as a number. A count, amount, rate or score that can be summed, averaged or compared over time.

e.g. 3P ordered GMS (USD), SP Ad Spend, Average CDQ Score

Tag

Arrives as a label. A category, band, flag, text or date that says who or what the seller is; used to filter and group.

e.g. Seller Type, GMS Band, Seller Launch Date

The mark is original, never processed. It is set from how the value lands in the source table, not from how we might use it later. Mart never turns a Metric into a Tag (no banding, thresholds, ratios or rollups); anything that needs processing is requested in the cart as 需加工 and is not a Mart item.

My Request

Track the progress of your data requests. Admins can move a request through the flow.

Selector

Build a seller audience from the Library: click a tag once to include, twice to exclude. Counts update live for the current audience.

Loading...
Try:
Rule-based parser in this prototype; production should call an LLM that returns the same structured conditions.
0matched sellers
Relation within a Field

Matched sellers

API

Standardized Seller Data (metrics, tags, etc.) will be provided centrally from a single source of truth through ICON's API service. The diagram below shows which Amazon applications are already leveraging ICON's API service and which are planned to connect.

My Cart

For each Field choose how you want it: as-is (原始值), or needs processing (需加工). Processing can combine several Fields from this cart.