DataGlue
INTEGRATIONS

Every system your customers touch. Joined into one view of each customer.

From your website and CRM to tills, tickets and sensors, DataGlue joins what each system records. Each card below says exactly how that system connects.

No pitch deck. No data-engineering homework. If yours isn't listed, the call is where we check it.

Trusted by

  • Ticketek
  • me&u
  • InvestorKit
  • Team Global Express
FIG. 01 · WHAT MOVES WHERE
  • YOUR SITE · STICK
  • YOUR BOOKING SYSTEM
  • YOUR EMAIL PLATFORM
  • CRM, THROUGH YOUR WAREHOUSE
  • POS, TICKETS AND FILES
  • WEBHOOKS AND REST API
THE GLUEONE VIEW
SIGNED WEBHOOK

Results leave through a signed webhook to any compatible HTTPS endpoint. Read results through our API, ask from an AI assistant that supports MCP, or export on request.

148systems in the library

Across 24 categories. Every card says how it connects.

THE INTEGRATIONS LIBRARY

148 systems. One view of each customer. Search by name or filter by category. Every card says how it connects.

Cameras and footfall, sensors, QR orders and online visits. What they record can become tags and alerts on the right person, place or vehicle, each showing its source.

Tags about people come only from signals your systems already record, under your privacy policy and local law. Sensitive tags, such as gender or income estimates, are marked as estimates and can be switched off. Records link only where recorded identifiers support the match. People are never identified from faces.

Showing 24 of 148 integrations

Not listed? If it keeps records, it can usually join through a webhook, your warehouse, our API or a file export.

Name it on the call. Tool names are enough; no access needed.

Book a Call

Native marks a connection that runs today. Every other card says how that system joins. Vendor names belong to their owners; a listing implies no partnership, certification or endorsement.

HOW SYSTEMS CONNECT

Seven ways to bring records in. Every named system is a source.

  1. Native

    Running today: a booking system, an email platform, Postgres, a site-builder component, signed webhooks and our API.

    7 IN THE LIBRARY

  2. Stick on your site

    Stick, our site script, served from your own domain: visits, forms, UTM tags, click ids and the signals below.

    22 IN THE LIBRARY

  3. Webhook

    Inbound URLs take source records in, with fields mapped in the build.

    73 IN THE LIBRARY

  4. Automation

    No direct route? An automation tool in your own account sends source records to DataGlue, for the apps it supports.

    36 IN THE LIBRARY

  5. Your warehouse or database

    CRM records, ad spend and offline activity come in from tables you already keep. Postgres plugs straight in; other databases use a scheduled copy you run.

    66 IN THE LIBRARY

  6. REST API

    Send events and linked ids in. Keys are limited to what each source needs.

    99 IN THE LIBRARY

  7. File export

    CSV files from systems with no live route, imported with their own ids, so a re-upload never duplicates. Recurring drops agreed in the build.

    63 IN THE LIBRARY

  8. Your warehouse or our API for the rest.

Connections are agreed in the build. Vendor names belong to their owners and imply no endorsement.

SIGNALS STICK CREATES

Your site already makes this data. Stick keeps it.

Errors, slow pages, frustration and forms left half-finished rise as Findings: ranked reports that need a decision.

01WHERE THEY CAME FROM
  • AI search

    Visits from ChatGPT, Perplexity, Claude, Gemini and Copilot, as their own channel.

  • Search, social, referral and email

    Organic search, unpaid social, links from other sites and your email campaigns, told apart.

  • Ads

    Ad click ids and UTM tags, read from the landing page URL, with the first touch.

  • Your own domains

    Stick is served from your own domain. The same person carries across your domains.

02WHAT THEY DID
  • Journeys and sessions

    Every page, visit and return.

  • Reading

    Scroll depth and engaged time.

  • Content

    Text copied, video watched and site searches.

  • Form hesitation

    Pauses, corrections and the step where people stop.

  • Recoverable leads

    Details typed, never sent. Kept, and marked unconfirmed.

  • Frustration

    Rage clicks and dead clicks.

  • Errors

    JavaScript and network failures.

  • Page speed

    Core Web Vitals, by page and device.

03HOW YOU SEE IT, UNDER YOUR RULES
  • Session replay

    Watch the visit, linked to the person, with personal details masked.

  • Heatmaps

    Where people click and how far they scroll.

  • Your rules

    Consent modes, masking and an on or off switch for each signal, with an audit trail.

  • Fields we skip

    Password, card, ID and health fields are skipped. Replays mask every input by default.

Your warehouse or our API for the rest. App installs, store visits, drive-through orders, car park visits, support records and offline sales can join too. They come in through your warehouse or our API, set up with our team. Before we promise a joined-up journey, we check what each source records, what consent covers and which details link people.

We don't connect everything. We connect what one decision needs, then extend the same records to the next.

  1. 01

    Start from the decision worth money.

  2. 02

    Find where its data lives today.

  3. 03

    Connect only that. Some systems plug straight in; the rest join through your warehouse or our API.

BEFORE THE CALL

Questions about your stack. Straight answers, including the ones about what we don't connect.

If yours isn't listed, the call is where we check it.

Bring one question. We glue the systems behind it. Your team, tools and AI act on the answer.

  • 01We run HubSpot or Salesforce. Can you connect it?

    Not with a native connector today. Your CRM joins through your warehouse, our REST API or automation workflows, as part of the build. We map the path with you in the working session.

  • 02Our warehouse isn't Postgres.

    Today our inbound database connection runs on Postgres. If yours is different, we map the route in the working session, before any build is scoped.

  • 03Do you send conversions to our ad platforms directly?

    Stick keeps ad click ids and UTM tags from the landing page URL. Results use the open route described above, with the receiver and fields agreed in the build.

  • 04Is every system in the library a native integration?

    No. Each card says how that system joins: native, Stick on your site, a webhook, Zapier, Make or IFTTT, your warehouse or database, our REST API or a file export. A listing implies no partnership or endorsement. If it keeps records, it can usually join one of those ways.

  • 05Do we have to move our data?

    No. Your systems stay where they are. We bring in only what one decision needs, and each recorded activity keeps its source. Your data stays yours: your visits, activity and record matches export on request.

  • 06What does Stick collect, and who decides?

    You do. Each signal has its own on or off switch, with an audit trail. Consent modes, storage modes and masking are yours to set. Form signals skip password, card, ID and health fields. Replays mask every input by default.

  • 07Which AI model does the Glue Console use?

    One model, chosen and run by us, so there’s nothing to pick or configure. With Workspace AI on, you ask in plain English in the Glue Console and see what the answer read. You can also ask from an AI assistant that supports MCP, using a scoped DataGlue key.

WHERE YOUR DATA LIVES

Tell us where your data lives. We'll tell you what glues today and what joins in the build.

The call is about fit. Any build is a separate engagement, priced before work begins.

You don't need the answer, only the question.

Trusted by

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