DataGlue

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.

Example outcome formula

Count people with a Call booked record. Agree which signals this outcome needs, and leave unrelated capture switched off.

Drafted from your source definitions. Review before saving.

Book a Call

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

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

Connect the required systems. Start with the records you have.

Your team brings one decision. Our dedicated team connects the sources and builds it 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

Agree the connection route.

Set Stick capture controls, consent modes and workspace access with your team. Rules for additional source systems are agreed in the build.

Know the limits.

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

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, with match keys, which it forwards to your ad platforms
  • Your warehouseSessions, events and identity links

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, event or CRM records behind it.
  • Link evidence. Confirmed, candidate, conflict and unmatched CRM links keep their state in view.
  • Your definition. Read the plain-English formula and preview the count before saving.
Book a Call

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

Scoped and priced to the outcome, agreed before work begins. No seat licences.

HOW THE RULES ARE SET

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

A dedicated team sets the collection rules with you. Capture 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. In the Outcome Build, a dedicated 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.

The same model can feed your LLM, BI tool or destination. We agree each connection in the build.

Scoped and priced to the outcome, agreed before work begins. No seat licences.

Book a CallSee the Outcomes

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