Skip to main content

Monitoring & Logs

Monitoring and logging are crucial for validating ad integration. They allow partners to trace ad requests, verify correct parameters, and diagnose issues in real time. Every request or data sync generates timestamped logs that provide end-to-end visibility.

Accessing Ad Request Logs​

Logs can be viewed in the GoWit Dashboard under Auction Logs.

Features​

  • Timestamps: Each log shows exact time and relative time (e.g., “just now”).
  • Request Details: Displays fields like marketplace ID, placement ID, session ID, product ID, and request ID.
  • Pagination: Shows last 50 logs by default, with navigation for older or newer entries (retained ~15 minutes).
  • Filtering: Search by placement ID, session ID, product ID, or any keyword to narrow down results.

If “No Logs Found” appears, confirm you are testing in the right environment and have triggered an ad request.

Filtering Logs​

  • Placement ID: Filter logs by specific ad slot.
  • Session ID: Track the journey of a single user session.
  • Product ID/SKU: Find logs tied to product pages.
  • Other Keywords: Case-insensitive substring search for error codes or IDs.

This helps locate relevant entries quickly in busy logs.

Monitoring Data Source Logs​

Beyond ad requests, product feeds and APIs also generate logs accessible in the Data Sources Console.

Features​

  • Batch Import Logs: Records results of each product feed sync.
  • Filtering: View logs by data source or specific sync attempt.
  • Search: Look for product IDs or error messages inside logs.
  • Retention: Logs are timestamped and stored longer than ad request logs (days vs minutes).

This helps confirm product data is correctly imported and highlights issues early.

Best Practices for Using Logs​

  1. Test with Real IDs: Use correct placement and session IDs to ensure requests log properly.
  2. Consistent Sessions: Simulate journeys under one session ID for clear tracking.
  3. Monitor in Real Time: Keep Auction Logs open while testing for instant confirmation.
  4. Use SDK Debug Mode: Client-side debug reveals rendering issues not shown in server logs.

Troubleshooting Issues​

No Logs​

  • Confirm SDK is initialized and sending requests.
  • Check marketplace ID and environment.
  • Refresh dashboard or remove filters.

Errors or No Ads​

  • Expand logs for error messages or missing fields.
  • Verify placement IDs in GoWit dashboard.
  • Review client-side console messages.

Data Source Problems​

  • Ensure product feed jobs are triggered.
  • Review error logs for rejected products.
  • Retry after correcting issues.

Authentication Issue​

  • Confirm correct API keys and headers.