How Do Zip Submit Scrubs Work?

Status
Not open for further replies.
T

Trademark

Copywriter / Author
Jun 30, 2007
613
21
0
I understand how the e-mail submit scrubs work.
Obviously, if the e-mail is in the merchant's db,
they get scrubbed out (if the merchant scrubs).
One person... one e-mail... that's fair.

But, I don't understand how zip submit scrubs work.

Here's what I mean...

Let's say I live in a city with 50,000 people. The
city has one zip code. Someone from my city has
already seen the merchant's offer and filled the
zip submit.

Am I right in thinking that if I send any of those
50,000 people to the merchant, they can get
scrubbed just because they're in the same zip
as the guy in my city who has already filled in the
zip submit?

Even if the merchant is cross-referencing the zip
and IP, it's not much better. I use Time Warner for
my cable and they service everyone in my city.
Same service, same zip, same IP.

If you know the answer, chime in.

If you just want to speculate or bitch about how
things should or shouldn't be, that's no use to me
(though others may find it entertaining).

If mkrongel is around and has a moment, it'd be a
real treat to get the scoop from him.
 


I think that the only way the merchants scrub zip submits is if multiple submits derive from a single IP. Zip codes aren't unique, so they can't scrub one once someone has submitted it.
 
Trademark said:
I use Time Warner for my cable and they service everyone in my city. Same service, same zip, same IP.
Click to expand...
Um, not everyone has the same IP on Time Warner in your city. You have your own IP, your neighbor has his own IP, etc.
 
Mike, thanks for the information.

I feel like an idiot for not thinking it through properly.
But, I'm on track now after reading your post.

Thanks.
 
I have heard of cool security that people are starting to implement to curtail fraud and multiple submissions. Some merchants/advertisers are implementing device security, meaning that they log your decide ID and if they see the same device submitting leads over and over through multiple IP's etc.. they automatically flag the account as fraud since the same machine is doing all the submissions. This type of security has been around a long time and used in financial institutions mostly. Itll be interesting to see if it rolls out big in AM
 
Interesting.

It makes sense that this would be implemented in spaces
with a lot of money flowing. Now that you mention it, it
seems odd that it hasn't been opened wide in the one-field
submit space yet.

I hope merchants/networks roll this out for the one-field
submits (I don't do a lot of volume with one-fields yet).
Getting rid of the fraudulent submits would allow the
merchants to back-end 'em with a higher ROI.

Being optimistic by nature, I'd hope that would filter to
higher payouts for affiliates sending good traffic to the
merchants.
 
Status
Not open for further replies.
Top Bottom