Glossary
Tip: When a page references a term (deeplink, cloaking, SAFE), check here first—most “what does this mean?” questions are answered in one place.
Overview
Section titled “Overview”This glossary defines product vocabulary used across the dashboard and public pages.
Core concepts
Section titled “Core concepts”Link page
Section titled “Link page”A link page is the unit you create in the dashboard: a public landing page with socials, links (buttons), cards, and styling. The UI often shortens this to “link.”
Slug (username)
Section titled “Slug (username)”The slug is the public path segment for your page (sometimes labeled username).
- Length: 3–32 characters
- Allowed:
a-z,A-Z,0-9,_,. - Cannot start or end with
.
Published
Section titled “Published”Published controls whether the page is served to anonymous visitors (together with domain and plan limits). Unpublished pages are not intended for public traffic.
Direct link (directLink)
Section titled “Direct link (directLink)”A direct link is an optional destination URL used for direct navigation flows (for example certain in-app or automation paths). Availability depends on your plan (direct links feature). Direct destination redirects are skipped when the visitor is detected as a bot.
Deeplink (deeplink)
Section titled “Deeplink (deeplink)”When deeplink is enabled, OnLynk may try to open your destination in the user’s regular browser (instead of an in‑app browser), with a fallback to a normal web link if the handoff fails.
Cloaking (cloak, /go/<token>)
Section titled “Cloaking (cloak, /go/<token>)”Cloaking masks the final URL behind an opaque token. Public buttons may point at /go/<cloak>; the server resolves the token and issues a permanent redirect to the real URL. Invalid tokens return 404. Cloaking requires the cloaking plan feature.
Bot detection
Section titled “Bot detection”OnLynk classifies some requests as bots using signals such as User-Agent, Accept-Language, and server-side heuristics (including certain IP ranges). Effects include:
Some traffic may be recognized as automated (previews, crawlers). OnLynk separates it so your analytics stay closer to real human behavior.
- Geo
REDIRECT: redirect not executed for bots (page still loads) - Geo
BLOCK: still returns 404 for bots - Direct link destination redirects avoided for bots
Geo-restrictions
Section titled “Geo-restrictions”Rules that match visitor location can block, redirect externally, or redirect to another OnLynk slug. See Geo-restrictions.
Chatbot
Section titled “Chatbot”A short scripted message sequence (up to three messages) plus optional chatbot link after completion. Requires the chatbot plan feature.
Meta Pixel
Section titled “Meta Pixel”When configured, loads Meta Pixel and emits events such as PageView and Lead on relevant interactions (links, cards, chatbot link).
Analytics event types (reference)
Section titled “Analytics event types (reference)”Aggregated stats and exports may reference:
| Type | Meaning (high level) |
|---|---|
| Views | How many times your page was opened |
| Clicks | How many times people clicked a button/card |
REDIRECT | Redirect-style event (e.g. direct or geo redirect) |
BLOCK | Geo block (404) |
LINK_CLICK / CARD_CLICK | Clicks on buttons or cards |
CHATBOT_CLICK | Chatbot completion / link tap |
If you’re looking for a term used in the UI, it should be listed in the sections below.