Exceptions

Every exception the package throws extends RoundlyConsulting\Plausible\Exceptions\PlausibleException, so one catch handles anything from the client:

use Illuminate\Http\Client\RequestException;
use RoundlyConsulting\Plausible\Enums\Metric;
use RoundlyConsulting\Plausible\Exceptions\PlausibleException;

try {
    $visitors = Plausible::stats()->query()->last7Days()->aggregate()->metric(Metric::Visitors);
} catch (PlausibleException $e) {
    // configuration, visitor, revenue or rate-limit problem raised by the package
} catch (RequestException $e) {
    // Plausible answered with a non-2xx status — $e->response holds it
}

A malformed setting is the one exception from outside this hierarchy: it throws RoundlyConsulting\PackageToolkit\Exceptions\InvalidConfigurationException from the package toolkit, naming the key — an env typo such as PLAUSIBLE_TIMEOUT=five or PLAUSIBLE_STATS_RATELIMIT_PER=hourly. See Configuration.

HTTP failures

HTTP errors are Laravel’s own: a non-2xx response from Plausible throws Illuminate\Http\Client\RequestException — after the rate limiter has recorded any 429 penalty — and a network failure throws Illuminate\Http\Client\ConnectionException. Enable retry.* for transient connection failures.