How the connection works
During onboarding, you provide a full-access API key that RevenueBug uses only for read requests. RevenueBug validates the credential and derives or asks you to confirm a selected Lemon Squeezy store. Nothing is published until the credential, website, and selected scope pass validation.
RevenueBug discovers stores, matches their root domains where possible, and imports store orders and qualifying subscription invoices, including proportional refunds.
What appears on the public listing
The listing includes trailing-30-day revenue, lifetime revenue, growth, and a daily revenue plot. The source credential and transaction-level customer data remain private. Revenue can briefly show zero while the first historical import is running.
Scope and attribution
The selected scope is important: a selected Lemon Squeezy store may contain revenue from more than one product. A verified connection proves the data came from that provider scope; it does not independently audit every product’s ownership or expenses.
Provider-specific limitation: Lemon Squeezy does not offer a restricted credential for this flow, and its adapter cannot classify disputes.
Credential safety
Create a dedicated read-only credential where possible, grant only documented permissions, and revoke it when you stop using the listing. RevenueBug encrypts stored provider credentials and does not expose them through public listing responses.