How the connection works
During onboarding, you provide a store secret key that RevenueBug uses only for read requests. RevenueBug validates the credential and derives or asks you to confirm one Blink store. Nothing is published until the credential, website, and selected scope pass validation.
RevenueBug imports store orders, successful refunds, and lost disputes into daily revenue history.
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: one Blink 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: Blink does not document a read-only key. Store-wide revenue can include multiple products, and the key is stored encrypted.
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.