Mixpanel setup guide

Agents read your numbers and run reports.

Ways to connect

Company admins connect apps, on the Integrations page in Everdeck: open Mixpanel, choose one of the ways below, follow its steps and fill in its fields. Everdeck checks what you enter before it saves anything, and asks you to confirm it’s you (your second factor) before you type any secret. How connecting works.

Service account

Username and password.

1. In Mixpanel, open Organization settings > Service Accounts (https://mixpanel.com/settings/org#serviceaccounts) or Project settings > Service Accounts. You need the Owner or Admin role.
2. Add a service account named "Everdeck", give it access to this project with the Analyst role (Analyst can create annotations; reads also work with less), and optionally set an expiry date.
3. Copy the username and the secret into the form. The secret is shown only once.
4. Copy the project ID from Project settings > Overview (https://mixpanel.com/settings/project). If the project uses data views, also enter the workspace ID of the data view the agent should read.
5. Pick EU or India data residency only if your project is enrolled there; otherwise keep US.

Field	What to enter
Data residency (optional)	Choice: US (mixpanel.com, the default), EU Data Residency (eu.mixpanel.com), India Data Residency (in.mixpanel.com). Starts as https://mixpanel.com/api.
Service account username	Text.
Service account secret	A secret: Everdeck saves it encrypted and never shows it again. Where to find it.
Project ID	Text. For example 1234567. Where to find it.
Data view (workspace) ID, only if the project uses data views (optional)	Text.

Disconnecting deletes the credentials Everdeck saved, but Everdeck can't revoke them: the key, token or password itself keeps working at Mixpanel until you delete or rotate it there.

What agents can do

An agent uses an action only when its charter grants it, on the agent’s Tools tab, where you choose whether each one runs by itself (Auto), asks first or never runs. Each action has a risk tier: tier 3 actions, which customers or the public see, ask first unless you choose otherwise, and tier 4 actions (money, deleting things, access) always need a person. How tools and tiers work.

Actions marked Reads outside content return things people outside your company may have written. Agents treat what they read as information, never as instructions, and their riskier actions later in the same session need approval.

• List event namesTier 0 · ReadReads outside contentmixpanel_list_event_names

  The most common event names in the project over the last 31 days. Use the exact names in other queries.

• List an event's propertiesTier 0 · ReadReads outside contentmixpanel_list_event_properties

  The most common property names on one event and how many events carry each. Use them in on and where expressions, for example properties["plan"].

• Count events over timeTier 0 · ReadReads outside contentmixpanel_get_event_counts

  Totals, unique users or averages for one or more events per minute, hour, day, week or month between two dates (YYYY-MM-DD, project time zone). Unique counts are not available per hour.

• Break down an eventTier 0 · ReadReads outside contentmixpanel_segment_event

  Count one event over time, optionally split by a property (on) and filtered (where), like an Insights report. Expressions look like properties["$browser"] or properties["plan"] == "pro" and properties["amount"] > 100; user properties use user["$email"].

• Read a saved Insights reportTier 0 · ReadReads outside contentmixpanel_query_saved_report

  Get the numbers behind a saved Insights report, as the team sees it in Mixpanel. report_id is the number after "report-" in the report's URL.

• List saved funnelsTier 0 · ReadReads outside contentmixpanel_list_funnels

  The names and IDs of the project's saved funnels.

• Read a funnelTier 0 · ReadReads outside contentmixpanel_get_funnel

  Conversion through a saved funnel between two dates: for each step the count, conversion from the previous step and from the start, and average time to convert, per day, week or month. Optionally split by a property.

• Read retentionTier 0 · ReadReads outside contentmixpanel_get_retention

  How many people come back after a first event: cohorts by start date with counts per later day, week or month. Birth retention starts each person at born_event; compounded counts repeat activity.

• Find user profilesTier 0 · ReadReads outside contentmixpanel_find_profiles

  Look up user profiles by distinct ID, by a where expression on user properties (for example properties["$email"] == "[email protected]"), or by cohort. Returns up to 1,000 profiles per page; pass session_id and page to read further pages.

• List cohortsTier 0 · ReadReads outside contentmixpanel_list_cohorts

  The project's saved cohorts with ID, name, description, size and creation date. Use an ID with find_profiles to list members.

• List annotationsTier 0 · ReadReads outside contentmixpanel_list_annotations

  Notes on the project's charts (releases, campaigns, incidents) between two dates. Use them to explain changes.

• Annotate a dateTier 2 · ReversibleReads outside contentmixpanel_create_annotation

  Add a note at a date and time on the project's charts, for example "Pricing page redesign shipped". Everyone in the project sees it.

Testing, problems and disconnecting

Everdeck checks the connection when you save it. On the connection’s page in Integrations, Test checks it again at any time.

If Mixpanel later refuses the connection, for example because a key was deleted or a sign-in expired, the connection shows Needs attention on the Integrations page and the people who manage connections are told. Agents can’t use it until a company admin fixes it with Edit.

To stop agents using Mixpanel, open the connection and select Disconnect. Agents stop using it at once and its saved credentials are deleted. What else happens depends on how it was connected: each way above says.