In short
Where a touchpoint sends someone is not stored in the artwork. It is a decision made at the moment of each interaction, and these are the controls that make it.
They are evaluated in a fixed order. If a touchpoint ever behaves unexpectedly, reading that order from the top will find the cause almost every time.
On this page
The order everything is evaluated in
This diagram is the most useful thing on the page. Every control below sits at one of these gates, and knowing which gate a control belongs to tells you why it is or is not firing.
Destination and fallback
The destination is where the touchpoint sends people when no conditional rule applies. Change it whenever you like; every door already in the field follows immediately.
The fallback is the safety net. It is used when the item is past its useful life, or when rules exist but none of them match the person in front of you. Leaving it empty is the most common self-inflicted wound in this whole system — a person who matches nothing then gets a dead end instead of your home page or a "this has ended" notice.
Conditional routing
| Rule | What it tests | Typical use |
|---|---|---|
| Location | Country or region | Regional stores, language markets, licensing restrictions |
| Geofence | Inside a drawn area | On-site content, venue offers, presence-based entitlements |
| Device and platform | iOS, Android, desktop | App store links, platform-specific instructions |
| Language | Device language setting | Multilingual content without asking the person to choose |
| Scan count | First interaction, or after a threshold | Welcome content on first scan, different content thereafter |
| Schedule | Date and time windows | Launch dates, event phases, opening hours, seasonal changes |
Rules are evaluated top to bottom and the first match wins, so put your most specific rules above your general ones. A broad "everyone in Europe" rule sitting above a narrow "Germany, on launch day" rule means the narrow one never fires — and nothing warns you, because both rules are perfectly valid.
When They Scan: timing rules
The editor has a separate When They Scan panel for rules about when a scan happens rather than who is scanning. The same rules can be set in the Create a TouchPoint wizard; both write to the same record.
| Rule | What it tests |
|---|---|
| After this many scans | A whole number, counted from the first scan |
| Before this date | Scans before the date you give |
| From this date onward | Scans on or after the date you give |
Each rule sends matching scans to its own address. The order of evaluation is fixed: who is scanning (country, device and language, from the targeting sections) is checked first, then when they scan, top to bottom, with the first match winning. Anything that matches nothing falls through to the main destination.
- Dates are compared in UTC, not your local time. A rule set for “tomorrow” can start the evening before in the Americas
- The panel shows what the record does right now: today’s date, scans so far, where it is resolving, and why
- A rule marked Cannot match has a date that has passed. It is kept rather than removed, because a printed Mark may have been made while it was live
Limits and lifecycle
| Control | Effect | Worth knowing |
|---|---|---|
| Active toggle | Switches the item on or off immediately | Reversible. The fastest way to pull content that is wrong |
| Expiry | Retires the item on a date | Set it when you create seasonal work, not when you remember later |
| Scan limit | Retires after a number of interactions | Counts interactions, not people — one person scanning five times uses five |
Protection
Three protections, often confused with each other. Two decide who gets in; the third decides how the content is handed over.
- Password asks for a shared password before the content opens.
- Secure restricts opening to the accounts whose email you add, signed in to their own Linxy account after Face ID or fingerprint. There is nothing for them to accept.
- URL Shielding decides how the content is delivered — through short-lived view tokens, so the real destination address is never handed to the browser and a copied viewer address neither keeps working nor opens on any other device or browser. See How protected content opens.
You can use any of them alone. Secure or Password without URL Shielding means the right person opens a normal, copyable link. URL Shielding without either means anyone may open it, but nobody can pass the address on. Most sensitive material wants a gate and URL Shielding together.
Notifications and webhooks
- Notifications alert you on interaction — every scan, first scan only, or when a threshold is crossed. First-scan alerts are the useful default; per-scan alerts become noise quickly on anything popular.
- Webhooks post interaction events to your own system, which is how you feed a CRM, a fulfillment process, or your own analytics.
A worked example
A distillery prints a Mark into the label artwork of a limited release. Here is how the controls stack up over the life of that bottle.
- Before launch.Item active, with a schedule rule pointing at a holding page until release day. Fallback set to the brand's main page.
- Launch week.Schedule rule expires. A device rule sends mobile visitors to a tasting film and desktop visitors to the shop. A first-scan rule offers a Connection; repeat scans go straight to the film.
- In market.A location rule routes visitors in markets where the release is not sold to a "where to find us" page rather than a checkout they cannot use.
- Sold out.Destination changed once to a waiting-list page. No rules touched, nothing reprinted, and every bottle already in homes and bars follows along.
- Two years later.The item is switched off. Because a fallback exists, late scans land on the brand page rather than an error — which matters, because bottles outlive campaigns.
Debugging a touchpoint that misbehaves
Work down the gates in the diagram, in order. The cause is nearly always at the first gate you have not actually verified.
| Symptom | Check first |
|---|---|
| Everyone gets the same thing despite rules | A broad rule sitting above the specific ones, matching everybody |
| A rule you added never fires | Its position in the list, and whether an earlier rule already matches |
| Some people see a password prompt unexpectedly | Protection is gate 2 — it applies before any routing you set up |
| Works for you, fails for customers | Location, language, or device rules; you are testing from one place on one phone |
| Suddenly everyone lands on the fallback | An expiry or scan limit was reached, or the item was switched off |
| A scheduled change did not happen | Time zone of the schedule, and whether the rule sits below one that already matches |