Integrations

Collection, commerce and the numbers finance trusts.

An analytics product that only reads a browser can tell you what a session did. It cannot tell you whether the invoice was paid. These connections are how a traffic number becomes a commercial one — and each page says exactly what it receives, what it lets you ask, and where it stops.

Collection

Where the traffic data comes from. One is the request; one is the experience.

Edge Network

Core traffic analytics from proxied HTTP requests. No snippet, no cost inside the request path.

Smart Beacon

The optional browser layer: SPA routes, engagement, Web Vitals, clicks and forms.

Business systems

The systems that know what the content said, what the visitor consented to, and what the money did.

Finance system

Customers, invoices, payments and subscriptions — revenue that arrived, not orders that were placed.

Accounting system

Cost, margin and recognised revenue — so a channel is judged on profit, not turnover.

Content platform

Stable identifiers for headlines, CTAs and claims — measure the message, not the URL.

Consent platform

Consent state decides the collection mode. One policy engine, never two.

Commerce & payments

Authoritative orders, subscriptions, refunds and recurring value.

Shopify

Orders, line items and refunds tied back to the visit that preceded them.

Stripe

Payments, subscriptions and refunds as authoritative revenue, with retries that cannot double-count.

WooCommerce

Orders sent server-side from WordPress, so a closed browser does not lose the sale.

Advertising & search

Campaign cost and search demand, joined to realised revenue.

Google Ads

Campaign cost joined to realised revenue, so spend is judged on money received.

Meta Ads

Meta campaign spend measured against orders, subscriptions and refunds recorded by your systems.

Google Search Console

Search queries, impressions and position per URL, joined to the revenue credited to those pages.

Developer

Deployment context, and an event API for everything else.

GitHub

Deployment annotations on the timeline, so a release can be compared before and after.

Custom event API

One POST covers any outcome a packaged integration does not — lead, booking, renewal.

Not listed

Anything else goes through the event API.

A server-side POST with an event name, a pseudonymous customer key, a value and an idempotency key covers any outcome a packaged integration does not. That is also how the packaged ones work underneath.

The event API Start free

Connect a site today. Read tomorrow's brief instead of building it.

Connect a site and the first brief arrives with the day's changes already explained — traffic separated from bots, conversions attached to revenue, and the evidence behind every sentence one click away.

Start free See how it works

Real people separated from bots Every answer shows its evidence Reveliqo runs on Reveliqo