runsonwhat

レコードブック Record book's tech stack

What does レコードブック Record book use?

レコードブック Record book (recordbook.jp) uses at least 11 tools we can see from public records, including Google Analytics for analytics and WordPress for its website. Last checked .

Based in
Japan
Re-check liveVisit recordbook.jp
Tools found
11
Categories
5
Layers
3 of 5
Last checked
Oct 2026

レコードブック Record book's stack, layer by layer

Each tool links to the other companies we've found using it. The label says what kind of public trace gave it away.

Application

3 tools, what the product is built with

Frontend

Media & UI

Data & Observability

2 tools, what they measure and store

Analytics

Go-to-market

6 tools, how they find and keep customers

Website & CMS

Ads & Pixels

Companies like レコードブック Record book also use

Tools common among companies with a similar stack that we haven't found at レコードブック Record book.

Companies with a stack like レコードブック Record book's

Ranked by shared tools, with rare tools counting more.

レコードブック Record book tech stack FAQ

What tools does レコードブック Record book use?

We've found 11 tools at レコードブック Record book (recordbook.jp). Application: jQuery, Google Fonts and YouTube. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: WordPress, Google Ads and Meta Pixel. Last checked October 3, 2026.

What analytics tools does レコードブック Record book use?

レコードブック Record book uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

What CMS does レコードブック Record book use?

レコードブック Record book uses WordPress and Yoast SEO for its website. We found WordPress through website code.

Does レコードブック Record book use jQuery?

Yes. We found jQuery at レコードブック Record book through website code. jQuery is used by 668,070 companies we track.

How does runsonwhat know what レコードブック Record book uses?

We read public traces only: レコードブック Record book's DNS and email records, certificate logs, the code its website loads, and published subprocessor lists. A tool is listed only when a direct record backs it up. DNS is rechecked weekly and the website monthly.

We read public traces only: DNS and email records, certificate logs, website code and published subprocessor lists. A tool is listed when a direct record backs it up, and dropped when a recheck no longer finds it. Is this your company? See how to opt out.