Key steps
1
The request enters the system
The request can come from a frontend SDK, a backend API call, or an MCP tool invocation.
2
Identify intent and context
ads-server combines the query, response, and context to identify purchase intent, entities, and the right serving moment.3
Retrieve candidates
The system pulls candidate products, programs, or links from
product-feed, partner-stack-feed, and other sources.4
Rank and finalize the result
The engine deduplicates and ranks candidates using relevance, policy, and context, then determines the final result to return.
5
Serve and track
Impressions, clicks, and feedback enter tracking and
data-center, creating a measurable event trail.6
Settle revenue
Billable clicks and accounting data flow into
finance-center, which powers statements, balances, and withdrawals.What to focus on in the diagram
- Left side: SDK, API, and MCP all feed into the same decisioning path.
- Middle: Intent detection, retrieval, and ranking are the platform’s three core decision layers.
- Right side: Serving is not the endpoint; tracking, analytics, and finance complete the monetization loop.
Continue reading
System architecture
See how each service supports this end-to-end path.
Platform capabilities
See how the platform is structured across access, decisioning, observability, and settlement.