DataGlue

DataGlue for Retail & shopping-centre operators

I see footfall and sales. I need to know my regulars.

Your tills, loyalty program, website and car park each see part of a regular’s week. DataGlue joins the records that share a member ID. Store totals stay store totals.

A dedicated team builds it with you. Start with one decision.

One question, every system
POS / tillsLoyaltyWebsiteGuest Wi-Fi
DataGlue

Shows the rule.

Which steps count, and in what order.

Example resultSigned in online, then bought

Sent to your CRM, email, ad platforms, reports or AI tools.
We agree each connection with you.

Sound familiar?

You could count the visits. You just can’t connect them to the people who buy.

Footfall and receipts sit apart

A busy Saturday doesn’t show which member visits became purchases.

Online and store teams see halves

A member browses at home and buys at the till, in two reports.

Loyalty misses part of the visit

Check-ins and purchases aren’t always tied to the same member.

Counts get mistaken for people

A camera count or a car in the car park can’t name a customer.

A joined picture

Join what you know. Keep the unknowns clear.

Use member IDs to join the steps you can confirm. DataGlue shows the rule and the limits of each source. Footfall and vehicle records keep their own meaning.

Systems usually joined

The same systems, joined
  1. POS / tills
  2. Loyalty
  3. Website
  4. Guest Wi-Fi
  5. Camera footfall
  6. Number-plate readers
THE GLUE
Signed in online, then boughtOne result, counted the same way by every team.
  1. Example 01

    1. Website: member signed in
    2. Loyalty: member purchase recorded

    In this order, within 7 days, for the same member ID.

    Steps → result

    Signed in online, then bought

  2. Example 02

    1. Loyalty: reward issued
    2. POS: reward used on a purchase

    In this order, within 14 days, for the same member.

    Steps → result

    Reward used in store

  3. Example 03

    1. Car park: member’s plate read

    At least 4 times in 30 days, for the same member. The member registered the plate for loyalty parking.

    Steps → result

    Regular visitor

Example outcomes, not customer results. We agree the systems, how records match, the time windows and where results go in your build.

How it works

One question. Five steps with your team.

The same build, shaped around your decision and the systems behind it.

  1. Book a call

    Bring one question.

    Talk it through with the people who would build it. We find where its data lives today.

  2. Architecture review

    Map every source behind it.

    We sit with the teams closest to the decision. We map where its data lives, where it disagrees and where it goes missing, then show you what it looks like glued together.

  3. Build together

    We connect the pieces.

    Our team finds the records that matter and joins them into one view of each customer. Records join only where they clearly match. Your systems stay where they are.

  4. Go live

    Your first result, ready to use.

    We take the first result live in your Glue Console. Open any count to see the records behind it. With Workspace AI on, ask in plain English and see what the answer read.

  5. Keep building

    The next outcome reuses what you built.

    We roll out in phases, each measured against the outcome. Each new outcome starts from the systems and matches you already have.

More about how we work
What you get

Useful context. In the tools you use.

  1. Member journeys joined

    Follow a member from the visit to the purchase.

  2. Store and web together

    Both channels on one record of the customer.

  3. Rewards you can follow

    See which rewards get used at the till.

  4. Honest footfall

    Crowd counts stay separate from named customers.

  5. Tags your team can use

    Send results to your CRM, email, ad platforms or reports.

  6. Your existing systems

    Join the tills and loyalty tools you already run.

See the working

Check the approach before the call.

Read the outcome examples, sector pages and comparisons behind this approach. They explain the method. They are not measured results for your role.

Trusted by

  • Ticketek
  • me&u
  • InvestorKit
  • Team Global Express
Fair questions

What you might be wondering.

Couldn’t I just compare footfall with sales?

Yes, for store-level trends. Tying a visit to a purchase needs a shared ID, such as a member number. DataGlue keeps those linked journeys apart from crowd counts.

Can a camera or number plate identify a shopper?

Not on its own. Camera footfall stays a count, and a plate describes a vehicle. A link to a member needs their consent, such as a plate registered for loyalty parking.

Do we need a data team or clean data first?

No. Bring one question and the names of the systems behind it. A dedicated team maps them, joins the records and builds the result with you. Your team sets the ownership, privacy and quality rules.

What does it cost, and what happens on the call?

The first call checks the outcome, the systems and the fit. You don’t need to give us access to anything. If it fits, we map the data together in a working session. The build is scoped and priced before work begins, and there is no public rate card.

Your next step

Bring the question you keep coming back to.

We glue the systems behind it. Your team, tools and AI act on the answer. No system access needed for the first call.

Book a Call

Free first call. Scope and price agreed before a build begins.

Is it a fit?

An honest fit check.

A good fit

This may suit you if…

  • Your question crosses tills, loyalty and visits.
  • Members have IDs you’re allowed to use.
  • You want crowd counts and named customers kept apart.

Probably not a fit

This may not suit you if…

  • You only need a footfall total.
  • You expect cameras to reveal who bought what.
  • You want to treat every car as a known shopper.
See every role we help