Dinamik WhatsApp QR Kodu Nasıl Oluşturulur

A dynamic WhatsApp QR code is one of the fastest ways to turn a poster, a receipt or a shop window into a live conversation. Scan, and WhatsApp opens with your number loaded and a message already typed. The catch is that most guides describe how these codes work in a way that is not technically true, and that misunderstanding is what leads people to reprint thousands of flyers.

Here is the honest version. A QR code is a static grid of modules encoding one fixed string. Once printed, that string can never change — nothing about the image is dynamic. What people call a "dynamic QR code" is an ordinary QR code whose encoded string happens to be a short redirect URL you control, so you can change where that URL sends people without touching the printed square.

This guide covers the whole chain: how to build a valid wa.me click-to-chat link, how to put a redirect in front of it so the destination stays editable, where WhatsApp's own Business QR code fits and why it is not dynamic in the redirect sense, and how to measure scans in a way that actually produces data.

What "dynamic" really means for a WhatsApp QR code

The code itself never changes

When you encode https://wa.me/15551234567?text=Hello%20Support%20Team, that entire string is baked into the black-and-white pattern along with its error-correction data. Scan it with any QR code reader and the raw text comes straight back out. There is no server call, no lookup, no version number. So when a vendor advertises an "editable" QR code, the code is not what they are editing — they are editing a database row their redirect service reads at scan time.

Where the dynamic part actually lives

A dynamic setup adds one hop between the scan and WhatsApp:

The QR encodes something short and neutral, for example https://go.yourbrand.com/chat.
Your server (or a third-party redirect service) receives that request, records it, and returns a 302 redirect.
The browser follows the redirect to https://wa.me/15551234567?text=... and WhatsApp opens.

Because the redirect target is an editable value, you can point the same printed code at a different number, message, agent, or a landing page entirely. And because the request passes through infrastructure you control, you finally have something to count. Editability and analytics both come from the redirect, not from the QR.

WhatsApp's own Business QR code is not a dynamic QR code

WhatsApp Business generates a QR code and a matching short link for your account. Meta's business messaging documentation describes these as encoding a randomly generated code in the form https://wa.me/message/<CODE> rather than embedding your number and message directly in the URL. That is a genuinely useful design, and it has one property people mistake for dynamism: the pre-filled greeting attached to the code can be changed or deleted at any time while the code itself stays the same.

That is where the similarity ends. The code always resolves to your WhatsApp account: you cannot repoint it, cannot route scans to a landing page or chatbot flow, and WhatsApp gives you no scan analytics — no counts, devices, locations or per-campaign attribution. Reset the code in the app and the old one stops working, which is exactly the reprint problem a dynamic code is meant to solve.

The accurate summary: WhatsApp's Business QR code has an editable message and a permanent destination, while a dynamic QR code has an editable destination and measurable traffic. They solve different problems, and using WhatsApp's own code on your storefront alongside a redirect-backed code for measured campaigns is a perfectly sensible split.

Static, dynamic and WhatsApp Business QR codes compared

Capability	Static wa.me QR	WhatsApp Business QR	Redirect-backed dynamic QR
What the image encodes	The full wa.me URL, number and message included	A random code at wa.me/message/	A short URL on a domain you control
Change the destination number	No, requires a new code	No, tied to your account	Yes, edit the redirect target
Change the pre-filled message	No, requires a new code	Yes, code stays the same	Yes, edit the redirect target
Scan counts and device data	None	None	Yes, logged at the redirect
Campaign attribution with UTMs	No	No	Yes, on the redirect URL
Works if a vendor disappears	Yes, no dependency	Yes, Meta-hosted	Only if you own the domain
Best fit	One-off signage, personal use	Storefront, profile, packaging	Measured campaigns and long print runs

A static code is not a bad choice. It has zero dependencies, and if the number will never change and you do not need scan data, it is the more robust option.

Build the WhatsApp link the code will point to

Phone number format

Click-to-chat links take the number in full international form with no punctuation: strip the plus sign, the leading zero used for domestic dialling, and any spaces, dashes or brackets. +1 (555) 123-4567 becomes 15551234567, giving https://wa.me/15551234567; a local 0300 1234567 in Pakistan becomes 923001234567. Getting this wrong is the most common reason a link opens WhatsApp and then reports an invalid number.

Pre-filled messages and URL encoding

Append ?text= to load a message into the composer. The message is a URL query value, so every character that is not URL-safe has to be percent-encoded. The equivalent api.whatsapp.com/send?phone=<number>&text=<message> form behaves the same way and is useful when you want the number as a named parameter.

