Observations

Record a steering render (partner-tier keys only)

First-party telemetry: a partner's consumer surface posts one row per candidate chain every time it localizes a "best choice" card, so the chosen store can be compared against the nearest store per candidate chain. Rolled up into daily, per-chain aggregates only — no per-request identifiers or coordinates are ever stored; distance_band is a client-computed bucket ('<1'|'1-3'|'3-10'|'>10'), never a raw lat/lng. Partner-tier API keys only (ShelfAtlas' own consumer surfaces); any other tier gets forbidden_tier. Chain ids are resolved from the given store ids server-side — never accepted from the client.

post/api/v1/steering-events

Request

  • Base URL: https://api.shelfatlas.com
  • URL: https://api.shelfatlas.com/api/v1/steering-events
  • Auth: HTTP bearer

Request body

product_idstring uuid required
winning_store_idstring uuid required

The store the "best choice" card actually pointed to.

visitor_keystring uuid

Opaque per-device key the consumer surface generates and keeps locally, used only for the report's COUNT(DISTINCT visitor). Omit to skip unique-visitor counting for this render.

Response

Steering rows recorded.

oktrue required
recordedinteger required

Number of involved rows rolled up.

Changes

No recorded changes to this operation across all 1 revision of this API.