We log every request made to ILSA. These are used for a various things:
- The request statistics of your instance that you can see in the Backoffice.
- Reporting statistics to the advertiser through DV.
- Replaying recent requests when verifying a new datafile.
- Internal monitoring of ILSA.
This, along with some internal fields, is what the log record looks like.
| Field | Description |
|---|---|
| timestamp | Date and time of the request |
| instance | The ID of the instance |
| locale | The requested locale (for example, en_GB) |
| duration | The time it took for the ILSA server to respond (in ms) |
| type | The API call (dropdowncontents, searchresults, vehicle, …) |
| object_ids | Any object id requested or returned by the API call |
| fieldset | The requested fieldset (for searchresults and vehicle API calls) |
| offset | The requested offset (used with some API calls) |
| limit | The requested maximum number of results (used with some API calls) |
| order | The requested sorting (used with some API calls) |
| filters | The requested filters (used with some API calls) |
| request_ip | The IP address of the client |
| visitor_ip | The real IP address, see Visitor IP below |
| user_agent | The user agent string |
| session_id | See Session IDs below |
| refererrer | The referrer as sent by the user agent |
| origin | The origin as sent by the user agent |
| http_code | The HTTP status code as returned by ILSA |
| error_message | If the request failed, the reason |
| is_bot | true if the request is likely made by a bot |
| loglabels | See custom loglabels below |
We can export the logs to your business intelligence tool. Contact us for more information.
When counting the number of views of a vehicle, we count only /vehicle calls and exclude development IP addresses, bots, machine requests and non-production requests.
If requests are initiated by an automated process (for example a cronjob), rather than a user visiting your site, include ?_machine_request=true in your API call so we can exclude them from the statistics.
You can attach a _session_id to each request. This will help correlate visitors in the statistics and request logs.
If you are proxying requests through your own server, all requests to us will show your server IP address. You can supply &_visitor_ip=192.0.2.1 to indicate the original users IP address (192.0.2.1 in this example). We can use this for detecting bots.
With every request you can pass custom loglabels like ?_loglabel.utm_campaign=example-campaign. You can supply any key+value you want and we’ll make them available in the statistics and request logs.