Documentation Index
Fetch the complete documentation index at: https://docs.hellocobi.com/llms.txt
Use this file to discover all available pages before exploring further.
Important: User interaction records have dependencies students. The system
validates the
student_id against existing records in the database. You
should upload student data before uploading user interaction records to ensure
proper data validation. The item_id field must reference the correct item
type as specified by item_type.Schema
Field Descriptions
Required Fields
| Field | Type | Description |
|---|---|---|
interaction_type | string | Type of interaction. One of: FILTER_CLICK, SHARE, PAGE_VIEW, DISCOUNT_CODE |
item_type | string | One of: TAG, OFFER, SHOP |
item_id | string (UUID) | UUID of the item (TAG, OFFER, KEYWORD or SHOP) as determined by item_type |
event_timestamp | int/ISO string | Event timestamp (positive integer or ISO datetime string) |
Optional Fields
| Field | Type | Description |
|---|---|---|
user_id | string | Psuedo Id of the student |
student_id | string (UUID) | UUID of the student |
city | string | City where the interaction occurred |
country | string | Country where the interaction occurred |
platform | string | One of: ANDROID, IOS, WEB, OTHER |
source | string | Source of interaction. Set to ‘COBI’ when from recommendation API, null otherwise |
recommendation_id | string (UUID) | Source of interaction. Set to ‘COBI’ when from recommendation API, null otherwise |
Example
Source Field for Recommendation Feedback
Thesource field is used to track whether user interactions originated from recommendation API responses:
null: The interaction occurred through normal user browsing (not from a recommendation)"COBI": The interaction occurred when a user clicked on or interacted with an item that was recommended by the Cobi recommendation API
- Feedback Loop: Helps the recommendation system understand which recommendations led to user engagement
- Analytics: Track the effectiveness of recommendation algorithms
- Model Training: Improve future recommendations based on user interaction patterns
Example Usage
When a user receives recommendations from the API and clicks on a recommended offer:Best Practices
- Data Validation: Ensure all required fields are present and properly formatted.
- Timestamps: Use a valid positive integer or ISO 8601 string for
event_timestamp. - Platform: Use one of the allowed values for
platform. - Source Tracking: Always set
sourceto “COBI” when tracking interactions from recommendation API responses.