URL overrides

You can override the resolved BSR segment with URL parameters — useful for QA (view the site as any segment) and for ad campaigns (land visitors in the segment your ad targeted).

Parameters

Parameter	Purpose	Sticky for the session?
?bsr-color=<slug>	Test / QA. Force a segment for this page view only.	No
?bsr-type=<pack>&bsr-segment=<slug>	Ad attribution. Land a visitor in a specific segment.	Yes
?bs=1	Debug. Skip caches and log the resolved color/postcode.	—

?bsr-color — one-shot QA

https://your-site.nl/product/example?bsr-color=blauw

Renders that page as the blauw segment. It is not written to the session, so navigating away returns to the real segment. Ideal for checking each variant.

?bsr-type + ?bsr-segment — ad attribution

https://your-site.nl/?bsr-type=bsr4&bsr-segment=rood

This is the sticky form used for real campaigns. It persists for the browser session, so the visitor keeps that segment across pages. bsr-type must match your tenant’s current pack or the override is ignored (a safety check).

Tip

The Bluestars ads content export auto-appends these parameters per segment, so ad clicks arrive pre-attributed. You usually don’t build these URLs by hand.

Resolution order

When several signals are present, the widget resolves the segment in this order:

1. ?bsr-color test override (one-shot)
2. ?bsr-type + ?bsr-segment ad params (sticky)
3. Cached segment from earlier this session
4. A fresh server lookup (IP → postcode → segment)

Debugging with ?bs=1

Add ?bs=1 to skip the session cache and print the resolved color, postcode, and its source to the console. Combine it with the others to verify an override is being applied — see Test vs. Live.