Blink logoRevenueBug

Turn your Blink revenue into a verified public profile

Publish verified revenue across every product in a connected Blink store. RevenueBug only reads revenue and never shows customer details publicly.

Startups verified via Blink
1
30-day revenue tracked
$170.91
History imported
Up to 2 years
Setup time
About 2 minutes
How it connects

Three steps, read-only from start to finish

  1. 1

    Create a read-only credential

    In Blink, create a dedicated live access token with read-only permissions. Blink docs ↗

    • Live access token with read-only permissions
    • Plus the store ID to publish
  2. 2

    Paste it into RevenueBug

    The credential is encrypted at rest (AES-256-GCM) and only used by the sync worker. RevenueBug validates it and confirms one Blink store before anything is published. You can replace or disconnect it any time from your dashboard.

  3. 3

    Your profile goes live

    RevenueBug imports store orders, successful refunds, and lost disputes into daily revenue history.

    History importedUp to 2 years
    Sync frequencyEvery 6 hours
    Customer data shownNever shown

Top startups verified via Blink

Full leaderboard →
#Startup30-day revenueChange
1Cuewake — Leave it here. Find it when you’re back.SaaS$170.91 68.5%

FAQ

What credential does RevenueBug use for Blink?

RevenueBug uses a live access token with read-only permissions. Use the narrowest read-only permissions the provider supports.

What Blink data is public?

RevenueBug publishes normalized revenue metrics and daily history. It never publishes the provider credential or raw transaction records.

Is the displayed metric always subscription MRR?

No. RevenueBug uses trailing-30-day provider-reported revenue for cross-provider comparison. Review the methodology before treating it as subscription MRR.

How the connection works

During onboarding, you provide a live access token with read-only permissions. 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: Store-wide revenue can include multiple products. The read-only access token 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.

Sources and further reading

Connect Blink in about 2 minutes.

Read-only credential, encrypted at rest. Get a live profile, an embeddable card and a spot on the leaderboard.

Connect Blink →