REST API, joined, in and out.
DataGlue marries REST API data with your other systems and sends outcomes back. Every number shows its formula and its records.
REST API: DataGlue's own HTTP interface for sending events in and reading people, sessions and conversions out.
- IN + OUT
- NATIVE
Bring REST API and one decision to the call. Tool names are enough; no access needed.
Trusted by
- NativeIN + OUT
What moves between REST API and DataGlue. Events and linked ids come in. People, sessions, events and conversions go out.
- IN + OUTNATIVE
Native
A native connection, built and running today. Send events in, read people, sessions, events and conversions out, and link ids from your other systems. Keys carry scopes, so each system gets only what it needs.
Connections are agreed in the build. We check the source data, consent and identifiers before promising a linked journey. REST API is a trademark of its owner; this page implies no partnership or endorsement.
Describe the outcome. DataGlue works it out and shows you the formula.
- 01
Describe the outcome you want in plain words, such as "In-house systems joined".
- 02
DataGlue works it out from the definitions of your data sources, REST API included, and shows the formula in concise English.
- 03
Send it on: to reports, BI tools, any destination, or the AI tools your team already uses.
- EXAMPLE OUTCOME 01
In-house systems joined
THE FORMULARecords from systems your team built, linked to the same people as everything else.
- EXAMPLE OUTCOME 02
Outcomes in your own product
THE FORMULAYour app reads a person's outcomes and first touch from the API.
Want one of these from your REST API data? We map the route and the first outcome on the call.
Book a CallBring REST API and one decision. We'll map the route and the first outcome on the call.
The call scopes fit. The build is a separate engagement, priced before work begins.