Connect Amplitude¶

Amplitude is a traffic calibration source for your AI shoppers. Squoosh reads aggregate event counts for geography and, when available, traffic source and device mix. These counts describe event activity, so frequent visitors can contribute more than occasional visitors.

What the connection does¶

Squoosh reads event segmentation totals for your selected base event. Leaving Base event blank selects Amplitude's Any Active Event, which includes active event occurrences rather than only page views. Geography uses country names. Traffic source uses the referring_domain user property when populated.

An optional Conversion event supplies a raw event count. Squoosh does not turn it into a session conversion rate and Amplitude cannot serve as the property's conversion source. This connector does not fetch a session denominator, even though Amplitude offers separate session reporting APIs.

The connector reads aggregate reports. It does not request individual user profiles, replay recordings or raw user-activity histories, and it does not write events back to Amplitude.

Connect Amplitude¶

You'll need the project's API key and secret key, plus its US or EU region.

In Amplitude, select Organization settings → API Keys, then choose your project. Copy its API key and generate a secret key if needed. Save the secret when generated: Amplitude does not let you retrieve it later. The Key ID is not the secret. See Amplitude's key management guide.

1. Open Integrations in Squoosh and select Connect for Amplitude.
2. Enter the API key and Secret key in their private credential fields.
3. Set Region to us or eu. The default is us.
4. Optionally set Base event to an exact event name, such as [Amplitude] Page Viewed, to limit the traffic reports to that event.
5. Optionally set Conversion event to the event whose occurrence count you want recorded, such as a purchase event.
6. Click Connect. Squoosh verifies the credentials before saving and requests the first snapshot.

What Squoosh reads¶

Small samples are excluded from calibration by the shared minimum-sample rules. Recognized device labels are inferred into categories; unsupported labels are dropped. Amplitude defines OS as a name combined with a version, including browser information for web traffic. A replacement device mapping still needs validation. See Amplitude's property definitions.

Limits and caveats¶

• Rate limits are shared by project. Amplitude limits concurrency and query cost. Wide windows or repeated refreshes can return a rate-limit error; retrying immediately may fail again. Squoosh does not currently coordinate a cost budget across connections to the same project. See Dashboard REST limits.
• Date boundaries can differ. Squoosh builds date strings in UTC; Amplitude interprets them in the project time zone. Near midnight, the selected boundary date can differ from the project's current date. The existing calculation also assumes both endpoints are inclusive, which the reference does not explicitly guarantee.
• Grouped reports have a ceiling. Squoosh requests up to 1,000 group values. Reaching that ceiling marks the dimension as potentially truncated. Raw referring domains can reach the cap even though they later map into only a few channels. Amplitude retains top groups before pruning the remainder. See group-by ordering.
• No session conversion rate. An event count is retained when configured, but it does not ground a conversion rate for AI shoppers.

Troubleshooting¶

Related¶

• AI shoppers
• Connect Google Analytics
• Connect Shopify
• Connect a CSV / Excel import