Brickwatch Partners - Technical specifications
Technical specifications
Brickwatch checks the prices of all LEGO® sets on your site several times per day. To make this possible, we require access to a product feed with up-to-date price information.
Feed requirements
- Format: CSV, XML or JSON
- The feed must be publicly accessible (no login or IP restrictions).
- Data must be updated at least once per day, preferably more frequently
- Brickwatch retrieves the feed multiple times per day and keeps it temporarily cached for a few hours
- Files may be compressed (e.g.
.gz)
Minimum fields
| Field | Description |
|---|---|
set_number | LEGO set number (e.g. 75419) |
title | Product name |
price | Current sales price (numeric, in EUR) |
url | Deeplink to the product page |
availability | In stock / Out of stock (see https://schema.org/availability) |
ean | Optional, helps with matching |
An existing Google Shopping feed will generally meet these requirements.
Feed quality
- Use stable, direct URLs for product pages and images
- Provide only products with correct prices and currency (EUR)
- Brickwatch is not a testing environment for price or assortment experiments. The feed should represent your current, complete offer.
Exceptions may be made for sets that are no longer in production. - Persistent incorrect or incomplete data may result in the connection being terminated.
Shipping information
Please provide us with shipping costs for the Netherlands, Belgium, France and Germany (if applicable).
Price-dependent shipping rules are supported, for example: € 6.95 below € 50 – free shipping above that.
Billing
For CPC partnerships, Brickwatch invoices monthly based on the number of valid clicks measured in our system.Clicks are filtered for unique visitors and bots to ensure only genuine traffic is billed.
Measurement differences
We follow industry-standard methods for tracking outbound clicks.
It’s normal for our numbers to differ slightly from data reported in tools such as Google Analytics.
Common reasons include:
- Not all browsers send a referrer header, which analytics platforms use to identify traffic sources.
- Analytics programs like Google Analytics try to count the number of visitors on a page, compared to actual page-visits. Especially when a user visits multiple sets on your site through the Brickwatch tracking system within a short timespan, the Analytics service might count it as one visit.
- Some traffic originates from email notifications, which may not always be recognised as coming from Brickwatch.
- Certain users have Do Not Track enabled in their browser, preventing analytics tools from recording their click.
- Technical interruptions (for example, network issues or script errors) can stop a visit from being logged on your side even though it was already counted in Brickwatch’s tracking system.