Start with the question, not the feature. If every visitor can use the same page, publish one dependable destination. Add routing only when a visitor condition must change the destination or when an experiment has a defined outcome.
Plan before publishing
Decision tree: does legal availability, language or inventory differ by location? Use a geo rule with a fallback. Does the destination depend on operating system or device? Use device routing. Are destinations equivalent alternatives being tested? Use weighted A/B allocation. Otherwise keep the default.
- Same destination for everyone: use the default only.
- Different market or device requirement: add one explicit rule layer.
- Equivalent alternatives with a metric: use A/B allocation.
Build and test the workflow
When needs overlap, document precedence before building. A country-specific destination may intentionally bypass device or experiment logic. A broad rule placed too early may unintentionally prevent later visitors from reaching their intended route.
Worked example
Create a matrix of country, device and experiment eligibility. Include unknown location, unknown device and repeat visitor cases, then verify the final URL and UTM values for each meaningful combination in a clean browser.
Measure the right outcome
Judge routing by delivery accuracy and destination outcomes. Click share can confirm whether traffic reached a branch; it cannot show which page produced more registrations or revenue without destination-side events.
Troubleshooting checklist
- Expected experiment receives no traffic: inspect earlier geo or device rules.
- Unknown visitors fail: improve the default.
- Matrix becomes unmanageable: simplify the campaign.
Product limits and responsible use
Location, device and bot detection are inferred. Complex routing increases QA and maintenance cost, and DrutoLink does not provide arbitrary nested rule logic. Prefer the fewest rules that satisfy a real campaign requirement.