Connect Adobe Analytics¶
Connecting Adobe Analytics gives Squoosh a source to calibrate your synthetic shoppers against. Squoosh reads your report suite's recorded traffic and shapes the shopper pool to match your real visitors, so experiment results reflect your actual audience. This page covers what the connection does and how to set it up from the Integrations page.
Beta
Adobe Analytics is a newly added connector and has not yet been validated against a live Adobe tenant. It calibrates device, geography, and marketing-channel mix from real visit counts, plus a conversion rate from your report suite's orders metric. Squoosh will not yet use it as an unattended background refresh source — see Limits and caveats.
What the connection does¶
Adobe Analytics is a calibration source. Once connected, Squoosh reads your report suite's visits and builds synthetic shoppers whose mix of device, marketing channel, and geography matches your real visitors — the same role Google Analytics or Shopify Analytics plays. Squoosh also reads your orders metric to ground shopper behavior against.
The connection is not required to run a test — Squoosh can build a pool from a general e-commerce mix without it. For how the calibrated pool behaves and how the match is measured, see Synthetic shoppers.
Before you start¶
Squoosh authenticates with an OAuth Server-to-Server credential — the replacement for Adobe's retired Service Account (JWT) credentials. In the Adobe Developer Console, open (or create) a project, add the Adobe Analytics API, and choose OAuth Server-to-Server as the credential type. Make sure the credential is assigned a product profile that has access to the report suite you want Squoosh to read.
From that credential you'll need the Client ID, the Client Secret, and your Organization ID. You'll also need your global company ID and the report suite ID you want to calibrate from.
Finding your global company ID
It is not the same as your organization ID. Call GET https://analytics.adobe.io/discovery/me with your credential — the response lists each company you can reach along with its globalCompanyId.
Connect Adobe Analytics¶
- In the sidebar, click Integrations.
- In the Adobe Analytics row, click Connect.
- Enter:
- Client ID — from your OAuth Server-to-Server credential.
- Client secret — kept private; Squoosh never shows it again after you save it.
- IMS organization ID — e.g.
1234567890ABCDEF12345678@AdobeOrg. - Global company ID — e.g.
examplecompany0. - Report suite ID — the rsid to read from.
- Conversion metric (optional) — defaults to
metrics/orders. Set it to another metric id (e.g.metrics/event12) if your conversion is tracked as a custom event. - Click Connect.
Squoosh exchanges the credential for a token and runs a live one-day report against the report suite before saving, so a wrong company or report suite is caught immediately rather than on the first sync.
What it grounds¶
| Dimension | Source | Notes |
|---|---|---|
| Device | variables/mobiledevicetype + total visits |
Adobe's mobile device type only classifies mobile hardware — there is no "Desktop" value, because a desktop visit has no mobile device type. Squoosh reads mobile and tablet directly and derives desktop as the remaining visits. Game consoles, media players and e-readers are excluded from the split rather than counted as desktop. |
| Geography | variables/geocountry |
|
| Marketing channel | variables/marketingchannel |
Adobe's default channels map onto Squoosh's channels (Natural Search becomes Organic Search, Referring Domains becomes Referral, and so on). A channel you've renamed or invented is kept as-is rather than forced into a bucket it doesn't belong in. |
| Conversion rate | metrics/orders vs. metrics/visits |
A true visit-based rate. A genuine zero (the metric exists but had no orders this window) is reported honestly, not hidden. |
A dimension needs a reasonable amount of traffic before Squoosh treats it as real signal — a handful of visits doesn't become a fabricated distribution. Below that floor, Squoosh leaves the dimension out of calibration rather than guessing.
Limits and caveats¶
- Marketing Channels must be configured. They come from processing rules you set up in Adobe, not from a built-in taxonomy. If your report suite has none, every visit lands in "No Channel Identified" — Squoosh treats that as no channel signal at all and leaves the dimension out, rather than reporting one 100% bucket.
- Desktop is derived, not measured. See the device row above. If your report suite turns out to enumerate desktop traffic under a mobile device type of its own, the derivation stops making sense — Squoosh detects that and drops the device dimension entirely rather than reporting a mobile-only split.
- No orders metric means no conversion rate. If the report suite has no commerce implementation, Squoosh reports no conversion rate rather than a zero — "we don't measure orders" and "we had zero orders" are different facts.
- Background refresh is off for now. Because the connector has not yet been validated against a live Adobe tenant, Squoosh checks the connection's health on a schedule but will not re-pull calibration data unattended. Reconnect to refresh.
- Squoosh reads reports only. It never writes to your report suite and never reads visitor-level identifiers.
Troubleshooting¶
| Problem | What to do |
|---|---|
| Connection fails immediately with an authentication error | Confirm the Client ID and Client Secret are from an OAuth Server-to-Server credential and haven't been rotated in the Developer Console. |
| "Missing Adobe Analytics company or report suite" | Both Global company ID and Report suite ID are required — reopen Connect and fill them in. |
| A permission error mentioning the report suite | The credential's product profile doesn't include that report suite. Add it in the Adobe Admin Console, then reconnect. |
| A "not found" error | Usually a mistyped global company ID. Re-check it against GET /discovery/me. |
| No conversion rate shows up | Your report suite needs the orders metric (or whichever metric you set as Conversion metric) to be implemented. |
| No traffic-source mix shows up | Marketing Channel processing rules aren't configured in Adobe. Set them up, then reconnect. |
Related¶
- Synthetic shoppers — how the calibrated pool behaves and how the match is read.
- Connect Google Analytics and Connect Shopify — the original calibration sources.
- Connect a CSV import — an alternative if you'd rather export numbers from another tool.