For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
LoginSandbox
Platform GuidesAPI DocsSDKMCP ServerChangelog
Platform GuidesAPI DocsSDKMCP ServerChangelog
  • Getting started
    • Introduction
    • Concepts
    • Onboarding guide
  • Use cases
    • Monetizing an AI agent
    • Pricing models for AI products
    • Configuring entitlements for AI products
  • Usage metering & events
    • Meters
    • Usage events
    • Unmatched events
    • Event reprocessing
  • Products & plans
    • Product Catalog
    • Pricing Plans
    • Features & Entitlements
  • Wallets & credits
    • Credit types & wallets
    • Credits in pricing plans
  • Customers & subscriptions
    • Customers
    • Subscriptions
    • Quotes
  • Invoicing
    • Invoices
    • Invoice corrections
    • Payment Collections
    • Tax
    • Currencies & Exchange rates
    • E-invoicing
  • Analytics & reporting
    • Insights
    • Report downloads
    • Revenue Recognition & Deferred Revenue
  • Integrations
    • CRM
    • ERP
    • Email Providers
    • Data Imports: Event File Uploads
    • Data Exports
    • Payment Service Providers
  • Settings & admin
    • Billing entities
    • Payment Options
    • User management
    • Customising invoices
    • Custom fields
    • Default platform settings
    • API key creation
    • Alert Rules
    • Workflows
  • Workflows
    • Workflow Triggers
    • Workflow Actions
    • Monitoring and Audit
    • Common Use Cases
  • For developers
    • Introduction
    • Authentication
    • Local development setup
    • API
    • Errors
    • Troubleshooting
    • Query Parameters
    • Expanding Responses
    • Idempotency
    • Timestamp formatting
    • Webhooks
    • Locale
    • MCP Server
LoginSandbox
Usage metering & events

Unmatched events

Was this page helpful?
Previous

Event reprocessing

Next
Built with

To avoid revenue leakage its really important to find out if all ingested events are not only accepted by Solvimon but also matched to a subscription and a pricing item. Unmatched events are not billed since Solvimon cannot find the price associated with the event. The reason for this can be incorrectly configured subscriptions, pricing plans or pricing rules.

Solvimon provides reports to identify these events. The reports can be found in your Solvimon Google Bucket.

If you don’t have access to this bucket, reach out to our support to get access.

To trigger the report generation you can ask your engineer to make an API call to our platform using the following code.

curl -v --request POST -H "X-API-KEY: xxxxxxxxx"
-H "X-PLATFORM-ID: plat_xxxxxxxxxx"
-H "Content-Type: application/json"
--url https://api.solvimon.com/v1/report-generate-requests --data
'{"report_code":"NOT_MATCHED_METER_DATA"}'

The Unmatched event report

The unmatched event report contains the raw data which is identical to how Solvimon received the event.

Finding reason why events are unmatched

In most cases the events are not matched since either the event belongs to a Product Item which is not configured on the customer subscription. However in case the product item is configured and there are pricing rules, the event can be unmatched because the pricing rule conditions were not met.

After updating the pricing settings the user can start the reprocessing of events on the customer level. Please find the instructions here. Reprocessing Events


UPCOMING FEATURE:

Soon we will have an option to automatically schedule the generation of the report.