Footfall Attribution reporting without relying on SDK’s
Did you know that Footfall Attribution reporting - based on installed SDK’s - is only possible in the western world?
And did you know that because of the GDPR, Footfall Attribution reporting - when based on installed SDK’s - is technically illegal in Europe?
In one of our recent blogposts we gave a first glimpse at our discovery regarding Footfall Attribution methods and the industries’ reliance on SDK’s. Yes, we dare to call it a discovery. Here is why:
As outlined in our newest whitepaper, Footfall Attribution is hot but has some significant challenges and obstacles to overcome. For starters, proving (or; reporting on) Footfall Attribution - until now - is done based on/and with the help of Software Development Kits installed in apps. Essentially SDK’s can see the location of a device WITHOUT an adrequest won, without an impression served. The phone can literately stay in someones pocket and still a Footfall provider (usually third party data providers or a dedicated location data tool) can ‘see’ what the location of you and your phone is. It is not surprising at all that since the activation of the GDPR in Europa, many Footfall Reporting providers stopped offering this product/solution (in Europe).
Then there is the fact that Footfall Attribution reporting is not possible in many countries of the world. Why? Because the lack of active and usable SDK’s in inventory that is popular within these respective countries.
In this new whitepaper we outline the SDK problem (in terms of the GDPR and the lack of SDK’s installed in apps that represent a large part of a countries’ available inventory). More importantly, we offer a solution to proof Footfall with a method that is GDPR compliant AND can also be activated in countries where Footfall Attribution reporting - right now - is not available.
Reach out if you are interested in this whitepaper.