FAQ / setup / ownership
These answers cover the questions that usually appear before a first campaign: how QR and NFC work, when geofence checks make sense, what happens with rewards, what data is reported, and who owns physical marker placement.
Markerra is a campaign kit built around a dedicated app, physical QR/NFC points, progress rules, a reward screen, and post-campaign reporting. Participants collect checkpoints in the app, while the brand receives an aggregated activation summary.
No. A QR code or NFC tag is only the physical entry point to a checkpoint. The real value is the campaign app: goal, map or point list, progress save, rules, finale screen, and reporting.
Yes. The same checkpoint can use both a QR code and an NFC tag linked to the same configuration. Participants choose the easier gesture: camera scan or phone tap when NFC is supported.
Markerra fits activations where the brand wants people to move through real places: a store, mall, event, stand, showroom, partner venue, or city route. It works best when the physical point is part of the experience.
No. Location can be used while the map is open or at scan time if the campaign requires a geofence check. Markerra is not designed for background location tracking.
A geofence checks whether a scan happens within a defined area. We use it when the campaign should confirm physical presence. The radius and tolerance must match real GPS conditions, especially in cities and indoor locations.
The campaign client is responsible for legal and safe marker placement, location permissions, maintaining points during the activation, and removing them after the campaign unless the agreed scope says otherwise.
The standard model is that Markerra delivers technology, configuration, QR/NFC payloads, instructions, and marker materials, while the client or its vendor handles physical production, installation, and field operations.
After the required markers are collected, the app can show a code, link, badge, or redemption instruction. The standard mechanic is deterministic: meeting the condition unlocks the finale described in campaign rules, not a random draw.
The client receives aggregated reporting: campaign entries, collected points, reward completions, and activity insights. We do not share user lists, emails, raw Appwrite identifiers, or raw participant location data.
Yes. Markerra can support one point, several store points, an event route, a mall activation, partner venues, or a city route. More locations require a more detailed brief, testing, and operational plan.
It depends on scale, branding, marker count, and how ready the client materials are. A small pilot is much simpler than a route with many locations, geofence rules, and a custom finale. The best starting point is a brief with places, reward, and goal.
Yes. The demo page shows sample QR codes and the point collection mechanic. It is not a public promotion and does not issue a real reward, but it shows the core app flow before discussing a client campaign.
The most useful inputs are campaign goal, activation type, expected participant scale, location list, planned marker count, reward, and timing. If the campaign uses geofence checks, exact point locations are needed, not only a building address.
