Questions: Caching and URL blacklisting/rating about eddystone HOT 2 CLOSED

What shortener are you using?

I have found that the google shortener would not register a hit for every visit. Bit.ly seems to handle this much better.

from eddystone.

We've run a lot more tests in the last couple of weeks with beacons and our own url shortener.

We found that using the same destination URL for 10 beacons leads to different request numbers than say 100 beacons. Whereas we've seen 50 requests/beacon (using 10 beacons), we only see 5 requests/beacon (using 100 beacons).

There seems to be a caching layer involved which is caching more aggressively when using the same URL with more beacons. To verify we generated "unique URLs" by appending query params to the same destination URL and this time the numbers don't change.

I'd like to add here that what we measure is just the Google Indexer hitting our URL shortener endpoint. For actual measurements we recommend using Google Analytics or similar on the destination URL. It is still valuable for us to measure these numbers since they loosely correspond to the foot traffic of a beacon relative to another beacon.

from eddystone.