Connect Mixpanel to Power BI

Create a Mixpanel connection in Catchr with the service-account username and secret, Project ID, and the correct US or EU region. Build a Power BI query for Event Name, Event Time, Distinct Id and Insert Id, preview a short range, then import its generated URL with Get data > Web. These are raw event rows, so keep the identifiers needed to investigate deduplication and identity differences.

The current connector exports raw events. It does not import the results of saved Mixpanel funnels, retention reports or boards. You can chart event activity in Power BI, but a funnel needs logic for event order, user identity and conversion windows. Use Mixpanel for those existing analyses or prepare the required calculations before presenting an equivalent dashboard.

Catchr exposes Event Name, Event Time, Distinct Id, Insert Id, Device Id, browser, operating system, location and common referral or UTM properties where present. Other properties remain in Properties Json rather than automatically becoming individual columns. Records lets you count exported rows. The presence of an event property depends on what your tracking implementation sends.

The raw export does not apply the same event deduplication as Mixpanel reports. Compare the same event, project, period and filters, and inspect Event Name, Distinct Id, Event Time and Insert Id when checking duplicates. Counting exported rows can therefore differ from the total shown in a Mixpanel chart. Identity rules and report calculations can create further differences.

You can calculate a distinct count of exported identifiers, but that is not automatically the same as Mixpanel’s resolved user count. Anonymous and identified activity may use different IDs, and identity handling matters when comparing results. Label the metric accurately, apply the same scope and filters, and do not add daily unique counts to estimate monthly unique users.

This Catchr version flattens a fixed set of common properties and retains other values in Properties Json. Refreshing the field list does not automatically expose every custom key. If your report depends on a nested purchase value or product attribute, prepare that property as a usable field in a suitable transformation workflow before promising a chart based on it.

Yes. Add sources such as Google Ads to the same report and use consistent dates and campaign identifiers where available. Mixpanel UTM properties reflect the tracking you send, while ad platforms use their own attribution. Comparing activity and spend is useful, but joining them by date alone does not prove which ad caused an event.

Catchr retains properties outside its fixed columns in Properties Json. In Power Query, parse that JSON and expand the specific keys your report needs, then assign suitable types. Test records where a key is absent or its value changes type. Expanding a property makes it usable in your model; it does not add Mixpanel identity resolution or saved-funnel logic to the exported events.