Event Types
Topsort tracks three core event types:| Event | Description | When to Send |
|---|---|---|
| Impression | User views a promoted product | When a sponsored product is rendered on screen |
| Click | User clicks on a promoted product | When a user clicks a sponsored product |
| Purchase | User completes a transaction | When an order is confirmed |
Integration Options
Direct API
Send events directly to Topsort’s Events API for maximum control and flexibility.
Analytics.js
Use our JavaScript SDK for easy client-side event tracking.
Twilio Segment
Route events through Segment if you’re already using it for analytics.
RudderStack
Integrate via RudderStack for unified event routing.
Key Concepts
Resolved Bid ID
TheresolvedBidId is a unique identifier returned from the Auctions API that links an event to a specific auction winner. This is required for impression and click events to enable proper attribution.
Event Attribution
Events are attributed to campaigns based on:- Direct attribution: User interacts with a promoted product and converts
- Halo attribution: User views a promoted product but purchases a different product from the same vendor
Implementation Steps
1
Store the Resolved Bid ID
When displaying auction winners, store the
resolvedBidId from the auction response.2
Track Impressions
Send an impression event when a sponsored product becomes visible to the user.
3
Track Clicks
Send a click event when a user clicks on a sponsored product.
4
Track Purchases
Send purchase events when orders are completed, including all purchased products.
Example: Sending Events
Next Steps
- Events API Reference - Full API documentation
- Analytics.js Guide - Client-side tracking
- Attribution Models - Understanding attribution