To support a trip with multiple destinations, such as a rideshare pickup
followed by a drop-off, implement each segment of the trip as a separate
Navigation Connect session. The Navigation Connect API tracks a single route to a
single destination and, if you supply more than one waypoint in the launch URL,
Google Maps or Waze displays an error. Each session triggers a billing event as soon as
the trip status becomes `ENROUTE`.

Follow these steps to implement tracking for a trip with multiple destinations:

1. **Generate a unique ID:** To track each segment, generate a unique trip ID
   for every destination along the route.

   > [!WARNING]
   > **Warning:** If your app reuses a trip token or trip ID across separate trips, Navigation Connect returns a `CLIENT_ERROR` status.

2. **Stitch the trip data together:** To group the separate trip updates into a
   single logical job for your dispatch systems, stitch the trip data together
   on your backend by using the unique trip IDs.

   > [!NOTE]
   > **Note:** During an active trip, Navigation Connect only provides data for the current segment. To calculate metrics like total travel time across multiple segments while the trip is in progress, use Navigation Connect for the active segment and augment it with data from the [Routes API](https://developers.google.com/maps/documentation/routes) for the remaining segments.

3. **Prompt the next segment:** To trigger the next Navigation Connect session,
   require the driver to tap the return button to switch back to your app and
   mark the current segment as complete. Then have the driver start the next
   segment by tapping the launch button to navigate in Google Maps or Waze.