Question 1

Create and publish your first QR code

Accepted Answer

Pick the content type, choose dynamic mode unless you have a reason not to, style the code, publish it, then scan the real export with a real phone before it goes anywhere.

Question 2

Static or dynamic: which to choose

Accepted Answer

A static code stores its payload in the matrix itself, so it works forever and can never be changed or measured. A dynamic code stores a managed Mosaqo address, so the destination stays editable and every scan is counted.

Question 3

Test a QR code before you commit to it

Accepted Answer

Test the exported file rather than the preview, on at least two phone models, in the lighting the code will actually live in, and follow the destination all the way to the end of its redirect chain.

Question 4

URL and app link codes

Accepted Answer

A URL code carries a web address. An app link carries a URL that a mobile operating system recognises as belonging to an installed app, and which falls back to the web when the app is missing.

Question 5

Wi-Fi QR codes

Accepted Answer

A Wi-Fi code carries the network name, the security type and the password, and the phone offers to join when it scans. Because the credentials sit inside the matrix, anyone who photographs the code has the password.

Question 6

PDF, vCard and plain text codes

Accepted Answer

A PDF code points at a hosted document, a vCard carries contact details a phone can save directly, and a text code shows a short message with nothing to open. Only the PDF needs a network.

Question 7

Change where a printed code goes

Accepted Answer

Open the dynamic code in your workspace, change its destination and publish the change. The printed matrix is untouched — it points at a managed Mosaqo address, and only what that address serves has changed.

Question 8

How a Mosaqo redirect works

Accepted Answer

The matrix encodes a short Mosaqo address. A scan opens that address, Mosaqo records the scan and answers with a redirect to the current destination, and the phone follows it. Everything you can change lives on the Mosaqo side.

Question 9

Publish, archive and restore a code

Accepted Answer

Publishing makes a dynamic code serve its destination. Archiving stops it serving, without invalidating anything already printed. Restoring and publishing again brings the same printed matrix back to life.

Question 10

Add a logo without breaking the code

Accepted Answer

A QR code carries error correction, and a logo spends it. Keep the logo centred, keep it small relative to the matrix, and re-test after every change — the point where it stops scanning arrives suddenly.

Question 11

Contrast and the quiet zone

Accepted Answer

Modules must be dark on a light background, with real contrast between them, and the code needs an empty margin on all four sides. Inverted codes and crowded margins are the two most common causes of a code that will not read.

Question 12

Frames, calls to action and stickers

Accepted Answer

A bare code on a wall gets fewer scans than the same code with three words under it. Frames and stickers add that instruction — as long as they stay outside the quiet zone.

Question 13

PNG, SVG or PDF: which export to use

Accepted Answer

Use SVG or PDF for anything that will be printed — they are vector, so they stay sharp at any size. Use PNG for screens. A PNG scaled up for a poster is the most common cause of a blurry, unreadable code.

Question 14

How large the code has to be

Accepted Answer

The further away a reader stands, the larger the code has to be. A useful working rule is a tenth of the scanning distance: a code read from a metre wants roughly ten centimetres across, and one on a billboard wants far more than a designer expects.

Question 15

Gloss, curves, fabric and foil

Accepted Answer

Anything that reflects, bends or stretches costs scan attempts. Gloss throws glare, curved packaging distorts the grid, and fabric and foil shift the modules. The fix is more size, more contrast and a physical test — never a bigger logo.

Question 16

Total scans and unique scans

Accepted Answer

Total counts every scan event. Unique counts a device once within the aggregation window. One person scanning three times adds three to the first number and one to the second, which is why the two never match.

Question 17

Why a static code has no analytics

Accepted Answer

A static code stores its payload in the matrix and never contacts Mosaqo, so no scan is ever observed. Analytics require a dynamic code, because only a managed redirect sees the scan happen.

Question 18

CSV export and campaign parameters

Accepted Answer

Export the series as CSV, or read it from the API, when you need the raw rows rather than the dashboard. Campaign parameters on the destination let your own analytics attribute the visit as well.

Question 19

Roles and what each one can do

Accepted Answer

Mosaqo workspaces have five roles — owner, admin, editor, analyst and viewer — running from full control to read-only. Give the narrowest role that lets someone do their job, and reserve owner for the person accountable for the workspace.

Question 20

Invite someone to a workspace

Accepted Answer

Invite by email address and pick the role at the same time. The invitation belongs to that address, so it has to be accepted from the account that owns it.

Question 21

Working in more than one workspace

