Automated Fiverr Gig Performance Reports
Every Monday, WebRun signs into Fiverr, opens your seller analytics, captures impressions, clicks, orders, conversion and cancellation rate for every active gig, appends the week to your Airtable history base, and posts a Telegram scorecard showing which gigs gained and which slipped against the four week average.
How do I track how my Fiverr gigs are performing each week?
Every Monday WebRun opens your Fiverr seller analytics, reads impressions, clicks, orders and cancellation rate for each gig, and logs the week into Airtable. It posts a Telegram scorecard showing which gigs gained and which slipped, so you know what to rewrite before it costs you work.
- A slipping gig is spotted in week one, not month three
- Every week of gig data is kept instead of vanishing from the dashboard
- Zero impression gigs are caught before they cost you orders
Built for Fiverr sellers · freelancers · small agencies · service providers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.fiverr.comin a real browser with your saved login - no setup, no API keys. -
1
Fiverr - read gig analytics
fiverr.com
WebRun opens Fiverr to read gig analytics. - Sign into Fiverr and open your seller analytics
- For each active gig, capture impressions, clicks, orders, conversion rate and cancellations for the last 7 days
- Note the gig's current position in its category where that is shown
- Capture your overall response rate, delivery rate and order completion figures
- Read only. Never edit a gig, change a price or reply to a buyer
Done when Every active gig has this week's numbers captured.
-
2
Airtable - log the week's numbers
airtable.com
WebRun opens Airtable to log the week's numbers. - Open your Gig performance base in Airtable and append one row per gig per week
- Fill in week ending date, impressions, clicks, orders, conversion and cancellations
- Calculate the four week rolling average for each gig in its own field
- Tag rows where a metric fell more than your threshold against that average
Done when This week's row exists for every gig with its rolling average calculated.
-
3
Telegram - post the scorecard
telegram.org
WebRun opens Telegram to post the scorecard. - Post a scorecard with one line per gig: impressions, clicks, orders and the change on the rolling average
- Put the biggest faller first, since that is the one worth rewriting
- Show your account level metrics such as response rate and delivery rate underneath
- Flag any gig with zero impressions all week, because that usually means a visibility problem, not a demand one
Done when This week's gig scorecard is posted to Telegram.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it edit my gigs or reply to buyers?
No. WebRun only reads your seller analytics. Editing a gig title, description, price or package, and replying to any buyer message, stays entirely with you.
Why track a rolling average instead of week on week?
Because a single quiet week is normal and a four week average shows real direction. WebRun flags a gig only when it falls below that average by the threshold you set.
What if a gig shows zero impressions?
It is called out at the top of the scorecard. Zero impressions usually points to a visibility or status problem rather than weak demand, so it is worth checking straight away.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.