We recommend communicating with ILSA directly from your visitor’s browser (using XHR / AJAX) rather than sending the requests from your server.

This provides the best performance (latency) for your users, since data does not need to flow through your server. It also eliminates a possible point of failure, especially if most of your site is static and served by a CDN.
Finally it helps ILSA in giving you more accurate statistics.

By using modern front-end frameworks like VueJS, Angular or React you should be able to easily render the information received by ILSA in the browser, resulting in a fast and snappy user experience.

ILSA is designed to be blazingly fast and as such you shouldn’t need to cache our responses. ILSA can update every few minutes, so your cache would be outdated quickly anyway.

By sending a request per visitor, we can also calculate statistics for you and report vehicle views statistics back to the advertiser through DV.

If you use Client Side Rendering the page load to your server can be cached and the requests to ILSA can be done by the browser.

Talk to us if you do need caching.

When configuring your instance, only include fields that you actually need in your fieldsets. Including unused fields wastes your visitor’s bandwidth and resources on our side.

Our development team is happy to answer your questions and help you build the best ILSA integration possible. Contact us to get a Slack channel set up.

We appreciate feedback and would love to know about missing features.

We can discuss options like:
* Client Side Rendering
* Updating the cached response from your server from javascript.
* Sending an event whenever ILSA updates to purge your cache. (Which wouldn’t solve the statistics.)