Skip to content

All of your products’ measurement in one panel. From traffic to ads, from e-mail to content; one definition per metric.

Postlip Metrics collects the events of your website, app and server, validates them and ties them to where they came from. Traffic, behaviour, conversions, ads, social media, e-mail/SMS and content are read from the same data, with the same definitions.

Event ingestion
An open API compatible with the Segment Spec
Privacy
No IP address is stored
Metrics
Each with a single definition
An event from the server · Node.js
metrics.track({
  userId: 'usr_7c1e',
  event: 'signup_completed',
  properties: { plan_id: 'pro' },
});
Live streamLive · refreshes every 3 s
TimeTypeEventValidation
14:46:03tracksignup_completedValid
14:46:01page/pricingValid
14:45:58trackdemo_requestedUnplanned
14:45:51identifyusr_7c1eValid
14:45:40trackpurchase_completedRejected
Sample data · the panel’s live event stream screen

Why Postlip Metrics

A measurement platform where one number never shows two values on two screens, personal data is protected from the start and integrations use open standards.

  • One definition per metric

    Each metric’s formula is written once in the catalogue; screens, reports, alerts and the Query API use that one definition. Rates come from the sums of numerator and denominator, and every number says whether it counts by cohort or by event date.

  • Conversions sent back to ad platforms

    Conversions such as sign-ups, purchases or leads are mapped from their business role and sent to ad platforms from the server; no click id is sent without marketing consent.

  • Designed for privacy law

    No IP address is stored; e-mail addresses, phone numbers, national id, IBAN and card numbers are refused in undefined fields, and defined personal fields are hashed. Consent modes are chosen per source; test, internal and bot traffic is marked apart.

  • An open API compatible with Segment

    The Tracking API uses the same endpoints and fields as the Segment Spec, so existing client libraries work too. Postlip Metrics’ own SDKs add request signatures, rejection reasons and typed events generated from the schema.

How it works

Your product sends the event, Postlip Metrics validates and enriches it, and the panel serves the same data to every module.

  1. Send with an SDK or the API

    A one-line snippet on the website, @metrics/node on the server, plain HTTP everywhere else. Every source has its own write key.

  2. Postlip Metrics receives and validates

    The event is checked against the app’s event schema; personal data is screened, location and device are derived, the source and campaign are attached. The IP address is dropped after this step.

  3. Read it in the panel

    Every message shows up in the live stream with its validation result. The same events are the one source of the traffic, conversion, ads and report screens.

Read the setup step by step

Who it is for

Postlip Metrics was built first to measure YGMR’s own products. Organizations are opened by the platform team; product teams manage their apps and sources in the panel.

Product and growth teams
Follow the funnel from sign-up to payment, the contribution of each channel and the course of every app, with the same definitions.
Marketing
Run ads, social media, e-mail and content with spend and results on the same screen.
Analysts
Ask their own questions with the event schema, the metric catalogue and the Query API.
Developers
Create sources and keys, map events to the schema, verify them in the live stream and check the schema in CI.

Want to connect your product to Postlip Metrics?

We open your organization and set up the first source with you. The technical details of the integration are in the developer docs.