A product source decides which products a campaign shows. You build it once under Product Sources, then point any campaign, widget or shoppable video at it.
Every source answers two questions: where do the products come from (the type, e.g. best sellers or a collection) and from what context (the entry point, e.g. the product page the visitor is on).
Options every source has
Option | Notes |
Name | Required. Up to 100 characters. Shown wherever you pick a source. |
Type | Required. Where the products come from. Changing it resets the type-specific options below it. |
Entry point | Required. The context the source runs in. Some types lock this to one value. |
Description | Optional, up to 500 characters. For your own team. |
Active | On by default. An inactive source returns nothing, so campaigns pointing at it show nothing. |
Entry points
Entry point | Means |
Generic | No product context. The source runs the same for everyone, on any page. |
Current Product | The product page the visitor is viewing. Only here can conditions compare against "the current product". |
Current Collection | The collection page the visitor is viewing. |
The entry point list greys out anything the selected type does not support, so you cannot save a combination that would return nothing.
The types
Type | Shows | Entry point |
Your top sellers by quantity or revenue | Generic, Current Product, Current Collection | |
Products added in the last N days | Generic | |
What this visitor has already looked at | Generic | |
Products matching rules you write | Current Product, Current Collection | |
A live AI blend you tune with sliders | Generic | |
What this customer bought before | Generic | |
Just the product being viewed | Current Product | |
Everything in collections you choose | Generic | |
A list you pick by hand | Generic |
Personalised Recommendation is AI-powered and is highlighted in the type list. It is worked out live for each visitor at the moment the campaign is shown, rather than read from a prepared list.
Filters
Most sources accept conditions that narrow what they return. Two things decide which conditions you can use, and both are shown on the form itself. For the conditions themselves, see the filter conditions reference.
Primary and secondary
Secondary filters describe the products the source shows. Nearly every source that supports filtering supports these.
Primary filters describe the products recommendations are built for — which products get a recommendation list at all. Only Similar + Current Product uses them.
Static and dynamic
Static conditions run when recommendations are generated, as a database query over the whole catalogue. Any product field can be used: tags, category, vendor, price, metafields.
Dynamic conditions run every time the campaign is shown, against the products already picked. Because they compare against the product the visitor is looking at, they are limited to tags, metafields and variant availability.
A set only appears on the form where it is actually read. If you do not see one, that source does not use it.
Match ALL / Match ANY
With two or more conditions in a set, you choose whether a product must satisfy all of them or any one of them.
Match every condition strictly
On the secondary set only. Left off, if the full set of conditions finds too few products the generator relaxes them one at a time — dropping the last condition, then the one before it — until it has filled the list, up to 20 products per source product. Turned on, it takes what the full set finds and stops.
Turn it on when a condition is a hard rule — an exclusion, a compliance constraint — rather than a preference. Order your conditions most to least important, because the last one is the first to be dropped.
