Question about Cloaking Fundamentals

I'm fluent in a handful of programming languages and have loads of experience with distributed architecture/infrastructure and database design. I have a question about cloaking with regard to traffic source landing page approval. I'd like to build a cloaker (not for nefarious purposes so much as protecting intellectual property from traffic source employees).

Am I on the right track here?

1. Detect client IPs from data centers/vpns/proxies using data from provider like Udger.com to eliminate the majority of automated "fetching"
2. Use data from Maxmind, etc, to determine that client IP is most likely mobile or non-business.
3. The hard part: Bait traffic sources into reviewing non-published (highly obfuscated urls, etc) white landing pages as to harvest their client review IPs. I believe some large mainstream paid traffic sources are leasing residential IP blocks from ISPs to get past cloakers, etc. I suspect NOIPFraud does this but I'm not sure.

If you have any tips or feedback on this please let me know. I would be happy to add you to my private contributors list and give you free access, etc.

Oh. Okay.

So basically, you want to determine if its a real visitor or a *special* visitor, then redirect them to different outcomes as required.

I'd do this
- check the user-agent headers to see if its an obvious browser or mobile user (flag appropriately)
- start with a IP database whitelist that you update, those people get fast passed
- then, query another source on the url (more expensive operation)
- determination (maxmind says this, then that.. etc)

Here's an interesting fact, you can build this in almost 100% nginx configuration code, and it'd be fast
- the maxmind part you can do with php, or lua/openresty.

You can also use the 'cloaker' outputs to route the traffic to different ad programs pre-sorted for more $$

There is an article written to detect data center, VPN or proxies in PHP. You can use it block traffics easily.

https://blog.ip2location.com/knowledge-base/how-to-detect-data-center-ip-address-ranges/