pages: landing, sign in, registration, device activation, subscription selection, payment, and cancellation.

Examples:
"Sign_Up|pageNumber=1|pageType=Landing Page" "Sign_Up|pageNumber=2|pageType=Sign In"

joetesta wrote:

There is insufficient guidance wrt pageNumber or pageType values:
 https://developer.roku.com/en-gb/docs/developer-program/discovery/search/prioritizing-authenticated-channels-in-roku-search.md

Should pages use consistent values for pageNumber (ie should a specific view be assigned a pageNum that's then used consistently for all users, no matter which path they follow to the page; or should the pageNum be incremented arbitrarily as the user steps through the process (such as maintaining a global pageCounter that's incremented on each page in the flow)?

What values may be used for pageType and where does it matter?  Can we create our own arbitrary types?

JD: The idea is to use the provided syntax so the Roku and you can easily identify the page where sign-up abandonments may be occuring...so for page numbering, it should just be based on a single path so that the page can be easily identifed. You don't need to number pages differently based on different user paths. 

Can we create our own arbitrary types?

joetesta wrote:

A challenge I'm facing is that our registration and sign-in flows are non-linear.  The "polling" screen could be screen number 3, 4 or 5 depending on the path and options the user chose.  I wish there were more guidance or an example of how this could work in a more complex / non-linear process.

Is it required that RED calls send incremental page numbers, or could we assign a distinct page number to each of our views and then a user might follow a path with non-sequential pageNumbers?

joetesta wrote:

Types listed do not match example:

pages: landing, sign in, registration, device activation, subscription selection, payment, and cancellation.

Examples:
"Sign_Up|pageNumber=1|pageType=Landing Page" "Sign_Up|pageNumber=2|pageType=Sign In"

Note: "Landing Page" vs "landing"

JD: BTW, I cleaned up the doc based on this feedback, and fixed some rendering issues that were affecting how the samples were displayed.
Can we use any arbitrary values we want for these?  Please clarify in the documentation.
https://developer.roku.com/en-gb/docs/developer-program/discovery/search/prioritizing-authenticated-channels-in-roku-search.md

marcelo.cabral wrote:

DrawObject is also wrong, please review all ifDraw2D interface methods

RokuJonathanD wrote:

joetesta wrote:

Types listed do not match example:

pages: landing, sign in, registration, device activation, subscription selection, payment, and cancellation.

Examples:
"Sign_Up|pageNumber=1|pageType=Landing Page" "Sign_Up|pageNumber=2|pageType=Sign In"

Note: "Landing Page" vs "landing"

JD: BTW, I cleaned up the doc based on this feedback, and fixed some rendering issues that were affecting how the samples were displayed.
Can we use any arbitrary values we want for these?  Please clarify in the documentation.
https://developer.roku.com/en-gb/docs/developer-program/discovery/search/prioritizing-authenticated-channels-in-roku-search.md

RokuJonathanD wrote:

joetesta wrote:

Types listed do not match example:

pages: landing, sign in, registration, device activation, subscription selection, payment, and cancellation.

Examples:
"Sign_Up|pageNumber=1|pageType=Landing Page" "Sign_Up|pageNumber=2|pageType=Sign In"

Note: "Landing Page" vs "landing"

JD: BTW, I cleaned up the doc based on this feedback, and fixed some rendering issues that were affecting how the samples were displayed.
Can we use any arbitrary values we want for these?  Please clarify in the documentation.
https://developer.roku.com/en-gb/docs/developer-program/discovery/search/prioritizing-authenticated-channels-in-roku-search.md