Libraries tagged by traffic sources

If your website has static caching on, and you drive traffic to it from social media, Google Ads and other sources that add query string parameters to the URL, there is a chance that each time new user visits a page, it will not be served from cache, but will be generated from scratch. This is because the URL with query string parameters is treated as a different URL from the one without query string parameters.

Go to Download

A Google Analytics 4 reports page for Filament panels: live visitors, KPIs, funnel, events, breakdowns and traffic sources, read through the GA4 Data API with a read-only service account.

Go to Download

A lean WordPress library for HTTP referrer detection and analysis

Go to Download

Per-entry Google Analytics 4 reporting inside the Craft control panel — page views, visitors, sessions, timeline, geography, traffic sources and user journey for any entry with a public URL.

Go to Download

A lightweight Laravel package that adds a middleware to automatically capture and store UTM parameters (like utm_source, utm_medium, utm_campaign) from incoming requests. Makes it easy to track traffic sources across sessions for analytics, marketing attribution, or lead tracking.

Go to Download

First-touch traffic source capture (UTM/referrer/search/AI chat) without external services

Go to Download

Clicky analytics in the Craft control panel: dashboard widgets, a live visitor feed and a Page Stats field for each entry.

Go to Download

Focused web analytics software, with real-time reports about the traffic sources, locations, and technologies used by the visitors.

Go to Download

IP address blocker for Craft CMS applications to bock traffic from malicious sources.

Go to Download

This is an **example** API to demonstrate features of the OpenAPI specification. # Introduction This API definition is intended to to be a good starting point for describing your API in [OpenAPI/Swagger format](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md). It also demonstrates features of the [create-openapi-repo](https://github.com/Redocly/create-openapi-repo) tool and the [Redoc](https://github.com/Redocly/Redoc) documentation engine. Beyond the standard OpenAPI syntax, we use a few [vendor extensions](https://github.com/Redocly/Redoc/blob/master/docs/redoc-vendor-extensions.md). # OpenAPI Specification The goal of The OpenAPI Specification is to define a standard, language-agnostic interface to REST APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code, documentation, or through network traffic inspection. When properly defined via OpenAPI, a consumer can understand and interact with the remote service with a minimal amount of implementation logic. Similar to what interfaces have done for lower-level programming, OpenAPI removes the guesswork in calling the service.

Go to Download