What Is Free Proximity Marketing Software, and What Does “Free” Actually Cover?

Searches for free proximity marketing software run at a steady volume, and almost nobody who types that phrase is looking for a toy. They are looking for a way to send a message to a phone that is near a particular shelf, gate, ward or stand, without signing a contract before they know whether it works.

That is a reasonable thing to want. It is also a question with a genuinely useful answer, because the components of proximity marketing split cleanly into parts that are free, parts that are cheap, and parts that are neither. This article maps that split, names the technologies properly, and sets out the legal obligations that attach the moment you start detecting a phone, free tier or not.

What is proximity marketing?

Proximity marketing is the delivery of a message to a person’s device based on where that device is, measured at the scale of metres rather than cities. A shopper standing in front of a chiller cabinet gets a different message from a shopper at the entrance.

The distinguishing feature is granularity. Geofencing a whole retail park is location marketing. Detecting that someone has stopped in aisle 7 for forty seconds is proximity marketing, and it needs a different sensing layer to do it.

Four sensing layers do almost all of the work in practice:

Bluetooth Low Energy is defined in the Bluetooth Core Specification maintained by the Bluetooth Special Interest Group, and ultra-wideband ranging is standardised as IEEE 802.15.4z. Those two names matter when you read a vendor’s feature list, because “beacon support” and “UWB support” describe very different accuracy and very different hardware budgets.

What does free proximity marketing software usually include?

Free tiers almost always cover the software layer that is cheap for a vendor to run: a dashboard, a small number of registered transmitters, basic campaign scheduling, and an SDK you embed in your own app. They rarely cover hardware, message volume at scale, or consent infrastructure.

The pattern is consistent because the costs are. Hosting a dashboard for a pilot with three beacons costs a vendor close to nothing. Delivering two million push notifications a month does not. Neither does a support engineer who walks you through why your beacons are being swallowed by a steel mezzanine.

So a free tier is best understood as a technical feasibility test, not a deployment. It answers the question “can my app detect this transmitter and fire an event?” That is worth knowing. It is not the same as knowing whether the campaign works.

What is genuinely free, and what only looks free?

Three things in a proximity marketing stack are free or near-free: the radio protocol itself, the operating-system APIs that read it, and the first few transmitters in most vendors’ trial tiers. Everything else carries a cost, and some of the costs are not money.

Here is the honest division:

The third row is the one that surprises people. Beacons and Wi-Fi sensing only reach a phone through an app that is already installed and has been granted location permission. If you do not have an app with meaningful installed reach at the venue, a free beacon platform has nothing to talk to. The sensing layer is not the hard part. Distribution is.

The permission wall is the real constraint

On iOS, an app must request location authorisation and the user must grant it, and background region monitoring needs the separate always-on grant rather than the while-in-use one. Android splits the same capability across fine location, background location and, since Android 12, a dedicated Bluetooth scan permission that is requested independently of location.

Each of those prompts is a place where users say no. A free tier does not change the conversion rate on a permission dialog, and no amount of campaign tooling recovers a user who declined.

What does the law require before you detect a phone?

If you process data that can identify a person, including device identifiers tied to behaviour, you need a lawful basis, and for marketing messages stored on or read from a device you generally need consent. This is not a feature of the software tier you chose.

Two instruments do most of the work in Europe. Article 6 of the GDPR sets out the lawful bases for processing personal data, and its Article 4(1) defines personal data to include online identifiers. Article 5(3) of the ePrivacy Directive covers storing information on, or gaining access to information already stored in, a user’s terminal equipment. The European Data Protection Board’s Guidelines 01/2025 on the technical scope of Article 5(3), adopted in 2025, address exactly this class of technology, including device-fingerprinting and local-storage techniques used for tracking.

In the United States, the position is state-by-state. The California Consumer Privacy Act, as amended, treats precise geolocation as sensitive personal information, and the California Attorney General’s office publishes the current regulations. The Federal Trade Commission enforces against deceptive data practices under Section 5, which is the mechanism that catches a privacy policy saying one thing while the SDK does another.

The practical reading

Three obligations survive every variation of the above, and they cost engineering time regardless of your software bill:

• A lawful basis, and consent where you are reading from or writing to the device for marketing
• Notice at the point of collection, not buried three taps into a settings screen
• A retention period you can state, and a deletion path you can actually execute

None of those appear on a pricing page. All of them appear in an audit.

What does a proximity pilot actually cost?

The software can be zero. The rest is hardware, installation labour, and the engineering time to wire an SDK into an app you already ship. For a single-floor pilot, the labour usually exceeds the hardware.

A realistic cost structure, with the quantities left to your own site:

