DataGlue
Retail & malls

Fashion & grocery stores

Join browsing, loyalty and till receipts to see what shoppers buy and when they return.

Example tags

What you can learn

  • Bought zero-alcohol beer on 3 visits
  • Viewed a jacket online, then bought in store
  • First recorded store purchase after an online order
  • Bought groceries on 4 Fridays in a row
  • Used a loyalty reward, then returned next week
  • Returned an item, then bought another size
  • Bought from 2 store branches this month

Built from recorded events, using the rules we agree with you.

From events to a tag

Say what you want to learn. See how it is defined.

DataGlue shows the formula: which events count, in what order, and over what time. Our team builds and checks it with you.

This is an example rule. Your event names, time limits and links are agreed in the build.

Example formula: Find a shopper who often buys zero-alcohol beer.

Example formulaEvents → tag

Find a shopper who often buys zero-alcohol beer.

  1. Loyalty: member scanned
  2. Till: zero-alcohol beer purchased

In this order, on 3 separate visits in 30 days, for the same member.

Tag created

Buys zero-alcohol beer regularly

Use cases

Start with a question that matters.

  1. Link browsing to store buying

    Join product views and loyalty receipts where the shopper has a shared id.

  2. Find repeat buying patterns

    Use item receipts over several visits to see who buys the same products again.

  3. See first-time store shoppers

    Find a member’s first recorded till purchase after an online order.

  4. Understand returns

    Join the original receipt, return and next purchase to see what happened after a return.

Sources joined

Each system adds a piece of the story.

  • POS / tills

    Items, basket values and returns.

  • Loyalty

    Member ids and reward use.

  • Website

    Product views and online orders.

  • Store visit records

    Recorded check-ins; camera footfall stays a store total.

We agree how each source connects through your warehouse, API or the connections in your build. Person records need a shared id to join. Vehicle, shipment, machine and site tags stay on those records.

Where it goes

Send the tag where your team works.

Choose the destination. We build the route so the result can reach the tools your team already uses.

  • CRM
  • Ads platforms
  • Email tools
  • BI dashboards

These are example destinations. The formula stays the same wherever the tag is sent.

Built with your team

Describe the outcome. We’ll join the data.

Bring one buying pattern. We’ll show how your records can define it.

Book a Call

A dedicated team builds the connections, rules and destinations with you.