Meter & usage event design

Unmatched events

Find events that were accepted by Solvimon but never matched to a subscription and pricing item, so you can fix the configuration and bill them.

Why some events are rejected

An accepted event isn’t necessarily a billed event. After ingestion, Solvimon matches each event to a customer subscription and a pricing item; when no match is found, the event is stored but not billed. Every unmatched event is revenue leakage, so you want to catch them early in the billing period, not after the invoice went out.

How events become unmatched

The two most common causes:

CauseFix
The event belongs to a product item that isn’t configured on the customer’s subscriptionAdd the product item to the subscription, or correct the customer_reference on the event
The product item is configured, but the event doesn’t meet any pricing rule conditionsAdjust the pricing rules or the meter properties sent on the event

Generating the report

Trigger the unmatched events report with POST /v1/report-generate-requests using report code NOT_MATCHED_METER_DATA:

POST
/v:version/report-generate-requests
1curl -X POST https://api.solvimon.com/v1/report-generate-requests \
2     -H "X-API-KEY: <apiKey>" \
3     -H "Content-Type: application/json" \
4     -d '{
5  "report_code": "NOT_MATCHED_METER_DATA"
6}'
Try it
Response
1{
2  "id": "rgr_QzKnt5Eyf1xmM9VV5Uk8",
3  "generate_at": "2024-01-15T09:30:00Z",
4  "report_code": "NOT_MATCHED_METER_DATA",
5  "status": "PENDING",
6  "run_type": "MANUAL"
7}

Generation is asynchronous. The finished report is written to your Solvimon Google Cloud Storage bucket, where each row contains the raw event data exactly as Solvimon received it, which makes it possible to trace an unmatched event back to what your system actually sent.

If you don’t have access to your Solvimon bucket, reach out to support to get access.

Scheduled generation of this report is an upcoming feature; for now, trigger it via the API when you need it.

After fixing the configuration

Correcting the subscription, pricing plan or pricing rules doesn’t retroactively bill events that already failed to match. Reprocess the affected customer’s events so they are matched against the updated setup. See Event reprocessing.