Battery life deserves a specific note, because it is where pilots quietly fail. A beacon’s power draw scales with how often it advertises and at what strength. Set the interval aggressively for fast detection and you shorten replacement cycles across every unit you installed. Set it conservatively and a walking shopper may clear the zone before the phone has heard the beacon twice.

Where UWB changes the maths

Ultra-wideband ranging under IEEE 802.15.4z gives you distance measurement in the tens of centimetres rather than the metres-wide uncertainty of BLE signal-strength estimation. That buys genuine precision, and it costs more: UWB anchors are dearer per unit than BLE beacons, and the phone side depends on handsets that carry a UWB radio, which is a subset of the installed base rather than all of it.

If your use case is “which side of a doorway”, BLE is adequate. If it is “which of two adjacent shelves”, it may not be.

How do you evaluate a free tier without wasting a quarter?

Run one zone, with one message, against one measurable outcome, and instrument it before you install anything. A pilot that cannot distinguish “the beacon was not detected” from “the message was ignored” produces a result you cannot act on.

Four questions settle most evaluations:

1. Does the free tier permit the number of zones your pilot needs? Many cap at three to five transmitters, which is enough for a doorway test and not enough for a floor.
2. What happens to your data when the tier ends? Ask whether campaign history and detection logs are exportable, and in what format.
3. Does the SDK work in the background on current iOS and Android? Background region monitoring behaves differently from foreground scanning, and the permission set is different.
4. Is message volume capped, and at what? A pilot that works and then hits a notification ceiling on the first busy weekend has told you nothing about steady state.

Write down what result would make you continue before you start. The pilots that generate clear answers are the ones that defined the answer shape in advance.

When is proximity marketing the wrong tool?

When you do not have app installs at the venue, when the message is not time-and-place sensitive, or when the physical space is small enough that signage does the job better and cheaper. These are common, and worth checking first.

A single-entrance shop with 200 square metres of floor does not need beacon zoning to tell people about an offer. A 40-gate airport terminal, a 90-bed hospital with eight departments, or a 60,000 square metre mall with four anchor tenants is a different problem, because the number of distinguishable places is large and the cost of a person being in the wrong one is high.

Use this as the short decision table:

The honest trade-off: proximity marketing earns its keep where location genuinely changes the right message, and where you have a channel to deliver it. Remove either condition and the free tier is free because it is doing nothing.

If you are weighing a proximity or indoor-location pilot for a specific building, the useful conversation starts with the floor plan, the app you already have, and the zones you actually need to distinguish. Book a scoping call and we will work through what your site requires before anyone quotes hardware.

Frequently asked questions

Is proximity marketing software really available for free?

The software layer often is, in a limited tier: a dashboard, a handful of registered transmitters, and an SDK. What is not free is the beacon hardware, the installation labour, the mobile app the SDK has to live inside, and the legal and engineering work to obtain and record consent. Treat a free tier as a technical feasibility test rather than a deployment plan.

Do I need my own mobile app for proximity marketing?

For BLE beacon campaigns, almost always yes. A beacon broadcasts an identifier, and something on the phone has to recognise it and act. That something is an app with Bluetooth and location permissions granted by the user. NFC tags and QR codes are the exception, because the person initiates the interaction themselves and no background app is required at all.

Does proximity marketing need consent under the GDPR?

Where you store information on or read information from a user’s device for marketing, Article 5(3) of the ePrivacy Directive generally requires consent, and the GDPR requires a lawful basis for processing the resulting personal data. The EDPB’s Guidelines 01/2025 address the technical scope of Article 5(3) directly. Take advice for your own jurisdiction and processing specifics.

Are device identifiers such as MAC addresses personal data?

Article 4(1) of the GDPR defines personal data to include online identifiers, so a device identifier counts whenever it can be linked to an identifiable person, directly or by combining it with other data you hold. The EDPB’s Guidelines 01/2025 treat identifiers read from a user’s terminal equipment as within the scope of Article 5(3). MAC randomisation on modern phones also degrades passive Wi-Fi counting.

Is ultra-wideband worth the extra cost over Bluetooth beacons?

It depends on how precisely you need to locate someone. UWB ranging under IEEE 802.15.4z measures distance by time of flight, giving tens-of-centimetres resolution, against metres of uncertainty for BLE signal-strength estimation. It costs more per anchor and depends on handsets carrying a UWB radio. Choose it when shelf-level or lane-level precision changes the outcome.

How long should a proximity pilot run?

Long enough to cover the venue’s full weekly cycle, including its busiest day, and long enough that detection failures and message-ignored outcomes can be separated in the data. One zone with clean instrumentation beats a whole floor you cannot measure. Define the result that would justify expanding before the first beacon goes up.