Order attribution

Order attribution is the practice of attaching structured metadata to CLOB orders that identifies the routing source that submitted them. On Polymarket this metadata lets the platform recognise which Builder (or integration) routed a trade so that builder fees, volume tracking, and leaderboard credits can be applied.

Key takeaways

• Order attribution tags orders with a Builder identity so Polymarket can pay builder fees and record volume.
• Attribution is used in Polymarket’s Builder Program to assign rewards and leaderboard placement.
• Attribution relies on the relayer and client SDKs rather than on-chain fields; the CLOB accepts attributed orders with appropriate headers or credentials.

In context

When a third party routes orders through Polymarket’s CLOB as part of the Builder Program, their integration supplies attribution information (typically via headers or API credentials recognised by the Relayer and CLOB). The attribution links executed volume and taker fees back to that Builder’s account, which is then eligible for the program’s rewards and daily relayer limits. Tiers in the Builder Program—Unverified, Verified, and Partner—affect limits and reward entitlements; attribution is the mechanism that ties a given order to a Builder’s tier and ledger.

How attribution appears in practice

• Client SDKs and the Relayer accept attribution headers or API keys that uniquely identify a Builder.
• Attributed trades are recorded in Polymarket’s backend so builder fees (paid in basis points) and leaderboard volume credit can be computed.
• Attribution does not change the on-chain settlement semantics of CTF outcome tokens; it is an exchange-layer bookkeeping feature used for rewards and routing.

See also

• /glossary/builder