With static filters you can reject vehicles from being accepted to your ILSA instance. This happens as part of the enrichment phase of the data flow, right after vehicles were received from DV.
TL;DR?
Use static filters to reject vehicles from your site. Use per-request filtering only to hide vehicles from specific search requests.
These are the differences between static filters and per-request filtering:
- When vehicles are rejected by a static filter, the advertiser will see a (translated) error message explaining why their vehicle isn’t advertised on your site.
- Vehicles hidden with per-request filters can still be viewed on your website with the URL we give back to the advertiser.
/dropdowncontents
will hide options that are not in your dataset, but will show optionsinfo that would be available with looser per-request filters.- Performance: all vehicles that passed the static filters are considered for every search query.
- When rejected by a static filter, enrichers won’t be run for a vehicle.
- Vehicles rejected by static filters are not counted towards the size of your ILSA instance, keeping your monthly ILSA costs lower.
Some common examples of static filters are:
- Requiring
general.category
to becar
orvan
, because you don’t support trucks, bicycles etc. - Requiring at least 1 image
- Requiring
sales_conditions.pricing.asking.business.in_eur.incl_vat.amount
to be at least € 100. - Rejecting vehicles that are marked as sold in the advertisers’ VMS.
You can see the static filters for your instance in the Backoffice. Making changes in the Backoffice is not yet supported. Contact us to make changes.
INFO
You can also reject vehicles by returning a HTTP 422 error from an enricher for complex cases, but those errors messages can’t be translated for the advertiser by DV.