Self-Hosted Gateway Locker: Use Timer or Postback to Unlock?

dingdong

Junior Member
Joined
Dec 20, 2006
Messages
128
Reaction score
19
Content locks. Then user is supposed to complete an offer and receive access to content ("unlocking" of the lock). So this thread is about the best way to unlock the lock. I know of 2 ways: 1) gateway unlocks after fixed X time period regardless of whether the user actually completed an offer or not 2) postback, which means your server is constantly checking with the CPA network's server to see if the user has completed the offer.

What is a better way? What provides better conversion ratios? Better user experience? What's better overall and why?
 
depends what kind of content you are having
and if you are placing any other ads on page or not
if your content can make some $$ then unlock the content after specific time period

if the only source of income is through content lock offer then use postback method
 
Thanks pavan. Anyone else?
 
Instant unlock = instant gratification

Post-back is good if it will take time to gather the content on your end, but for most purposes you won't, unlock after X time (or after survey completion) - thats where its at
 
There's also a third way to consider: pixel fire. Has anyone tested different fixed interval timeouts and see which results in higher conversion?
 
Instant unlock = instant gratification

Post-back is good if it will take time to gather the content on your end, but for most purposes you won't, unlock after X time (or after survey completion) - thats where its at

Not sure what you meant.
 
Anyone else have anything to add to this thread?
 
Time interval method is certainly bad in terms of user experience. I've tried frame load count (count frame number before submit and after submit and close if numbers match) but it fails in cross browser compatibility.

Postback is best option if setup correctly. I know WSM and Maxbounty have decent APIs and verifying offer completion would hardly take few a milliseconds
 
Time interval method is certainly bad in terms of user experience. I've tried frame load count (count frame number before submit and after submit and close if numbers match) but it fails in cross browser compatibility.

Postback is best option if setup correctly. I know WSM and Maxbounty have decent APIs and verifying offer completion would hardly take few a milliseconds

What's WSM?
 
Back
Top