Get a weekly Dribbble Pro Analytics report with your top shots

1. Open your Pro Analytics dashboard at dribbble.com/activity and pick 30, 60 or 90 days or All Time.
2. Read the Performance Summary in Pro Analytics: Leads, Project Proposals, Funded Projects, Completed Projects, Average Project Value and Earnings.
3. Check Key Ranking Factors (Response Time, Response Rate, Lead Conversion Rate, Cancellation Rate) and Work in Progress (Active Projects, Open Proposals, Unreleased Funds) on the same Dribbble page.
4. Look at Shot Engagement, which Dribbble shows on the same Pro Analytics dashboard, to see how recent shots did, then copy the numbers into a spreadsheet next to last week's row.
5. The Dribbble help center describes no comparison with the previous period, and the Pro Analytics chart always ends on a partial week that looks like a drop, so the Monday check is easy to misread.

Every Monday, send me my Dribbble Pro Analytics for the last 30 days compared with the 30 days before, plus which shots from the last month got the most saves.

1. 01

   Build a fair comparison

   The agent calls get_pro_analytics for 30d and again for 60d. For counts such as leads, funded projects and earnings, the 60-day figure minus the 30-day one gives the previous 30 days. Rates such as Response Rate or Lead Conversion Rate cannot be subtracted, so the report shows the 30-day and 60-day rates side by side instead.

2. 02

   Run after the daily refresh

   Dribbble updates Pro Analytics once a day, so the Monday run covers activity up to Sunday. The agent says so in the report instead of treating yesterday's silence as a drop.

3. 03

   Point at what hurts ranking

   A Response Rate below the 60-day rate, any Cancellation Rate above zero, or leads without funded projects are named at the top, with the next step: answer open Project Requests, follow up on Open Proposals.

4. 04

   Rank last month's shots fairly

   list_shots gives your shots newest first. The agent keeps those published in the last 30 days, calls get_shot_stats for each, and ranks them by saves per 100 views as well as raw saves, because an older shot always has more views. Stats are totals at the time of the call; when last week's report is in the thread or in your n8n run data, the agent adds the weekly change.

5. 05

   Report, change nothing

   All three tools only read. On an account without Pro, get_pro_analytics returns no figures; the agent says so and still sends the shot ranking.

Pro Analytics, last 30 days (to Sun 11 Oct) vs the 30 days before:
Leads 14 (previous 30 days: 9). Funded Projects 3 (2). Earnings $4,800 ($2,100).
Response Rate 92.9% over 30 days, 97.0% over 60 days: 1 request still unanswered.
Cancellation Rate 0%. Open Proposals: 2, both older than 7 days.
Top shots since 11 Sep: Fintech dashboard, 74 saves from 4,120 views (1.8 per 100).
Onboarding flow, 41 saves from 1,530 views (2.7 per 100), the best save rate this month.

• Dribbble refreshes the Pro Analytics page once a day, so activity from today shows up tomorrow.
• In the Pro Analytics chart Dribbble runs weeks from Monday to Sunday, and the latest week is always partial, so it tends to look like a decline until it ends.
• Dribbble counts Earnings as payouts actually received in the period; money paid for active projects sits in Unreleased Funds until the work is complete.
• Dribbble counts a lead in the period it arrived even if it was later declined, and a Funded Project in the period of its first payment even if it is not fully paid out.
• Dribbble lists client analytics as part of Pro Standard, moved all legacy Pro subscribers to Pro Standard, and uses these numbers, with a focus on recent data, for ranking in Shot Search, Service Search, Designer Search, Popular and New & Noteworthy.

Every tool here only reads, so it can run weekly from n8n, Make, Zapier or cron without waiting for your OK.

Sources: Dribbble Help: Understanding your analytics · Dribbble: Work in Progress, part 14 (Pro tiers) · Dribbble API v2: Shots

curl https://cotlet.dev/api/v1/dribbble/get_pro_analytics \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"period":"60d"}'

{
  "period": "30d",
  "leads": 14,
  "project_proposals": 6,
  "funded_projects": 3,
  "completed_projects": 2,
  "average_project_value": 2400,
  "response_time_hours": 3.5,
  "response_rate": 92.9,
  "lead_conversion_rate": 21.4,
  "cancellation_rate": 0,
  "earnings": 4800,
  "currency": "USD"
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the tool is dribbble_get_pro_analytics. Example data.

• Answer Dribbble Project Requests and client messages
• Dribbble API and MCP server: every tool
• All use cases