Mixpanel

Runs on its own 12

Looking things up, writing to Everdeck's own records and changes one step can undo. Once an agent's charter grants one of these, it runs without asking, unless you set it to Ask first in the charter or one of your approval rules covers it.

• List event names Tier 0 · Read Outside content

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

• List an event's properties Tier 0 · Read Outside content

  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 time Tier 0 · Read Outside content

  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 event Tier 0 · Read Outside content

  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 report Tier 0 · Read Outside content

  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 funnels Tier 0 · Read Outside content

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

• Read a funnel Tier 0 · Read Outside content

  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 retention Tier 0 · Read Outside content

  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 profiles Tier 0 · Read Outside content

  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 cohorts Tier 0 · Read Outside content

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

• List annotations Tier 0 · Read Outside content

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

• Annotate a date Tier 2 · Reversible Outside content

  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.