Absolutely! The goal of the POC is to use an mbox to load profile parameters for authenticated users into Target, then on another device/browser, after authentication, to use those profile parameters to deliver content [specifically populating an ordering widget]. In a use case we would use dynamic values, but for the POC we are great with static.
e.g., of adding the parameters [per https://marketing.adobe.com/resources/help/en_US/target/target/r_target_behavioral_steps.html]
<div class="mboxDefault">
<p>Testing adding profile parameters.</p>
</div>
<script>
mboxCreate('test_profiles', 'profile.eVar45=eVar45', 'profile.origin=DAL', 'profile.destination=NYC', 'profile.dateOut=02/12/2017', 'profile.dateRtn=02/12/2017', 'profile.paxType=ADT', 'profile.promo=flyfree');
</script>
It is my understanding that in Target Classic, we would then use something like following code in the offer order to 'show' the profile parameter values: ${profile.origin}
I am not seeing any values passing however.