if the action forces the frame to refresh, you should be able to do it with a 3-page setup:
- page one loads the offer in the frame and sets a counter for the frame refresh
- page two is the offer (loads in the frame)
- page three loads when the counter reaches a value (say 2 if no meta refresh, 3 with meta refresh) and contains the protected content or redirects to the protected content
This is not very elegant for protecting content since page three is available to open in the browser by itself (the link would be public, so you'd better give it a crazy long name). Even worse, if the user refreshes page 2 (the offer) in the browser, it jumps to no 3. Same for doing back/forward in the browser while loading page 2.
It is useful though if you do PPL and know the offer form very well - it can help you use content as an incentive, clean the referrer and by counting the visits on page 3 have a rough idea how many visitors actually completed the offer aka measure the shaving
This is not exactly what you asked, but might give you an idea for a better workaround.