No worries, I think a solid workaround for now would be housing the headphone check in a separate eligibility/screener experiment that gets linked to from prolific, and then linking to our main experiment from there based on a url parameter. That would at least impose that there be no reason to refresh in the main experiment. I’d be interested in hearing more about what’s going on under the hood once you’ve done some testing.
Thanks again,
Nickolas