science This product or feature is Experimental (pre-GA). Pre-GA products and features might have limited support, and changes to pre-GA products and features might not be compatible with other pre-GA versions. Pre-GA Offerings are covered by the Google Maps Platform Service Specific Terms. For more information, see the launch stage descriptions.
Navigate to multiple destinations
Stay organized with collections
Save and categorize content based on your preferences.
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:
Generate a unique ID: To track each segment, generate a unique trip ID
for every destination along the route.
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.
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2026-06-11 UTC."],[],[]]
