Connect Mixpanel

Previous Next

Connect Mixpanel

Mixpanel is a traffic calibration source. Squoosh reads aggregate event counts to shape your AI shoppers' device, geography, and traffic-source mix. These breakdowns are weighted by occurrences of your chosen base event, including repeats. They are not counts of unique visitors or sessions.

Beta

Device categories are inferred from operating systems. Mixpanel supplies no session denominator through this connector, so it does not provide a conversion rate and cannot be selected as a property's conversion source.

Provider API note

This connector uses Mixpanel's Segmentation Query API, which is in maintenance mode. Mixpanel recommends the Insights Query API for new integrations. Switching Squoosh to that API would require a saved report in your project; this connector continues to use Segmentation.

What the connection does

Squoosh requests aggregated breakdowns of your base event and, optionally, the total count of a conversion event. That optional count is recorded on the connection's snapshot. It is never divided by base-event counts to produce a session conversion rate.

The connector does not request individual user profiles, session recordings, or raw event exports. A connection is optional: Squoosh can create AI shoppers from a general e-commerce mix without it.

Connect Mixpanel

You'll need a Mixpanel service account and the project's numeric ID. Use the username and secret from your organization's service accounts, with access to the project you want Squoosh to read.

  1. In the sidebar, click Integrations.
  2. In the Mixpanel row, click Connect.
  3. Enter:
  4. Service account username: the service account's username.
  5. Service account secret: kept private; Squoosh never shows it again after you save it.
  6. Project ID: the numeric ID of the project to read.
  7. Data view workspace ID (optional): the numeric Mixpanel workspace ID for the Data View, when applicable. This is a Mixpanel ID, not your Squoosh workspace ID. See Query API authentication.
  8. Region (optional): us, eu, or in. Defaults to us.
  9. Base event (sessions proxy) (optional): the event used for traffic breakdowns. Despite the field label, its measure is event occurrences. Defaults to $mp_web_page_view.
  10. Conversion event (optional): the exact event name for a purchase or signup. Leave it blank if you do not need that event's aggregate count. It does not enable a conversion rate.
  11. Click Connect.

For the default base event, enable pageview tracking through Mixpanel's JavaScript SDK using track_pageview or Autocapture. Automatic pageview tracking is off by default. You can instead enter an event your project already records. See Mixpanel's pageview tracking setup.

Squoosh checks access with a one-day query before saving. A successful check does not prove that the base event has traffic: an empty response can pass verification. Calibration requires enough recorded events in the selected window.

What it grounds

Dimension Source Notes
Device Operating-system property ($os) Inferred categories. Unknown OS labels are dropped. Web iPads reported as iOS and Android tablets fall into mobile; this is not a reliable tablet split.
Geography mp_country_code Country codes from recorded events.
Traffic source $initial_referring_domain Initial referring domains from the JavaScript SDK. $direct maps to Direct. This does not distinguish paid and organic visits from the same domain.

The shared calibration layer excludes dimensions with too few events instead of treating sparse data as a reliable audience distribution.

Limits and caveats

  • Event counts weight the mix. Repeated base events count repeatedly. Changing the base event changes the measured population.
  • Device mix is inferred. The JavaScript SDK's OS detection does not distinguish web iPads from iPhones by $os. The connection carries a device_inferred_from_os warning.
  • No conversion rate. A configured conversion event supplies only a count. There is no session denominator in this connector.
  • Initial referrers have limited coverage. The default-properties reference lists $initial_referring_domain for JavaScript events. Other SDKs and custom events may not carry it.
  • Date windows include today. Squoosh sends inclusive calendar dates computed in UTC. Mixpanel's segmentation reference does not specify how project timezones affect these dates.
  • Quotas are shared per project. Mixpanel allows 60 queries per hour and five concurrent queries. Each snapshot uses three or four queries. The 15-minute refresh minimum is per Squoosh connection; other connections and tools can still exhaust the project's quota.
  • Breakdowns have a cap. Each sliced query requests up to 10,000 property values. Reaching that limit marks the affected dimension as capped.

Troubleshooting

Problem What to do
Connection fails immediately Confirm the service account username and secret are active, the account can access the project, and the project ID and region match.
Missing Mixpanel project ID Reopen Connect and fill in Project ID.
Project or Data View cannot be accessed Check the project ID and, when applicable, the Mixpanel Data View workspace ID and service account permissions.
Connected but no traffic calibration Confirm the exact base event exists and has traffic in the window. Enable pageview tracking for $mp_web_page_view, or enter an event already recorded in your project.
No conversion rate shows up Expected: Mixpanel supplies event counts through this connector. Choose a source with a real session denominator for conversion-rate calibration.
Rate limited Space out refreshes and check other connections or tools using the same Mixpanel project.
Connect PostHog Connect Amplitude