Some publishers have existing consent flows on their non-AMP pages that they'd like to use for AMP as well.
Possible options:

1. Use a way to iframe and message communication between the iframe and the AMP page, so consent status is available to the AMP page
2. Send user using links in amp-consent to the non-AMP page but have the ability to direct the user back to the AMP page (even when AMP page is in the viewer) once the user is done with the consent flow on the non-AMP page. It's also important to get consent status from the non-AMP flow channeled back to the AMP page.

CC @lannka @rudygalfi

Master Issue: #13716