Character	Encoded as	Why it matters
Space	%20	Raw spaces break the URL at the first gap
Line break	%0A	The only way to get multi-line pre-filled text
Ampersand (&)	%26	An unencoded & starts a new query parameter and truncates your message
Question mark (?)	%3F	Safe in most parsers, but encode it to be certain
Hash (#)	%23	An unencoded # turns the rest of the message into a fragment and drops it

Rather than encoding by hand, paste the finished sentence into a URL encoder and drop the result after ?text=; a URL decoder reverses it when you inherit a link and want to read what it says. A WhatsApp link generator assembles number and encoded message in one step, which is fastest if you are producing several variants.

Keep the pre-filled text short — it is a conversation opener, not a form. Remember that the customer can edit it before sending, and often will, so never rely on it arriving intact.

How to create a dynamic WhatsApp QR code

Assemble and test the destination link. Build the wa.me URL with the international number and encoded message, then open it in a phone browser. If WhatsApp opens with the right chat and text, the destination is correct. Fix it here, before anything is printed.
Choose where the redirect will live. A subdomain you own, such as go.yourbrand.com, survives any vendor change. A hosted dynamic-QR platform is faster and gives you a dashboard, at the cost of depending on that vendor for the life of the print run.
Create the short path and point it at the wa.me link. Configure a 302 (temporary) redirect rather than a 301. Browsers and intermediaries cache 301s aggressively, and a cached permanent redirect will keep sending returning scanners to the old destination long after you have changed it.
Add campaign parameters to the short URL, not to wa.me. Give each placement its own path or query string — go.yourbrand.com/chat?utm_source=flyer&utm_medium=print&utm_campaign=holiday — so every scan arrives already labelled. A UTM builder keeps names and casing consistent, which matters because GA4 treats Flyer and flyer as different sources.
Encode the short URL as a QR image. Paste it into a QR code generator and export vector (SVG) for print, PNG for screens. The generator's job ends here: it produces the image, while editability and tracking come from the redirect behind it.
Verify the whole chain before it ships. Scan the printed proof on Android and iOS, and paste the short URL into a URL unshortener to confirm it resolves to exactly the wa.me link you intended, message parameter intact. A URL parser will break the query string into components if you need to inspect it.
Publish, then change the target instead of the code. When the promotion ends, the number changes or a different team takes over enquiries, edit the redirect target. The printed square stays exactly as it is.

Track scans in a way that produces real data

This is where most WhatsApp QR advice goes wrong. Appending UTM parameters directly to a wa.me link does nothing for your analytics: those parameters only become campaign data when a page carrying your Google Analytics tag loads with them in its URL, and wa.me is Meta's domain, where your tag never runs.

There are two places where measurement genuinely works:

At the redirect hop. Every scan hits your short URL before reaching WhatsApp. Log the request server-side, or serve a near-instant interstitial that fires a GA4 event then redirects. This is the only point where scans of a printed code can be counted at all, and it yields totals, timestamps, coarse geography and device type.
At the click, on your own pages. For WhatsApp buttons on your website, a Google Tag Manager "just links" trigger matched against wa.me or api.whatsapp.com fires a GA4 event on click. That covers on-site chat CTAs but tells you nothing about scans of a printed code, which never touch your site.

A workable schema is a single chat_start event with parameters for placement and campaign, so print, packaging and on-site clicks stay comparable in one report. Keep the naming consistent from the first campaign, because GA4 will not merge renamed events for you.

Be honest about the limit: you can measure intent to chat precisely, but you cannot see inside the conversation. Tying a scan to revenue means matching it to a CRM record or order at the other end, usually via a reference the agent captures in the first reply.

Design, size and scan reliability

Scan failures are almost always physical, not technical. The widely used guideline is a distance-to-size ratio of roughly 10:1 — the code about one tenth the width of the intended scanning distance — with roughly 2 cm (0.8 in) square as a practical floor for handheld scanning. A code on a shop window read from three metres away needs to be about 30 cm across, and shrinking it to fit the layout is what breaks it.

Keep the quiet zone. The clear margin around the pattern is part of the code, and cropping it is a common cause of unreadable prints.
Keep contrast high and polarity conventional: dark modules on a light background. Some scanners still fail on inverted, light-on-dark codes.
A centred logo works because QR error correction can reconstruct obscured modules, but the budget is finite. Keep the logo small, and if you cover more than a token area, generate at a higher error-correction level and retest.
Add a short instruction next to the code. A label such as "Scan to chat on WhatsApp" tells people what will happen before they scan, which a bare square does not.
Test the final printed piece, not the screen proof — stock, curvature and low light all behave differently from a monitor.

Where dynamic WhatsApp QR codes earn their keep

Dynamic codes pay off wherever the printed surface outlives the campaign behind it, and they pair naturally with the tactics in our guide to QR codes and WhatsApp for business growth:

Retail: a checkout sticker for feedback, repointed to whichever survey or agent is current.
Restaurants: a table code for WhatsApp orders that switches between lunch and dinner menus without a reprint.
Property: a code on a board that follows the listing to a different agent when territories change.
Packaging: a support code on a box that may sit in a warehouse for a year before a customer scans it — precisely the case where a static number is a liability.
Events and services: one code across signage, badges and handouts, repointed each day or to whichever line is staffed.

The same logic works for digital placements, and it is a practical way to drive traffic to your WhatsApp Business profile from channels that are otherwise impossible to attribute. Auditing what is already in circulation is easier with an extract URL from text tool, which pulls every URL out of a document in one pass.

Security, privacy and vendor risk

A redirect is a small piece of infrastructure with real consequences, so treat it accordingly.

Serve the short URL over HTTPS and use a domain a customer will recognise. An unfamiliar shortener in front of a chat request looks like phishing, and cautious users will not scan it.
Never chain redirects through services you do not control. Each extra hop is another party that sees the request and another point of failure.
Scan logs are personal data in many jurisdictions. IP addresses and approximate location fall under GDPR and comparable regimes, so cover them in your privacy notice and apply the same retention limits you use elsewhere.
Verify your WhatsApp Business account so customers see a business profile rather than an unknown number when the chat opens.
Keep an inventory of which printed asset points at which redirect, and keep the pre-filled message free of anything sensitive — it is visible in the URL, in history and in screenshots.

Several commercial platforms — QRCodeChimp, Uniqode (formerly Beaconstac), QR.io and QR Code Generator PRO among them — package the redirect, dashboard and design tooling together. The trade-off is that your printed codes then depend on that vendor's domain and your subscription staying current. For anything expected to outlive a single campaign, our notes on QR code best practices for WhatsApp Business integration are worth reading alongside any vendor comparison.

Common errors and troubleshooting

Symptom	Cause	Fix
WhatsApp says the number is invalid	Plus sign, leading zero, spaces or dashes in the number	Use the full international number with digits only
Message arrives truncated	An unencoded & or # in the text ended the parameter	Percent-encode the message with a URL encoder
Multi-line message shows on one line	Literal line breaks were used	Replace each break with %0A
Code scans but nothing opens	WhatsApp not installed, or the number has no WhatsApp account	Provide a visible fallback contact next to the code
Old destination still loads after an edit	A 301 redirect cached by the browser	Use a 302 and short cache headers on the redirect
Code will not scan from a poster	Printed below the 10:1 size for the viewing distance, or the quiet zone was cropped	Enlarge the code and restore the clear margin
Dashboard shows zero scans	Tracking was attached to the wa.me link instead of the redirect	Move UTM parameters onto the short URL and log at the redirect

Frequently asked questions

Can a QR code itself actually change?

No. A QR code is a fixed encoding of one string, and printed ink cannot update. A dynamic QR code is a normal QR code encoding a redirect URL; changing what that URL points to changes where scans land, while the pattern stays identical.

Is the QR code in WhatsApp Business a dynamic QR code?

Not in the redirect sense. It encodes a fixed wa.me/message/ code that always resolves to your account. You can edit the pre-filled greeting without the code changing, but you cannot repoint it elsewhere and WhatsApp provides no scan analytics for it.

Will UTM parameters on a wa.me link show up in Google Analytics?

No. UTM parameters are read by an analytics tag when a page loads, and your tag does not run on Meta's wa.me domain. Put the parameters on your own short URL and record the hit at the redirect, or track on-site WhatsApp button clicks as a GA4 event.

Do I need a paid platform to make a dynamic WhatsApp QR code?

No. Any redirect you control will do: a short path on your own domain that 302s to the wa.me link, with server logs as your scan data. Paid platforms buy a dashboard and design tooling, not a different mechanism.

How small can I print a WhatsApp QR code?

Work backwards from the scanning distance using the 10:1 guideline, and treat roughly 2 cm square as the practical floor for handheld scanning. Encoding a short redirect URL rather than a long wa.me link keeps the module count low, which helps at small sizes.

What happens to my printed codes if my QR vendor shuts down?

If the code encodes the vendor's domain, every printed copy breaks and cannot be repaired. This is the main reason to run the redirect on a domain you own for anything with a long shelf life, such as packaging or permanent signage.

The short version

Dynamic WhatsApp QR codes are a redirect trick, not a special kind of QR code, and that distinction is what keeps a campaign flexible instead of fragile. Encode a short URL you control, point it at a properly formatted wa.me link with an encoded pre-filled message, log the hit at the redirect where measurement actually works, and print it at a size the scanning distance justifies. The printed square then becomes an asset you can repoint for years, not a decision you are locked into the moment it goes to press.