A fragrance owner taps the bottle cap for the first time. The brand learns the unit, the market and the moment, and confirms the item is genuine. Six months later the dashboard still shows a map of dots, and no team has changed a decision because of it. Product interactions become actionable customer data when a chain connects each tap to an action: a verified event, a consent, a named attribute and a CRM trigger.
The signal is rarely the weak point. A tap carries a specific item, a real person holding it, a place and a moment. What is missing is the plumbing between that signal and a team that acts.
Four drivers recur:
The distinction that matters: a scan nobody acts on is a cost. A scan that changes a decision is data.
Product interaction data is the record created when someone reads a product’s digital identity and the brand logs the event against that unit. It is attached to an item first and to a person only if the owner opts in.
That difference shapes the whole design. Most interactions describe the product, not the individual.
| Interaction | What it tells the brand | Data captured |
|---|---|---|
| First tap after purchase | A real owner exists, in this market | Unit, time, country, authenticity |
| Repeat taps | The product is in use | Frequency, content viewed |
| Registration | The owner agrees to be known | Consented contact, preferences |
| Ownership transfer | The item changed hands | Owner change, resale event |
| Opening (tamper-evident tag) | The product was opened or consumed | Opened status, date |
| Service scan | The product is being maintained | Service event, location |
| Failed verification | Someone holds or suspects a fake | Failed check, location |
Only registration and transfer involve a known person. The other five are useful even if no owner ever shares a name.
The process runs in seven steps, from the tap to the measured outcome.
Most programmes break at step 5. They hold events but never define their meaning, so the CRM has nothing to react to.
People tap when the product gives them something at that stage of ownership. Design one reason per stage, not one generic landing page.
| Moment | What the owner wants | What to offer | What the brand learns |
|---|---|---|---|
| Purchase | Reassurance | Authenticity result, origin | First market of use |
| First use | To get the most from it | Serving, care or usage guidance | Language, preferences |
| Ongoing use | Refills, inspiration | Routines, replenishment | Usage rhythm |
| Gifting | A meaningful gesture | Personal message, certificate | A new owner |
| Resale | Proof for the buyer | Verification, transfer | Second owner, resale market |
| Service | Care and value | Booking, history | Maintenance pattern |
The experience has to load without an app. iPhone XS and XR and later read NFC tags in the background, and Android phones read them natively with the screen on. Every extra step between tap and value loses owners.
Ask when the owner receives something clearly worth more than their details. A scan alone identifies a unit, a time and an approximate place. Linking it to a person requires an opt-in.
Four offers tend to earn it:
Keep consent progressive. The first tap works anonymously. Registration follows when the owner has a reason. Marketing permission is a separate choice. In Europe this sits under GDPR: clear notice, a specific purpose, and personal data kept apart from product events.
Define attributes once, in plain language, with a named owner for each. Raw events do not drive journeys. Attributes do.
| Event pattern | Attribute | Possible action |
|---|---|---|
| First verified tap in a market | Owner market | Localised content and offers |
| Three or more taps in 30 days | Active user | Usage tips, loyalty invitation |
| Opened status after first tap | Consumed / in use | Replenishment journey |
| Ownership transferred | Second owner | Welcome and care journey |
| Registered owner, no tap for 12 months | Dormant owner | Service reminder, re-engagement |
| Failed verification | Possible counterfeit victim | Support journey, alert to brand protection |
| Genuine tap outside intended market | Grey channel purchase | Alert to commercial team |
The thresholds in this table, such as three taps in 30 days, are starting points to calibrate against your own data.
A caution on the last row. The owner of a diverted product bought a genuine item and did nothing wrong. Give them the normal customer experience, and pass the signal to the team that manages distribution. Grey tracking shows how those scans become a diversion map.
Each journey starts from a product signal, not a campaign calendar.
Replenishment. Opened status and tap frequency estimate when a bottle runs low. The brand makes a refill offer to a known owner before they buy elsewhere.
Second-owner welcome. An ownership transfer triggers a welcome, care guidance and a certificate. The CRM gains a customer it would never have found through retail data.
Counterfeit victim support. A failed check opens a support journey and sends brand protection the location. Trust is protected and enforcement gets evidence.
Service reminders. Registration date and last service event schedule a prompt. Watches and leather goods stay better kept, and hold value in resale.
Customer data is only as good as the carrier behind it. If a code can be copied, counterfeits generate interactions that look genuine. Fake owners register, fake usage patterns trigger journeys, and marketing ends up nurturing buyers of fakes.
Compare the three common carriers on what they do for interaction data.
| Standard NFC (NTAG213 class) | Secure NFC (NTAG 424 DNA class) | Serialised printed QR | |
|---|---|---|---|
| Authentication | Static ID, can be cloned | Signed code on every tap, via SUN messaging (AES-128) | None by itself, serial can be copied |
| Standard | ISO/IEC 14443-A | ISO/IEC 14443-A, NFC Forum Type 4 | GS1 Digital Link |
| Indicative cost | About €0.19-0.23 at 1-10k units | About $0.45-0.65 at five-figure volumes, on-metal +7-30% | Near-zero marginal print cost |
| Best for | Engagement where fraud risk is low | Verified interactions and ownership | Visible, compliance-facing access |
Sources: public converter catalogues, 2026; industry sources, 2026. Above 50k units, secure tag pricing is quote-only.
A basic tag is like a door with the key hanging next to it. A secure tag generates a new one-time code each time someone approaches, and only the genuine chip can produce the right one. That is what keeps interactions from fakes out of the CRM.
On the QR row, the real cost is not the print. It is serialisation and the platform behind it.
Two physical constraints matter. Standard tags detune on metal, so on-metal tags with a ferrite layer are needed for caps, tins and watch cases. For opened status, tamper-evident variants such as the TagTamper version of the NTAG 424 DNA class report whether a closure has been broken.
A serialised QR wins in several cases. It fits very high volumes with low unit value, lines with no secondary market, and cost-constrained production. It also needs no chip, so any existing print process can carry it.
A visible carrier matters for compliance too. The ESPR (Regulation (EU) 2024/1781) is carrier-neutral, but GS1 Digital Link QR is emerging as the practical default for Digital Product Passports. A common approach is NFC for trust, visible carrier for compliance.
The trade-off is plain. A copyable QR can still feed an experience layer, but its events carry less certainty about the item. Where an owner profile, a warranty or a resale record depends on the event, a secure chip or a copy-resistant print gives a firmer base. NFC and QR compared for protection covers that choice in more depth.
| Sector | Most valuable interaction | Journey it powers |
|---|---|---|
| Wine and spirits | First tap and opened status | Serving content, collector registration, refill fraud alerts |
| Beauty and fragrance | Repeat taps and opened status | Routines, replenishment, reorder |
| Luxury leather goods | Ownership claim and transfer | Care, repair, resale welcome |
| Watches | Registration and service scans | Warranty, service reminders, certified pre-owned |
| Fashion | Care and passport scans | Care guidance, repair, resale |
The CRM is where journeys run. The identity platform is where product events live. Be deliberate about what crosses between them.
The unit identifier is the join key. It is the same one that links products to ERP and PIM data, as described in connecting ERP, PIM and PLM data to product identities. Keep unit events and person profiles separate, or every scan becomes a false lead.
Measure from tap to result. Each step has its own number, and the weakest one shows where to invest.
| Step | Metric |
|---|---|
| Coverage | Share of units with a working identity (target 99%+) |
| Interaction | Share of units tapped at least once after sale |
| Consent | Share of tapping owners who register |
| Activation | Share of registered owners in at least one triggered journey |
| Outcome | Repeat purchase, service uptake, resale transfers, counterfeit cases resolved |
Interaction rate and consent rate move most with experience design. A better reason to tap and a better reason to register usually do more than any change to the CRM.
40+ brands · 12 years · €1.5B protected
Brands that treat every tap as a decision input, not a count, build a customer record that retail data cannot supply. Selinko, part of Toppan, links verified product events to consented owners and CRM triggers through its customer engagement and data collection solution.
Product interaction data is the record of each moment someone reads a product’s digital identity, stored against that specific unit. It includes time, place, authenticity result and content viewed. It becomes personal data only when the owner opts in, for example by registering an ownership certificate.
Verify each scan against the unit, enrich it with model, batch and market, and ask for consent when the owner receives clear value. Then apply rules that convert event patterns into attributes, and let attribute changes start CRM journeys. Measure each journey back to the tap that began it.
Ask when the owner gets something concrete in return: a digital ownership certificate, an extended warranty, replenishment reminders or exclusive access. The first tap should work anonymously. Registration comes next, and marketing permission is a separate choice. In Europe, GDPR requires clear notice and a specific purpose.
No. Anonymous events have no person to attach to, so they belong in the product record, or reach the CRM only as aggregates. Send the registered owner, items owned and attribute changes. Keeping units and people separate stops every scan being treated as a lead.
Use carriers that cannot be copied. Secure NFC in the NTAG 424 DNA class produces a signed, fresh code on every tap through SUN messaging, so a cloned tag fails verification. Where a chip is uneconomic, copy-resistant print gives similar protection. Failed checks should route to brand protection, not marketing.
Common journeys include replenishment based on opened status and tap frequency, a welcome for second owners after a transfer, support after a failed verification, and service reminders from registration and service dates. Each reacts to what the owner does with the product, not to a campaign calendar.
Track five steps: coverage of units with a working identity, share of units tapped after sale, share of tapping owners who register, share of registered owners in a triggered journey, and business outcomes such as repeat purchase or resale transfers. The weakest step shows where to invest next.
Map your interactions