Mixpanel events

Three events cover the journey. Break any of them down by id, title or utm.

Event	Sent when	By
deep_link_click	Someone taps a link	The link handler
deep_link_handled	They reach the destination, signed in	The app or website
deep_link_open	An email with the pixel is opened	The API

Test links (ids starting with TEST_) send none of these events. They still open and redirect normally. The email pixel still returns its image.

deep_link_click

• Properties: id, utm, and dynamicParams when data was in the URL.
• User: always deeplink_handler, because the handler does not know who tapped. Count events, not users.
• The handler does not look the link up, so it cannot check which params the link allows. dynamicParams here is everything simple found in data.
• It is sent even if the link is switched off.

deep_link_handled

• Properties: id, title, utm, and dynamicParams (only the ones the link allows).
• User: the signed-in person.
• Not sent when the link is off, deleted, or could not be found.
• For the rest of that visit, every event the app sends also carries deepLinkId and deepLinkTitle, so you can see what people did after arriving.

deep_link_open

• Properties: id, title, utm, and the params the link allows (for example email).
• User: the email param if present, otherwise email_pixel.
• Not sent for off, deleted or unknown links.

Useful questions

Question	How
Which channel works best?	deep_link_handled, break down by utm
How many taps never arrived?	Compare deep_link_click with deep_link_handled
Which campaign?	Break down by title or id
How many emails were opened?	deep_link_open, count distinct email