Learn when to encode a URL value, why ampersands and spaces matter, and how to avoid encoding the same value twice.
A URL works until you add a search phrase containing spaces or an ampersand. The problem may be that characters intended as data are being interpreted as part of the address structure.
Separate the address from its values
Suppose a search value is tea & coffee. The ampersand has a structural role in query strings, so a component encoder represents that value as tea%20%26%20coffee. You can then use it as a parameter value rather than accidentally creating another parameter.
Component encoding is different from taking a complete URL and encoding every separator. MDN explains the component-encoding behavior used for this kind of task.
Use the tool on the right piece
- Identify the value you need to place inside a URL.
- Open the URL encoder and enter that value.
- Inspect the encoded result.
- Place it into the intended parameter position.
- Open the completed URL and verify the receiving page understands it.
For a generated campaign link, a UTM builder can be simpler than assembling every parameter manually. The right choice depends on whether you are constructing a complete campaign URL or fixing one value.
Watch for double encoding
If an already encoded percent sign is encoded again, the result changes. Do not repeatedly run a value through an encoder just because it looks unfamiliar. Check what the receiving system expects.
The decoder helps inspect encoded text, but decoding does not establish that a destination is trustworthy. Encoding is also not encryption: do not use it to conceal private information in shared URLs.
Try the example in the encoder. For campaign preparation, use the newsletter tracking guide, then create a r37dy account if you need a manageable short address.