Troubleshooting
Situation — What to check Target URL not accepted — Scheme, completeness of the address, length and absence of a link to the service itself. Copy the exact error message. Own ID is busy — Use a different ID; check case and service names. The link doesn't work yet — UTC start time and actual current UTC. Link has ended — End date, counter and limit; Availability of a backup URL. All owner links are unavailable — Status of account freezing and service messages. The correct password does not immediately lead to the site — An OTP, warning or other check may remain. Go through the entire chain in a new session. OTP does not arrive — Email, allowed list, code period, request frequency, Spam folder and mail delivery. Referrer is prohibited — The actual source page and the browser's transmission to the referrer; direct opening may not transmit it. Unexpected target URL is selected — Priorities, inclusion, dates, UTC, empty conditions, weights and up-to-date status information. Compare the scenario in the simulator. One person always sees one A/B option — This is expected if the visitor's technical key is stable. Check different virtual numbers. The new address did not appear after the change — Form saving, active targeting rule, permanent redirect cache and openable short address. QR looks correct but doesn't scan — Contrast, white margins, overlapping blocks, print size, image quality and content mode. Old phone in printed vCard — Contacts are built into the QR itself. Generate and distribute new code. No conversions — Token, actual pixel execution/POST, API response, link state and download blocking. Webhook did not arrive — HTTPS, public handler availability, mode and threshold, inclusion, last delivery error. Fewer notifications than clicks — Interval between messages, exclusion of bots and channel availability. CSV partially imported — Result by line, encoding, separator, dates, 100 line limit and occupied identifiers. No function button — Login, owner access rights and feature availability for the account. Copying is prohibited by the browser — Select the short address and copy it manually or allow access to the clipboard for the site.
To contact support, please prepare a short address, time of the problem with the time zone, action, expected and actual result, error text, language and browser. Do not send passwords, one-time codes or API tokens. The support contact is located in the header of the site.
Publication checklist
• The link has been created in the desired account; the domain and ID correspond to the location.
• The target URL opens and contains the correct UTMs.
• Dates are recalculated in UTC, the limit corresponds to the plan, and the completion of the campaign is provided for.
• For each significant language, device, and time, the rule selection is tested; There is a working default option.
• The comments in the diagnostic report were studied; saved JSON if you need a startup log.
• In the new session, the real password chain, OTP, referrer, warnings and link click are checked.
• The exported QR and proof print are scanned; The link/vCard mode was chosen deliberately.
• Test conversion and webhook are checked where they are needed; messages reached through the selected channels.
• Colleagues were given the necessary rights, the recipient's report was checked without the owner logging in.
• Once published, actual link clicks and the status of the destination URL are tracked; old printed links are not removed without assessing the consequences.
To consistently master these actions, go to Practical course.