What are the advantages of using the Beaconinside SDK?

The Beaconinside Proximity DMP is a turnkey solution for all your proximity needs. It's vendor-agnostic and provides open APIs to get all your data in and out. Several years of development effort went into building the Proximity DMP. It's used in hundreds of applications and is a production-ready platform that will be continuously extended.

The Beaconinside SDK is a key component to efficiently scan for beacons and geofences and to ensure that proximity events (e.g. exiting a store) are sent at the right moment. Beacon diagnostics and status alerts also require the SDK. The integration effort is only a few hours including testing and saves hundreds of in-house development hours. The pricing for the SDK usage is based on monthly active users (MAUs) and number of monitored locations.

In some special cases (e.g. infrastructure owners) only the beacon management backend is required and via APIs the beacon IDs and meta data is shared across mobile apps.

Frequently Asked Questions

Why should I use the Beaconinside SDK?

It's primarily a question of what features do you want to use. Beacon diagnostics, secure beacon advertising, advanced visitor analytics and dashboards, real-time webhooks and proximity campaigns all rely on an SDK integration.

Can multiple proximity SDKs work in parallel?

Yes, this is possible to monitor for your own scan events but you should ensure that it's done in a battery-efficient way. The Beaconinside SDK also exposes raw scan events, enriched with beacon meta data, that can be used as well. On iOS you have to ensure that you are not using too many CoreLocation Region Monitoring slots. The Beaconinside SDK needs at least 1 slot.

Are there side effects to other SDKs?

No, there shouldn't be side effects. The Beaconinside SDK is developed to work well with the most common mobile service providers like Adjust, Webtrekk, Adobe Omniture, Google Analytics, TUNE and many more. The Integrated Partner Network also ensures compatibility with these 3rd-party service providers on the client and backend side.