Blockmetry produces anonmyized web analytics hit-level data that is stored in customer-controlled databases. This document describes the details of this data integration.
Sending measurements to Blockmetry
Blockmetry can receive measurements through a number of channels:
- JavasScript (with a <noscript> tag) for web traffic measurement
- Log files records sent via an API We plan to add to these channels in the future. Please get in touch if you have a specific use case or need.
Blockmetry measurement processing
The Blockmetry pipeline is built for high availability, using AWS products such as AWS Lambda. This has many technical and user-facing benefits, such as high availability and user-visible low response times.
# Storing hit-level data records in customer databases
The final step is to produce the analytics record with all the (anonymized) parameters.
The analytics record, called BMRecord, is produced only if the measurement is detected to have come not from a bot/spammer. **This means that not all Blockmetry processing will produce an analytics record**.
If produced, the analytics record is stored in a customer-owned data asset such as:
* An S3 bucket to store a separate file for each record,
* A data pipeline, such as AWS Kinesis which can send the data to Redshift, Elastic, or for further processing.
**Blockmetry is given write-only access to these customer-owned data assets**. You really own your data. Part of the privacy promises from Blockmetry is that we cannot read back the analytics data.
# Sample Blockmetry record
This is a simplified Blockmetry analytics record that is sent to a customer's database, rendered as JSON: