Edge-Engine Redirection Protocol

    Route Campaign Clicks.
    Optimize Every Impression.

    Take full control of your advertising links. Route visitors dynamically by operating system, location criteria, or test multiple landing page weights at the serverless Edge DNS.

    Configure Targeting Rules View Safety Controls
    Linktery Core SystemREADY
    • Redirect Processing time: <12ms
    • Geo-routing rules: Mapped
    • Device redirection: Active
    • Validation bot scanner: Online

    Routing Rules Visualizer

    Select a routing rule parameter below to simulate visitor dispatch paths in real-time.

    Rule Variable Selection

    Inspect visitor's device. Trigger native mobile app store redirection based on OS.

    Visual Redirection FlowACTIVE
    CLICK INApp Store (iOS)Google Play (Android)
    Selected Routing Target URL:

    https://apps.apple.com/us/app/telegram-messenger/id686449807

    Interactive Tool

    Redirect Latency Calculator

    Calculate how redirection delays impact conversion rates and advertising budgets.

    Simulated Redirection Latency280 ms
    15ms (Linktery Edge)500ms (Cloud Foundry)1000ms (Cold Proxy Proxy)
    $
    Visitor Drop-off9.3%
    Bounced Clicks1,868
    Lost Ad Budget$2,802.00
    The Science of Delay

    The Engineering Behind Edge Redirect Latency

    Every millisecond added to your redirection path triggers visitor bounce. When users click an advertising link on Facebook, TikTok, or Google, they expect instantaneous response. If the DNS routing takes 300ms to resolve and dispatch HTTP headers, up to **8.5% of mobile users** click away before your landing page starts loading.

    Traditional redirect proxies route requests through centralized cloud instances (e.g. AWS us-east-1). If your visitor resides in Europe, their request must travel across the Atlantic, execute routing logic, and travel back. This geographic distance adds significant latency.

    Linktery solves this by utilizing globally distributed serverless Edge compute. Redirection logic runs on serverless nodes physically closest to the user (e.g. Frankfurt node for European users), completing processing in under **12 milliseconds**. This guarantees minimal click drop-off and prevents ad budget waste.

    Campaign Protection

    How Ad Reviewer Bots Scan URLs

    Ad platform bots (Google, Meta, TikTok) review landing pages using crawler engines. If your campaign redirects visitors, reviewers must see a compliant page, while human buyers proceed to checkout.

    ASN Registry Lookup

    Google (AS15169), AWS (AS16509), and Meta (AS32934) operate review scrapers from cloud datacenters. We filter requests originating from these IP registries.

    Browser Canvas Challenge

    Headless browser automation environments lack full canvas rendering capabilities. Background JS challenges test device dimensions and WebGL profiles.

    Spoofed UA Inspection

    Scrapers often inject mismatched User-Agent headers (e.g. mobile Chrome header on a desktop Linux host). We run strict format verification.

    Dynamic Dispatch

    Reviewers receive a static, 100% compliant informational layout, keeping advertising accounts healthy, while human buyers proceed to checkouts.

    edge-bot-filter.jsEDGE RUNTIME CODE
    // Check datacenter ASN arrays & automation headers
    export async function onRequest(request) {
      const clientIp = request.headers.get("CF-Connecting-IP");
      const userAgent = request.headers.get("User-Agent");
      const asn = request.cf?.asn;

      // Block Meta (AS32934), Google (AS15169), AWS (AS16509) review bots
      const blockedAsns = [32934, 15169, 16509];
      if (blockedAsns.includes(asn) || userAgent.includes("HeadlessChrome")) {
        // Redirect to clean, static informational page
        return Response.redirect("https://mysite.com/privacy-policy", 302);
      }

      // Check browser attributes for headless engines
      const isAutomation = userAgent.includes("Lighthouse") || userAgent.includes("Googlebot");
      if (isAutomation) {
        return Response.redirect("https://mysite.com/privacy-policy", 302);
      }

      // Real user: Proceed to target conversion link
      return Response.redirect("https://target-destination.com", 302);
    }
    DEPLOYED VIA SERVERLESS FUNCTIONS CLOSEST TO THE CLICK
    Technical Vocabulary

    Redirection & Traffic Glossary

    Essential terminology for high-volume conversion optimization, traffic routing, and tracking security.

    Autonomous System Number (ASN)

    A unique identifier assigned to global networks on the Internet. Datacenters (like Google Cloud, AWS, or DigitalOcean) have specific ASNs, which allow tracking platforms to distinguish cloud servers from real residential internet service providers (ISPs).

    A/B Split Weight

    The percentage distribution of incoming clicks assigned to multiple destination targets. For instance, a 70/30 split weight sends 70% of visitors to Offer A and 30% to Offer B, facilitating conversion testing.

    Subdomain (CNAME) Cloaking

    Mapping a custom domain (e.g. `track.company.com`) via CNAME records to run redirection scripts. Using private custom domains prevents campaign tracking paths from sharing public domain footprints.

    Edge Computing Redirection

    Executing redirect calculations on serverless nodes physically close to the visitor. Edge computing bypasses roundtrip network routing to a central host database, reducing redirection latency to under 12ms.

    FAQ & Redirection Knowledge

    Essential facts about Edge DNS routing, A/B split weights, and traffic protection.

    Deploy Smart Links At the Edge

    Create an account to configure weight-based rotators, geolocation targeting, and device OS redirection rules.

    Configure Smart Links View Pricing