technical layer
App, backend, and checkpoints built to the client’s scenario.
The client identifies the points and supplies the content, rules, and instructions.
Markerra implements them in the app and backend, encodes NFC tags, and generates QR
codes. A checkpoint can represent a training station, instruction zone, or control stage.
The client supplies the concept, rules, content, branding, and reward and independently manages event communication.
Markerra produces and deploys the app, backend, and QR/NFC points; it does not offer strategy, creative,
media, targeting, retargeting, or campaign management or optimization.
control and reporting
The app validates markers; the report describes scan diagnostics.
The app displays the technical status of a specific scan. Markerra handles duplicates,
invalid markers, and optional location checks at scan time. If the
event takes place indoors or in a complex venue, the geofence setup must match real GPS
conditions.
After deployment, the client receives an aggregated report covering starts, scans, checkpoint progress,
completions, and handled rewards. The app can show a code, voucher, benefit, or redemption instruction.
client responsibility
Scenario and materials ready before deployment.
The client hands over the final checkpoint order, screen texts, interface files,
operating instructions, and interface requirements. Markerra agrees the technical parameters,
feasibility, and the way these materials are implemented.
It is also worth preparing on-site support. The team on location should know where the
markers are, what a correct scan looks like, and what to do when NFC or QR fails. Markerra supplies a test
instruction and a technical checklist, while the client is responsible for the physical organization of the space.
Before launch, it is a good idea to run a short test on a real phone, preferably in a
place similar to the target venue. We check whether the QR code is readable in the venue lighting,
whether NFC works with a typical case, and whether the scan status message is unambiguous. Such a test removes
the most common deployment risks: a badly positioned marker, a code that is too small, no internet in
part of the venue, or an unclear technical message.
