How to export your MakerWorld analytics

Support Material

How to export your MakerWorld analytics

Creator Center shows you the numbers one model at a time, with no export button. Here's how to pull every model you've published into two spreadsheets in about five minutes.

133,400Impressions

4,100Views

3.07%Click-through

One of my models. MakerWorld gives you the first two numbers and never mentions the third.

That third number is your thumbnail and title doing their job — or not doing it. It's the most useful figure on the whole dashboard and there's no way to see it across your catalogue without pulling the data yourself.

This gets you two files:

makerworld-summary.csv — one row per model. Lifetime totals, click-through rate, conversion rates, traffic sources.
makerworld-daily.csv — one row per model per day. This is the valuable one. Once you have it you can measure any date range you like without ever pulling again.

Before you start

This runs in your own browser, in your own logged-in session, and reads your own analytics — the same data Creator Center already shows you, just all at once. Nothing is sent anywhere and nothing is installed. It won't work on models you don't own.

Three ground rules: don't lower the delay (the script waits 1.5 seconds between models on purpose), don't paste raw API responses in public (the response includes a session block with your account details), and know that this is an internal endpoint rather than a documented API — it works today, it may not work forever.

You'll need desktop Chrome or Edge, and to be logged in to MakerWorld.

Get your design IDs

Go to your public profile at makerworld.com/en/@YOURHANDLE and scroll all the way to the bottom so every model loads. The page loads lazily — skip this and you'll only capture the first dozen.

Open the console with F12, or Ctrl+Shift+J on Windows and Cmd+Option+J on Mac, then click the Console tab. If it refuses to let you paste, type allow pasting and press Enter first — that's a Chrome safety feature and you only do it once.

console

const ids = [...new Set([...document.body.innerHTML.matchAll(/\/models\/(\d+)/g)].map(m => m[1]))];
console.log(ids.length + ' ids found');
console.log(JSON.stringify(ids));

You'll get a count and a list of numbers. Copy that list.

Check the count

Still in the console:

console

console.log(__NEXT_DATA__.props.pageProps.session.user.MWCount.designCount);

That's how many models you've actually published.

Numbers match? Move on.
Found more? The page swept up recommended models from other creators. Harmless — the script logs them as failures and skips them.
Found fewer? You didn't scroll far enough. Reload, scroll to the very bottom, try again.

Run the puller

Paste your ID list into the DESIGN_IDS line near the top, then paste the whole thing into the console and press Enter. Any MakerWorld page works as long as you're logged in.

javascript

/* MakerWorld Analytics Puller
   Paste your design IDs into DESIGN_IDS below, then run in the browser
   console while logged in to MakerWorld. Downloads two CSVs when finished. */