Accepted Answer

A workspace is the boundary for codes, templates, assets, members and API keys. Separate workspaces keep separate work apart; nothing crosses between them, including keys.

Question 22

Personal and workspace templates

Accepted Answer

A template stores a finished look — colours, logo, frame, module style — so the next code starts approved instead of starting blank. A workspace template is shared with the team; a personal one is not.

Question 23

Brand kit

Accepted Answer

The brand kit holds the colours and logos the workspace is allowed to use, so a code made by someone who has never seen the brand guidelines still comes out on-brand.

Question 24

Managing logos, images and stickers

Accepted Answer

Assets are the logos, images and stickers a workspace reuses. Keeping them in the shared library rather than on individual laptops is what makes templates reproducible.

Question 25

Prepare a CSV for bulk generation

Accepted Answer

Export UTF-8, keep one row per code, keep the header row exactly as expected, and validate a handful of rows before uploading thousands. Most bulk failures are encoding or column problems, not Mosaqo problems.

Question 26

Reading preview and validation errors

Accepted Answer

Validation reports the row and what is wrong with it. Fix the source spreadsheet rather than the exported file, so the correction survives the next export.

Question 27

Re-run a bulk job without duplicating everything

Accepted Answer

Re-running a whole file after a partial failure is how workspaces end up with thousands of duplicates. Re-submit only the failed rows, and use an idempotency key when driving bulk work through the API so a retry cannot double-create.

Question 28

Create an API key and choose its scopes

Accepted Answer

Create the key in the workspace it will act on, grant only the scopes that integration needs, and store it as a secret. A key is shown once — if it is lost, revoke it and issue another rather than hunting for the original.

Question 29

Diagnosing 401, 403, 422 and 429

Accepted Answer

401 means the key was not accepted at all. 403 means it was accepted but the operation is not allowed. 422 means the request was understood and the payload was wrong. 429 means you are over the rate limit and should back off rather than retry immediately.

Question 30

Paging through results and staying inside the limits

Accepted Answer

Listing endpoints page with a cursor rather than an offset, so follow the cursor the response gives you instead of computing one. Watch the rate-limit headers, and use `updatedSince` for polling rather than re-reading everything.

Question 31

Verify a webhook signature

Accepted Answer

Compute the signature over the raw request body, before any JSON parsing, and compare in constant time. Re-serialising the payload changes the bytes, and the signature will then never match.

Question 32

Connecting Make, Zapier and n8n

Accepted Answer

Mosaqo integrates with automation platforms through its HTTP API and webhooks rather than a published marketplace connector. Every one of these tools has a generic HTTP module, and that is what you use.

Question 33

Signed image links for Airtable, Notion and Sheets

Accepted Answer

To display a code image in a tool that only accepts a URL, give it a link the tool can fetch rather than uploading a file by hand. Treat that link as shareable — anyone with it can see the image.

Question 34

Web, mobile and extension: which to use when

Accepted Answer

Do authoring in the web app, where the editor and bulk tools live. Use the mobile apps for scan testing and sharing in the field. Use the Chrome extension for quick codes from the page you are on. All three share one account.

Question 35

Camera permissions and scan testing

Accepted Answer

Scanning needs camera permission from the operating system. If the camera view stays black or never opens, the permission was denied once and has to be granted in system settings rather than in the app.

Question 36

What the Chrome extension stores

Accepted Answer

The extension generates codes from the page you are on. Work you have not saved to a workspace stays in local browser storage, which means it is tied to that browser profile and disappears with it.

Question 37

Check whether the problem is only yours

Accepted Answer

A code that stopped working for everyone at once and a code that fails on one phone need different messages. Five minutes of checking decides which one you are writing, and that decides how fast it gets handled.

Question 38

What to include in a support request

Accepted Answer

Platform and version, the steps you took, the result you expected, the result you got, and the identifier of whatever went wrong. One complete message is answered faster than five short ones, because each round trip costs a working day.

Question 39

How requests are prioritised, and what never to send

Accepted Answer

Priority follows impact and urgency, not wording. And no request should ever carry a password, an access token, an API secret, an `Authorization` header or a private QR payload — not in the message, not in a screenshot, not in an attached log.

How can we help?

Browse by area

Getting started

QR code types

Dynamic codes and redirects

Design and scanability

Printing and export

Scan analytics

Workspace and team

Templates, brand kit and assets

Bulk generation and CSV

Public API

Webhooks and integrations

Mobile apps and Chrome extension

Contacting support

Still stuck?