I modified the numberGuess sample to simulate the senario of a wizard, that is, click a button to display a new page, but the there is no conversationId parameter displayed in the new page's url.
I add a button in the numberGuess form:
<h:commandButton type="submit" value="Interval" action="interval" />
<start-page name="displayGuess" view-id="/numberGuess.jsp"> .... <transition name="interval" to="toInterval" /> </start-page> ... <page name="toInterval" view-id="/interval.jsp"> <transition name="back" to="displayGuess"/> </page>
JSF actions use a POST, and the conversation is automatically propagated with that data. The only time time you need the conversationId in the URL is when you do a GET. (if you redirect after a POST, then the redirect filter will add the conversationId for the GET that follows, so that might be why you are thinking you should need it)