Bitcoin Forum
May 10, 2024, 09:53:52 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Faucet Owner revenue problem | discussion  (Read 175 times)
Haythem1995 (OP)
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
May 02, 2020, 03:18:14 AM
 #1

I recently created a bitcoin faucet website but i am facing a big problem with the shortlinks :
when i count the number of people that visited the shortlinks i found that it is bigger than the ones counted by the ad network because  some  of these visitors already visited the shortlink from other faucets.

the question is : is there any method that check if the visitor already visited the ad before he access my faucet ? Huh Huh

How to deal with this loss?
1715378032
Hero Member
*
Offline Offline

Posts: 1715378032

View Profile Personal Message (Offline)

Ignore
1715378032
Reply with quote  #2

1715378032
Report to moderator
1715378032
Hero Member
*
Offline Offline

Posts: 1715378032

View Profile Personal Message (Offline)

Ignore
1715378032
Reply with quote  #2

1715378032
Report to moderator
1715378032
Hero Member
*
Offline Offline

Posts: 1715378032

View Profile Personal Message (Offline)

Ignore
1715378032
Reply with quote  #2

1715378032
Report to moderator
"There should not be any signed int. If you've found a signed int somewhere, please tell me (within the next 25 years please) and I'll change it to unsigned int." -- Satoshi
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715378032
Hero Member
*
Offline Offline

Posts: 1715378032

View Profile Personal Message (Offline)

Ignore
1715378032
Reply with quote  #2

1715378032
Report to moderator
hugeblack
Legendary
*
Offline Offline

Activity: 2506
Merit: 3649


Buy/Sell crypto at BestChange


View Profile WWW
May 03, 2020, 02:49:54 PM
 #2

the question is : is there any method that check if the visitor already visited the ad before he access my faucet ? Huh Huh
How to deal with this loss?
You can do this in two ways:

 - Ask the user to access his cookie files: Here you can check whether the user has visited the ads site or not then let him watch and pay.
 - Pay after making sure that the ad has not been seen before: Since the user is forced to create an account in order to use your faucet, you can check whether the user has seen the ad before or not and then deduct that amount from an account before withdrawing.

.BEST..CHANGE.███████████████
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
███████████████
..BUY/ SELL CRYPTO..
examplens
Legendary
*
Online Online

Activity: 3276
Merit: 3172


Crypto Swap Exchange


View Profile WWW
May 03, 2020, 07:50:07 PM
 #3

the question is : is there any method that check if the visitor already visited the ad before he access my faucet ? Huh Huh
How to deal with this loss?
You can do this in two ways:

 - Ask the user to access his cookie files: Here you can check whether the user has visited the ads site or not then let him watch and pay.
 - Pay after making sure that the ad has not been seen before: Since the user is forced to create an account in order to use your faucet, you can check whether the user has seen the ad before or not and then deduct that amount from an account before withdrawing.


the cookie files can be a solution.
Also, they must be sure that "no-counted" visitor does not come from an automated bot script. I guess the ad network has its own way of traffic filtering and they won't count trash clicks.
I think he must make it harder to access automated visits.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
Haythem1995 (OP)
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
May 04, 2020, 01:19:00 AM
 #4

the question is : is there any method that check if the visitor already visited the ad before he access my faucet ? Huh Huh
How to deal with this loss?
You can do this in two ways:

 - Ask the user to access his cookie files: Here you can check whether the user has visited the ads site or not then let him watch and pay.
 - Pay after making sure that the ad has not been seen before: Since the user is forced to create an account in order to use your faucet, you can check whether the user has seen the ad before or not and then deduct that amount from an account before withdrawing.


i will try building a check script that check witch ad networks has been visited by the user  then based on the result i will choose which one he will be sent to thank you my friend it may solve the problem
buwaytress
Legendary
*
Offline Offline

Activity: 2800
Merit: 3446


Join the world-leading crypto sportsbook NOW!


View Profile
May 04, 2020, 12:34:38 PM
 #5

The cookie settings is probably the best workaround, but I won't be surprised if users could find a way to workaround cookies while still getting at your faucet. It's always going to be a problem for non-account sites, but you could do an internal check that sets the faucet only if the user sees enough ads -- which won't happen if he's already seen them.

██
██
██
██
██
██
██
██
██
██
██
██
██
... LIVECASINO.io    Play Live Games with up to 20% cashback!...██
██
██
██
██
██
██
██
██
██
██
██
██
hugeblack
Legendary
*
Offline Offline

Activity: 2506
Merit: 3649


Buy/Sell crypto at BestChange


View Profile WWW
May 04, 2020, 12:40:40 PM
 #6

i will try building a check script that check witch ad networks has been visited by the user  then based on the result i will choose which one he will be sent to thank you my friend it may solve the problem
I don’t know what form your faucet works on, but if you create a separate account for each user, it’s easy to keep track of all things.
You can also visit (Micro Earnings) to find out how other faucets works, and then estimate which method is most appropriate to solve this problem.

Generally, I noticed some grammatical errors, and based on the username, I think you can speak Arabic, if this is correct, you can discuss things in Arabic here --------> https://bitcointalk.org/index.php?board=241.0.
good luck.

.BEST..CHANGE.███████████████
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
███████████████
..BUY/ SELL CRYPTO..
UserU
Hero Member
*****
Offline Offline

Activity: 2030
Merit: 531


FREE passive income eBook @ tinyurl.com/PIA10


View Profile WWW
May 10, 2020, 08:10:09 AM
 #7

One way is to actually redirect users a few times or spam the popups when they click anywhere on the site.

As an end user, I'd loathe this but hey, a man's gotta eat too.

.
.500 CASINO.██

  ▄

.
THE HOTTEST CRYPTO
CASINO & SPORTSBOOK
         ▄▄▄███████████
 ▄▄▄████████████████

▐████████████████████
 ██████████████████
 ▐██████████████████
 ▐█████████████████
  ██████████████████
  ██████▀█████▀█████
  ▐████████████████
  ▐██████████████
   █████████████████
   ▐██████████████████
    ▀██████▀▀▀▀▀▀   ▀▀▀█
▄▄▄▀▀▀▀▀▀▀▄▄▄
▄▄▀▀▄ ▄ ▀ ▀ ▀ ▄ ▄▀▀▄▄
▄▀▄ ▀               ▀ ▄▀▄
█ ▄                     ▄ █
█ ▄  █████  ▄███▄  ▄███▄  ▄ █
█ ▄   ██▄▄   ██ ██  ██ ██   ▄ █
█ ▄   ▀▀▀██  ██ ██  ██ ██   ▄ █
█ ▄   ▄▄ ██  ██ ██  ██ ██   ▄ █
█ ▄  ▀███▀  ▀███▀  ▀███▀  ▄ █
█ ▄                     ▄ █
▀▄ ▀ ▄             ▄ ▀ ▄▀
▀▀▄▄ ▀ ▄ ▄ ▄ ▄ ▀ ▄▄▀▀
▀▀▀▄▄▄▄▄▄▄▀▀▀

▄▄▄██████████▄▄▄
████████▀██▀▀██▄▄
 █
█████████████████▄
 █
████████████████████
  █
██▄████▄███████▄███
  █
████████████████████
  █
███▀████▀███████▀███
 █
████████████████████
 █
█████████████████▀
█████████▄██▄▄██▀▀
 ▀▀▀██████████▀▀▀

ORIGINALS

SLOTS

LIVE GAMES

SPORTSBOOK



.
██..PLAY NOW..
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!