Connect Adobe Commerce (Magento)¶

Squoosh reads your order count from Magento Open Source or Adobe Commerce on-premises and Cloud infrastructure (PaaS). It does not yet change how your AI shoppers behave. This connection collects order evidence for future use, without inventing a conversion rate.

What the connection does¶

The connection checks access to the same read-only Orders API used for data retrieval. A data read requests the total count of orders created in the last requested number of full UTC days, excluding today, whose current order state is processing or complete. An empty window produces a real count of zero.

Squoosh can also collect an order-weighted distribution of billing countries. These are buyers' order countries, not a distribution of visitors. Orders have no session denominator, so Squoosh does not calculate a conversion rate or use this connection to calibrate shoppers. Connecting this source is optional.

Create integration credentials¶

Use an integration access token, not an administrator username, password, or temporary administrator token.

1. In your Commerce Admin, open System > Extensions > Integrations and choose Add New Integration.
2. On Integration Info, enter a descriptive name, such as Squoosh order read. Complete any fields required by your installation.
3. On the API tab, set Resource Access to Custom. Select Sales > Operations > Orders > Actions > View (Magento_Sales::actions_view). Squoosh does not need write access or access to all resources.
4. Save the integration, then choose Activate > Allow. Copy the Access Token from Integration Tokens for Extensions. The consumer key and secret and the access token secret are not used by this connector.
5. For Commerce 2.4.4 and later, ask your store administrator to open Stores > Configuration > Services > OAuth > Consumer Settings, set Allow OAuth Access Tokens to be used as standalone Bearer tokens to Yes, and save the configuration. This store-wide setting is required by this connector's Bearer authentication. OAuth 1.0a signing is not available here.

An integration token lasts until it is revoked. Deactivating or deleting the integration stops Squoosh's access. See Adobe's integration setup guide and token authentication documentation.

Connect in Squoosh¶

1. Open Integrations and choose Adobe Commerce (Magento).
2. Enter the Store base URL, such as https://shop.example.com. Use your installation's public HTTPS base URL, without /rest/<code>/V1, query parameters, or embedded credentials. Localhost and private network addresses are not accepted.
3. Paste the Integration access token. Squoosh stores it as a secret and sends it only in the Authorization header.
4. Optionally enter the Store view code, such as en_us. The default is all; only letters, digits, and underscores are accepted.
5. For a multi-store installation, enter the numeric Store view ID filter if you want only one store view's orders. Leave it blank to read all stores on the installation. The store view code in the URL does not filter orders by store. Your Commerce administrator can confirm the store view ID. The optional REST discovery endpoint /rest/all/V1/store/storeViews also exposes IDs but requires the separate Stores > Settings > All Stores permission; Squoosh does not call it or require that permission for verification.
6. Choose Connect. Squoosh verifies access using a one-row Orders request. A store with no orders can still verify successfully. Authentication success does not mean this beta connector has been validated for shopper calibration.

What Squoosh reads and never reads¶

Squoosh requests only order IDs, billing country codes, and the total count. It does not request customer names, email addresses, street addresses, phone numbers, payment details, cart contents, products, IP addresses, or device and acquisition-channel data. It does not create, edit, cancel, or refund orders. The stored snapshot contains aggregate counts and warnings, not individual order records.

Limits and caveats¶

• Order counts do not currently affect AI shoppers. No session-based conversion rate is available, and pairing with another source's sessions is not implemented.
• State selection is fixed: processing,complete. Custom order statuses are not used as filter values. Canceled, closed/refunded, on-hold, new, and payment-review states are excluded. The current state is evaluated when data is read, so historical counts may change as orders progress.
• UTC window: creation time is filtered from midnight at the start, inclusive, to today's midnight, exclusive. The UTC filter interpretation still needs comparison with your Admin Orders grid during live validation.
• Geography ceiling: at most 20 pages, normally 300 orders per page (6,000 orders). If Commerce advertises a smaller page-size maximum on the first geography request, Squoosh retries once with that maximum. An unreadable maximum falls back to 20 rows. A smaller page size lowers the number of countries sampled within the same 20-page ceiling.
• Only geography can be truncated. The count comes from a separate total_count request. If the 20-page ceiling is reached while more matches remain, Squoosh flags the geography as truncated. If an unexpectedly short page contradicts the reported total, geography is omitted with an incomplete-read warning; that does not prove a cap was reached.
• Changes during retrieval: if totals change or order IDs repeat across pages, geography is omitted with a warning. The count remains the value from the initial count request. These separate requests are not an atomic snapshot, so undetected changes remain possible.
• Request pace: the connector declares a minimum refresh interval of six hours. This is Squoosh's policy, not a claimed Adobe quota. Store administrators may configure their own API, firewall, and page-size limits. A rate-limited call returns a retryable error without an immediate retry; a valid Retry-After header is shown as seconds in the error message. The shared scheduler does not yet accept a provider-specific delay from this connector.
• Nested field selection remains unverified live. If your installation does not accept the documented nested-field grammar for billing countries, contact support. Squoosh does not silently request full customer addresses as a fallback.

Troubleshooting¶

Related¶

• Connect WooCommerce
• Connect BigCommerce
• Connect a CSV / Excel import
• Adobe REST overview
• Search criteria and pagination
• Selecting response fields
• Order states and statuses