On this page
URLs, landing pages & click tracking
Configure generated links and read tracking data correctly.
Destinations and presentation#
The client's URLs section stores destination addresses. Settings controls whether a message landing page is displayed before redirecting. Rewritten links can redirect directly when the landing page is disabled.
URL settings#
| Setting | Effect |
|---|---|
| Generate URL when missing | Append a tracking link to messages without an original URL |
| Custom message content | Text used with generated links |
| Content position | Before or after the generated URL |
| Send only generated URL | Discard other outgoing text when a generated link exists |
| Generated URLs as Unicode | Force UCS-2 for final SMS containing a generated tracking link |
| Auto redirect | 0–600000 milliseconds; 0 means no automatic landing-page redirect |
| Remove URLs | Takes priority and selects traffic without tracking links |
Custom SMS text and generation work independently of the landing-page display switch. URL-only mode requires an actual generated link; it is not a promise to fabricate one without a configured destination.
SSL and DNS#
Use domains under your control. Confirm DNS resolves to the intended service before applying SSL. Client URL actions support validation-file upload, certificate application and removal. Never copy real certificate private keys into public documentation or an example message.
Interpret clicks#
A generated token, a clicked token, a click event and a unique IP are different metrics. The same token can receive repeated clicks. Automated previews and bots can influence counts; use the configured bot and human-challenge controls when investigating.
Retention#
URL_TOKEN_LENGTH controls token length and URL_MAPPING_RETENTION_HOURS controls mapping retention. An expired or missing mapping cannot be repaired merely by increasing the visible report date range.
Screenshots show fictional data from the public demo. Your instance may have different records and permissions.