In the first example, the 1 sets the administrative distance of the route.
By default, the administrative distance of a static route is 1, so normally you wouldn't need to set it.
The track feature allows the route to be conditionally installed in the forwarding table based on the status of the tracked object -- usually an IP SLA monitor or an interface status. If the IP SLA monitor is valid, for example, if an external IP is pingable, the route gets installed in the forwarding table. If it isn't, the route is not installed.
These features can be combined to provide backup routing on the ASA. Imagine you have two interfaces: outside and backup. You want the default route to use the outside interface as long as the next hop is reachable. If it isn't, traffic should use the backup interface. You can configure something like this:
route outside 0.0.0.0 0.0.0.0 126.96.36.199 track 1
route backup 0.0.0.0 0.0.0.0 188.8.131.52 254
sla monitor 1
type echo protocol ipIcmpEcho 184.108.40.206 interface outside
sla monitor schedule 1 life forever start-time now
The monitor pings the next hop address every 10 seconds. As long as it gets a response, the first route is installed in the forwarding table. If the monitor fails, the route is removed.
Note that the second route has an administrative distance of 254. when the first route is valid, it will be installed in the routing table because it has a lower administrative distance compared to the second route. When the route is removed, the second route gets installed. This has the effect of routing traffic to 220.127.116.11 if that address is reachable. Otherwise traffic uses the backup route to 18.104.22.168.
Cisco has a similar example here