(async () => {
  // ----------------------------- CONFIG -------------------------------------
  const DESIGN_IDS = [];   // <-- PASTE YOUR IDS HERE, e.g. ["3188091","3186519"]

  const START_DATE = '2023-01-01';                        // earlier than your first publish
  const END_DATE   = new Date().toISOString().slice(0, 10);
  const DELAY_MS   = 1500;                                // be polite; don't lower this
  // --------------------------------------------------------------------------

  if (!DESIGN_IDS.length) {
    console.error('DESIGN_IDS is empty. Paste your ID list in first (see Step 1).');
    return;
  }

  const buildId = window.__NEXT_DATA__ && window.__NEXT_DATA__.buildId;
  if (!buildId) {
    console.error('No buildId found. Run this on a makerworld.com page while logged in.');
    return;
  }

  console.log(`Pulling ${DESIGN_IDS.length} models, ${START_DATE} to ${END_DATE}...`);

  const sleep = ms => new Promise(r => setTimeout(r, ms));

  const esc = v => {
    const s = v == null ? '' : String(v);
    return /[",\n\r]/.test(s) ? '"' + s.replace(/"/g, '""') + '"' : s;
  };

  const download = (filename, rows) => {
    const csv = rows.map(r => r.map(esc).join(',')).join('\r\n');
    const blob = new Blob(['\uFEFF' + csv], { type: 'text/csv;charset=utf-8;' });
    const url = URL.createObjectURL(blob);
    const a = Object.assign(document.createElement('a'), { href: url, download: filename });
    document.body.appendChild(a);
    a.click();
    a.remove();
    URL.revokeObjectURL(url);
  };

  const pct = s => {
    if (s == null) return '';
    const n = parseFloat(String(s).replace('%', ''));
    return Number.isFinite(n) ? n : '';
  };

  const fetchModel = async id => {
    const url = `https://makerworld.com/_next/data/${buildId}/en/my/data-overview/model/${id}.json`
              + `?designId=${id}&startDate=${START_DATE}&endDate=${END_DATE}`;
    const res = await fetch(url, { credentials: 'include' });
    if (!res.ok) throw new Error(`HTTP ${res.status}`);
    const json = await res.json();
    const md = json && json.pageProps && json.pageProps.modelData;
    if (!md) throw new Error('no modelData in response');
    return md;
  };

  const summary = [[
    'designId', 'title', 'publishTime',
    'impressions', 'views', 'ctr_pct',
    'downloads', 'prints', 'collects', 'likes', 'followers',
    'view_to_download_pct', 'collect_to_download_pct',
    'points', 'boosts',
    'src_recommend_pct', 'src_search_pct', 'src_browse_pct', 'src_direct_pct', 'src_other_pct'
  ]];

  const daily = [[
    'designId', 'title', 'date',
    'impressions', 'views', 'downloads', 'prints',
    'collects', 'likes', 'followers', 'boosts', 'points'
  ]];

  const failed = [];

  for (let i = 0; i < DESIGN_IDS.length; i++) {
    const id = DESIGN_IDS[i];
    try {
      const md = await fetchModel(id);
      const info = md.designInfo || {};
      const s = md.summary || {};
      const ts = md.trafficSource || {};
      const title = info.title || '';
      const ratio = (a, b) => (b ? +((a / b) * 100).toFixed(2) : '');

      summary.push([
        id, title, info.publishTime || '',
        s.impression, s.view, ratio(s.view, s.impression),
        s.download, s.print, s.collect, s.like, s.follower,
        ratio(s.download, s.view), ratio(s.download, s.collect),
        s.point, s.boost,
        pct(ts.recommend), pct(ts.search), pct(ts.browse), pct(ts.directUrl), pct(ts.others)
      ]);

      for (const d of (md.dateList || [])) {
        daily.push([
          id, title, d.intervalVal,
          d.impression, d.view, d.download, d.print,
          d.collect, d.like, d.follower, d.boost, d.pointFromModel
        ]);
      }

      console.log(`[${i + 1}/${DESIGN_IDS.length}] ${title || id} — ${(md.dateList || []).length} days`);
    } catch (err) {
      console.warn(`[${i + 1}/${DESIGN_IDS.length}] FAILED ${id}: ${err.message}`);
      failed.push(id);
    }

    if (i < DESIGN_IDS.length - 1) await sleep(DELAY_MS);
  }

  console.log(`\nDone. ${summary.length - 1} models, ${daily.length - 1} daily rows.`);
  if (failed.length) console.warn('Failed IDs:', failed);

  download('makerworld-summary.csv', summary);
  await sleep(800);                     // browsers block back-to-back downloads
  download('makerworld-daily.csv', daily);

  window.__mwData = { summary, daily, failed };
})();

You'll see a progress line per model, then two downloads.

What you got

summary.csv

Column	What it means
impressions	Times your model appeared in a feed or search result
views	Times someone clicked through to the page
ctr_pct	views ÷ impressions. Your thumbnail and title's click-through rate
view_to_download_pct	How well the page converts once someone lands on it
collect_to_download_pct	How many people who bookmarked it actually took the file
src_*_pct	Where traffic came from: recommend, search, browse, direct, other

daily.csv

One row per model per day. Days before a model was published show as zeros. Pivot it, filter it, chart it — because it's daily, you can isolate any window after the fact, like a fourteen-day before-and-after around a thumbnail swap, without pulling again.

Why click-through is the number to watch

Raw views are close to useless for measuring a change, because model traffic decays as a listing ages. Compare last month to this month and you're mostly measuring age.

Click-through rate largely sidesteps that. When impressions fall, views fall with them, and the ratio holds. Swap a thumbnail on a six-month-old model and a move from 2.8% to 3.4% is a real signal even if total views barely budge.

It isn't a perfect control — older models likely get worse feed placement, which affects click-through too. For a cleaner read, change one model and leave a similar-age, similar-traffic model alone as a control, then compare both.

Three things to do right now

Back up both CSVs somewhere permanent

This is your baseline. If MakerWorld ever trims historical data or changes this endpoint, the copy you're holding is the only one.

Screenshot every current thumbnail

When you replace one, the old image is gone. You'll want the before and after.

Start a change log

A plain spreadsheet: date, model, what changed, old value, new value. MakerWorld records what happened to your models. It does not record what you did to them. Without a log, in three months you'll have a beautiful dataset and no idea which spikes were your edits and which were the algorithm. This is the step everyone skips, and it's the one that turns numbers into evidence.

Troubleshooting

Unexpected token '<', "<!DOCTYPE"... is not valid JSON

You're not logged in, or you're on the wrong domain. Make sure you're on a makerworld.com page and signed in.

No buildId found

Same cause. Run it on a MakerWorld page, not a blank tab.

Every model fails with HTTP 404

MakerWorld probably changed their internal endpoint. Open Creator Center → Analytics → Model Data, click into a model, open DevTools → Network → Fetch/XHR, clear the log, then change the date range. The request that appears is the current endpoint.

A run of consecutive failures partway through

That's rate limiting, not bad IDs. Stop, wait a few minutes, raise DELAY_MS to 3000, and re-run with just the failed IDs.

Fewer daily rows than expected on some models

Check the publishTime column. If a model predates your START_DATE, move that date earlier and re-run.

The console won't let me paste

Type allow pasting and press Enter, then paste.

Support Material

Explore

Account