DataGlue

A common problem / a joined result

Offline sales can't be linked to online visits

Join a web visit to a store purchase when a shared key supports the link.

Book a Call

Talk through the sources behind your question.

01 / The symptom

Sound familiar?

People browse online and buy in store. Your website report stops at the visit, while the till shows a sale with no earlier journey.

02 / Why it happens

The pieces live apart.

The web session, shop visit and receipt live in separate systems. A shared member or customer key can join them; a nearby timestamp alone cannot prove that two records belong to one person.

Separate systems / separate pieces
  1. Website

    The signed-in visit

  2. POS

    The store receipt

  3. Loyalty

    The member and reward

Each source has a piece. The join gives the pieces a shared meaning.

03 / What changes with DataGlue

One rule. A useful result.

Example rule / events → tag

  1. Website: member viewed a product

  2. POS: member bought in store

  3. Loyalty: reward used

In this order, within 30 days, on the same member ID.

Resulting tag

Online member bought in store

Illustrative rule. Sources, match keys and timing are agreed in the build.

What you get

  • A joined journey for records with a supported match.
  • A visible distinction between linked and unknown visits.
  • An outcome tag for CRM, BI or an agreed ads destination.

Systems usually joined: Website, POS, Loyalty. The team checks the records, match keys and destination with you.

04 / Who feels it

A question that crosses teams.

Retail marketers and customer teams working across websites, shops and venues.

05 / Questions before the build

Good questions. Clear answers.

Do we need a loyalty programme?

Not always. A loyalty member ID is one possible key. The team checks whether your sources offer another confirmed customer, order or account link.

Can camera or Wi-Fi data identify the shopper?

Not on its own. Those records may add a recorded visit or location, but a person-level link needs supporting identity evidence and the agreed data controls.

Will all our past receipts be matched?

No guarantee. Coverage depends on the records and keys you already have. The team checks the available history and leaves unsupported matches unconfirmed.

06 / Keep exploring

Follow the next piece.

Build it with us

Bring the problem. We'll map the pieces.

A dedicated team checks the sources, defines the result and builds it with you. Scope and price are agreed with the team.

Book a Call