![]() ![]() Unlike many other Amplitude charts, Pathfinder requires you to choose a specific event that is instrumented in Amplitude choosing Any Event is not supported. ![]() Select the starting (or ending) event.To view the events users take before a given event, select ending with from the Paths within sessions dropdown menu.To view the actions or events users take after a given event, select starting with from the Paths within sessions dropdown menu.In the Events Module, decide whether you want your path to start with a specific event, or end with one:.To build your own Pathfinder chart, follow these steps: If you don't, your product's path views won't be accurate. This means that if you're sending Amplitude events via the HTTP API or through another pipeline, you must send a session_id with the event. You should also keep in mind that all paths in Pathfinder are tracked in individual sessions. You'll also want to read up on session IDs and how Amplitude tracks sessions, where you'll also find instructions on setting custom session properties. You should also familiarize yourself with our helpful list of Amplitude definitions. Before you beginīe sure to read our article on building charts in Amplitude, as this is where you'll learn the basics of Amplitude's user interface. We recommend using Pathfinder to see the top common paths users can take to conversion, then use this information to build out your funnel chart. You can view both outgoing and incoming paths to a specified event, and Pathfinder will show you paths of up to fifty steps in depth. Pathfinder shows all the events (also called nodes) users fire in your product, and the sequences of those events (also called paths) that users take during a specified time, measured by event totals. Compare properties of events in your users' pathsĪmplitude's Pathfinder chart lets you explore aggregated user flows within your product.Analyze the top paths users take before or after a specific event.Discover the paths users most frequently take through your product. ![]()
0 Comments
Leave a Reply. |