چۈشەندۈرۈش
Temso captures every request your WordPress origin serves over HTTP and sends it to Temso in the background. No DNS changes, no extra infrastructure — install, paste two values, done.
- Captures all server-side requests — front-end, wp-admin, REST, AJAX, login, xmlrpc. Bot classification happens in Temso.
- Non-blocking, batched delivery — adds no perceptible latency to your pages.
- No cookies, no JavaScript, no client-side tracking.
- Visitor IPs are sent over TLS and hashed in Temso before storage; raw IPs are never retained.
- WordPress Multisite supported (activate and connect per site).
Learn more at temso.ai.
Requests served from full-page cache never reach PHP and therefore can’t be captured by any origin plugin — this is expected and matches the documented CDN-cache limitation.
Privacy
This plugin sends the following per HTTP request that WordPress serves (front-end, wp-admin, REST, AJAX, login, xmlrpc) to the Temso API endpoint you configure: timestamp, request URL, HTTP method, response status, user agent, referer, and the visitor IP address. The IP address is transmitted over TLS and hashed by Temso before storage — it is never stored in raw form, and the plugin sets no cookies and adds no client-side tracking.
ئورنىتىش
- Install and activate the plugin.
- Open Settings Temso.
- Paste the Ingest URL and API key from your Temso project (Crawlers Add source WordPress).
- Make sure Tracking is enabled and save.
FAQ
-
Do I need a Temso account?
-
Yes. The plugin is an interface to the Temso service — create a source under Crawlers Add source WordPress in your Temso project to get the Ingest URL and API key.
-
Why are my counts lower than my own analytics?
-
Requests served from a full-page cache (a caching plugin or a CDN) never reach PHP, so no origin plugin can see them. Temso measures cache misses; expect lower numbers than total traffic.
-
What data leaves my site?
-
Per request: timestamp, URL, HTTP method, response status, user agent, referer, and the visitor IP. The IP is sent over TLS and hashed by Temso before storage — never retained raw. No cookies, no JavaScript, no client-side tracking. See the Privacy section.
-
Does it slow down my site?
-
No. Delivery is batched and non-blocking — the visitor response is never delayed by the upload.
-
Does it work on WordPress Multisite?
-
Yes. Activate and connect it per site; each site uses its own Ingest URL and key.
باھالاشلار
بۇ قىستۇرمىغا تېخى باھا يېزىلمىدى.
تۆھپىكار ۋە ئىجادكار
«Temso AI» نى تىلىڭىزغا تەرجىمە قىلىڭ
ئىجادىيەتكە قىزىقامسىز؟
كودقا كۆز يۈگۈرتۈپ، SVN خەزىنە تەكشۈرۈپ ياكى RSSئارقىلىق ئىجادىيەت خاتىرىسىگە مۇشتەرى بولغىلى بولىدۇ.
ئۆزگىرىش خاتىرىسى
1.0.1
- Fix: fix wordpress deploy
1.0.0
- Fix: enforce release
- Continuous Integration: add manual WordPress.org SVN deploy pipeline
0.4.6
- Fix: add sanitize for the key input in the admin panel
0.4.5
- Fix: point Plugin URI at the GitHub repo to differ from Author URI
0.4.4
- Fix: add Test connection button to verify Ingest URL and API key
- Fix: add Test connection button to verify Ingest URL and API key
0.4.3
- Fix: bump Tested up to 7.0 to match current WP release
0.4.2
- Fix: end wp-org strip markers with
.for WPCS InlineComment rule - Fix: strip self-updater references from the wordpress.org build
0.4.1
- Fix: ready readme.txt for .org review and auto-sync it from release-please
0.4.0
- Packaging: WordPress.org submission readiness — plugin headers, build pipeline, and uninstall flow finalized.
0.3.0
- Captures every server-side request (front-end, wp-admin, REST, AJAX, login, xmlrpc).
- Security hardening: stricter request-header sanitization, HTTPS-only ingest endpoint, bounded delivery buffer.
0.2.0
- Initial public release: request capture with batched, non-blocking background delivery, settings screen, and multisite support.