Connect Plausible¶

Connecting Plausible lets Squoosh shape your AI shopper pool using your recorded device, geography, and traffic-channel mix. Set it up from Integrations.

What the connection does¶

Squoosh reads aggregate unique-visitor counts for device, country, and acquisition channel. It also reads the site's overall unique-visitor total and, if you configure a goal, the number of visitors who completed it. Squoosh does not modify your Plausible site, record events, or request individual visitor records.

Plausible's visitor counts are not session counts. Squoosh therefore does not use this connection as a property's conversion source. You can still run a test without a traffic connection using a general e-commerce mix. See AI shoppers for how calibration works.

Connect Plausible¶

Create a key under the team that owns the site. Select that team in Plausible, open your account settings, go to API Keys → New API Key, choose Stats API, save the key, and confirm Create API Key. The team's plan must include Stats API access, a Business-plan feature on plausible.io. A key cannot query another team's site or a site where its owner only has guest access. See Plausible's authentication guide.

1. In Squoosh's sidebar, click Integrations.
2. In the Plausible row, click Connect.
3. Enter:
4. API key: the key you created. Squoosh keeps it private.
5. Site domain: the exact domain registered in Plausible, such as example.com.
6. API host (optional): your self-hosted instance's base URL. Defaults to https://plausible.io.
7. Conversion goal name (optional): the goal's display name exactly as shown in Plausible. Leave it blank to skip goal counts.
8. Click Connect.

Squoosh verifies the key and site before saving, then reads the calibration data. If Plausible explicitly reports that the named goal is not configured, Squoosh keeps the traffic results, omits the goal figure, and records a warning. Other request failures still fail the read.

What it grounds¶

A dimension needs sufficient traffic before it contributes to calibration. A handful of visitors does not become a fabricated distribution.

Limits and caveats¶

• Visitor basis. Device, geography, and channel counts use unique visitors. A visitor who appears in several buckets may count in each, so a dimension's total can exceed the site's overall unique-visitor total.
• Existing date boundaries. Squoosh sends an inclusive pair of date labels derived from the UTC clock. Plausible interprets those labels in the site's reporting timezone. The end may differ from site-local today by one date, and the range can contain a partial day. It is not a guarantee of complete reporting days.
• Imported history excluded. Queries use the default include.imports=false, so imported GA or CSV history is excluded. See the Stats API reference.
• Reduced channel taxonomy. Organic Shopping and Video join Organic Search. Paid non-social formats join Paid Search. Organic and Paid Social join Social. Affiliates, AI Assistants, and Audio join Referral. SMS and Mobile Push Notifications join Direct. Future unrecognized channel labels use the existing source heuristic.
• Shared request budget. Hosted defaults are 600 requests per hour and 60 requests per 10 seconds. A snapshot uses four requests plus one optional goal request; verification uses one more. Other activity under the same team shares the budget. Self-hosted limits can differ. See Plausible's rate-limit implementation and configuration.
• Self-hosted compatibility. Your instance must serve Stats API v2 at /api/v2/query. Check that endpoint's support on your installed version.

Troubleshooting¶

Related¶

• AI shoppers
• Connect Google Analytics
• Connect Shopify
• Connect a CSV / Excel import
• Plausible device definitions
• Plausible acquisition channels