router/index.js assumes a load-session successful response should always go to heritage. This may have been true in the initial version of NextGen but now we can load and direct it to the correct page. The incorrect routing to heritage was also failing here for returning users that already had a NextGen cookie. The error caused us to route to the beginning.
Fixed that error by removing the default true in the navigateToHeritageFunnel and changing all calls to pass a true or false.
a3dff865ea