DataGlue

Governed context

Collect what the decision needs. Keep every switch on record.

Set collection, consent, masking and access around one outcome, before customer context reaches your teams or AI.

An example outcome

People with Call booked. Agree which signals this count needs, and leave the rest switched off.

With Workspace AI on, DataGlue drafts rules like this from what your fields mean. You check each one before saving.

You don't need a data warehouse project first. We start with one question and the systems you already run.

FIG. 01 · CLEAR COLLECTION RULESDEMO
Consent
Collection
Masking
Access
Audit trail
YOUR RULES
ONLY WHAT THE DECISION NEEDS

Each signal with its switch.

Required systems

Start with the systems you already run. Each one holds part of the answer.

You bring one decision. Our team connects the systems behind it and builds the result with you.

  • Website and forms. the signals the decision needs
  • Consent settings. the collection rules you choose
  • Replay and tags. capture switches and masking
  • Workspace. roles, scoped keys and audit records

How each one connects.

Set Stick's capture switches, consent modes and workspace access with your team. We agree the rules for any other system with you.

Know the limits.

Rules are set per workspace with you. Approved contact fields may be kept; payment details and passwords are not captured.

Define success together

What would make the first result useful?

More teams want customer context, but the rules for collecting and sharing it are not yet agreed.

Define the permitted use, responsible owners and limits before expanding access.

Prepare the implementation review
  1. Choose a starting question

    Which customer information does this decision actually require, and who should use it?

  2. Agree what you will check

    Review the collection, consent, masking and access requirements with the relevant owners. Agree how each requirement will be checked in the proposed setup before treating it as satisfied.

  3. Use it in the next decision

    Revisit the agreed rules when adding a source, team or AI use case. A new use of the data needs its own review.

Inspect the capture rules. Each switch and change stays on record.

DEMOSTICK · CAPTURE CONTROLS · AUDIT TRAIL ONFIG. 02
CAPTURE CONTROLS
  • Journeys and sessionsOn, after analytics consent
  • Session replayOn. Typed values masked.
  • HeatmapsOn
  • Form valuesApproved contact fields onlyLIMITED
  • LocationOff
  • Tag managers and ad pixelsLoad after marketing consentHELD
  • Do Not TrackRespectedRESPECTED
  • Your cookie bannerDetectedDETECTED
  1. LOCATION SWITCHED OFF · ADMIN · AUDIT TRAIL
  2. SESSION REPLAY SWITCHED ON · ADMIN · AUDIT TRAIL
WHERE IT GOES
  • Glue ConsoleOwner, admin and member roles
  • CRMNew lead, with its source and form answers
  • Email platformBookings for confirmed CRM people, which it passes to your ad platforms
  • Your warehouseVisits, activity and record matches

DEMO. Sarah is fictional. Rules are set per workspace, with you, during the build.

Check the number. Open the records behind it.

  • Source and time. Each count opens to the form, booking, activity or CRM records behind it.
  • Every match explained. Each CRM link shows confirmed, possible, in conflict or not found, and why.
  • Your definition. Read the rule in plain English and see the count before you save.
Book a Call

On the call, we map one outcome and the systems it needs. Then our team builds it with you.

We agree the scope and the price before any work begins. No per-seat fees.

HOW THE RULES ARE SET

Decide first. Collect second. Then keep each switch on record.

Our team sets the collection rules with you. The switches and access controls stay in your workspace.

  1. 01

    Start from the decision

    Choose the outcome first. Switch on the signals it needs and leave unrelated capture off.

    SIGNALS · ON / OFFDEMO
    • JOURNEYSNeeded for the decisionON
    • LOCATIONNot neededOFF
  2. 02

    Set consent and storage

    Set essential, analytics and marketing consent levels. Use cookieless modes and respect Do Not Track. Hold tag managers and ad pixels until consent.

    CONSENT · ANALYTICS · MARKETINGDEMO
    • ANALYTICSJourneys after analytics consent
    • MARKETINGTag managers and ad pixels held until consent
    • BANNERYour cookie bannerDETECTED
  3. 03

    Mask and minimise at capture

    Mask replay input by default. Keep typed values only for approved contact fields and errors without raw text. Do not capture payment details or passwords.

    REPLAY · TYPED VALUES MASKEDDEMO
    • EMAIL FIELDApproved contact field, kept
    • NOTES FIELD•••• •••••• ••••MASKED
  4. 04

    Keep each switch on record

    Record every capture switch change. Set owner, admin and member roles, scoped API keys and an admin audit log to control access.

    AUDIT TRAILDEMO
    • ADMINLocation switched off
    • ADMINSession replay switched on

Rules you can show. Collection, masking and access, set per signal and on record.

  • A switch for each signal.On or off per capture feature, with an audit trail.
  • Consent your way.Essential, analytics and marketing levels, cookieless modes and Do Not Track.
  • Less collected at the source.Masked replay, approved contact fields only, no payment details or passwords.
  • Access by role.Owner, admin and member roles, an admin audit log and scoped API keys.

Bring the question legal keeps asking. We'll show what would be collected, and why.

On the call, we go through the decision, the signals it needs and the ones that can stay off. Then our team sets the rules with you before anything is collected.

Decide what to build first.

  • Which signals the decision needs, and which stay off.
  • What AI and each team may read.
  • When consent is required, and for what.

Keep the context you build.

Use the results in any AI tool, report or system you choose. We agree each connection with you.

We agree the scope and the price before any work begins. No per-seat fees.

A straight answer on fit, whether you work with us or not.