config.collection_id.
Creating and managing collections is free.
What’s in a collection
Each collection is made of one or more clauses. Inside a clause, fill in any of:- Any of these brands (
brand_ids) - Any of these websites (
website_ids) - Any of these categories (
category_ids) - Any of these products (
product_ids)
Add a clause
Nike running shoes or anything from REI.
Add to the clause
Only Nike running shoes, and only from REI.
A collection can have up to 100 clauses, 100 IDs in each list per clause, and
500
product_ids in total.nike.com.
You can create an empty collection (clauses: []) and add clauses later.
Optional user_id ties the collection to one of your users. If a later search uses this collection and you don’t send x-user-id, Channel3 attributes clicks to that user.
Search, browse, image search, and similar
Pass the ID onconfig.collection_id.
config.collection_id field works on POST /v1/image-search, POST /v1/similar, and POST /experimental/find-products-in-image. A 404 means that ID doesn’t exist. /v1/lookup doesn’t take a collection.
List collections
List is paginated. Passuser_id to see one user’s collections.
Get a collection
Fetch one collection by ID. The response includes name, description,user_id, and every clause.
Update a collection
PATCH can replace a clause in place byclause_id, remove one, or add another clause.