Markerra FAQ: mobile app, QR/NFC, rewards, and reports.

Markerra is a technology production service: a dedicated mobile app, backend, physical QR/NFC points, progress rules, reward screen, and aggregated reporting. The client can use the system in its own deployment or another project.

Markerra donates 5% of income from its projects to help shelter cats in need. This is Markerra's own commitment and is independent of the technical scope of the client's deployment.

Markerra produces the mobile app and backend and implements the supplied rules, QR/NFC marker flow, reward screen, and aggregated reporting. The client supplies the concept, rules, content, branding, and reward and independently handles strategy, creative, communication, media, distribution, project organization, marker locations, and reward fulfillment.

Markerra does not provide internet advertising, media buying, retargeting, remarketing, programmatic advertising, DSP/SSP/ad network services, ad targeting, advertising audience creation, or audience export to advertising platforms.

Markerra does not implement advertising platform SDKs, pixels, tags, containers, or server-to-server events in the app for ad conversion measurement, attribution, retargeting, remarketing, ad targeting, or audience export.

No. A QR code or NFC tag is only the physical entry point to a checkpoint. The real value is the dedicated 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.

Yes. A deployment can start in a limited scope — for example one venue or one event, a fixed number of points, and a set duration — to technically validate the scenario before a full rollout. If that is what you need, mention it in the inquiry form.

No. Location can be used while the map is open or at scan time if the deployment 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 deployment should confirm physical presence. The radius and tolerance must match real GPS conditions, especially in cities and indoor locations.

The client is responsible for legal and safe marker placement, location permissions, maintaining points during the deployment, and removing them after it ends unless the agreed scope says otherwise.

Markerra can supply ready-to-use QR codes and NFC tags with configuration and instructions. Before shipping, we agree the format and confirm the required labeling and documents. The client selects the location, secures permission, and handles safe installation and field operations unless the order also includes installation.

No. Markerra does not run advertising campaigns, buy media, or manage ads in systems such as Google Ads, Meta Ads, TikTok Ads, or DSPs. We provide the app, QR/NFC mechanic, reward handling, and aggregated reporting. The client manages activation communication independently.

No. Markerra does not create advertising segments, run retargeting or remarketing, or export audiences to advertising platforms. The app is used to join a game or QR/NFC activation and to issue a reward after deployment conditions are met.

The client decides where to place markers, obtains location permissions, communicates the activation, and fulfills the reward. Markerra remains responsible for the agreed app scope and preparation of the supplied markers.

We do not integrate the Markerra app with advertising platforms for ad conversion measurement, attribution, targeting, remarketing, retargeting, or audience export. Any integrations are limited to technical activation handling, such as reward fulfillment, discount code delivery, or basic aggregated reporting.

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 deployment rules, not a random draw.

The client receives an aggregated report, for example scan counts, started and completed games, and issued rewards. The report does not contain user lists, raw identifiers, raw location data, or advertising segments.

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 simpler than a deployment with many locations, geofence rules, and a custom finale. The client should prepare the concept, rules, content, locations, and reward first.

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 experience before discussing a client deployment.

The most useful inputs are deployment goal, activation type, expected participant scale, location list, planned marker count, reward, and timing. If the deployment uses geofence checks, exact point locations are needed, not only a building address.