Smart Link Personalization

Route different visitors to different destinations from the same short link, based on location, device, traffic source, or behavioral segment.

Key concepts

How personalization works

The platform evaluates rules in this order:

1. Link-level routing rules

   Rules set via routingRules on the link are checked first, in priority order.

2. Handle-level personalization rules

   Checked next if no link-level rule matched.

3. Default destination

   The link's base destinationUrl is used if no rules match.

Available conditions

Create personalization rules

    curl -sS -X PUT "https://api.10x.in/v2/handles/{handle}/personalization-rules/{ruleId}" \
      -H "Authorization: Bearer <access-token>" \
      -H "Content-Type: application/json" \
      -d '{"enabled": true, "when": {"countryIn": ["US"], "deviceIn": ["MOBILE"]}, "variant": {"destinationUrl": "https://example.com/us-mobile"}}'

    {
      "enabled": true,
      "when": {
        "countryIn": ["US"],
        "deviceIn": ["MOBILE"]
      },
      "variant": {
        "destinationUrl": "https://example.com/us-mobile"
      }
    }

    curl -sS -X POST "https://api.10x.in/v2/handles/{handle}/links/{slug}/route-preview" \
      -H "Authorization: Bearer <access-token>" \
      -H "Content-Type: application/json" \
      -d '{"country": "US", "device": "MOBILE", "source": "email", "campaign": "spring-launch"}'

    {
      "country": "US",
      "device": "MOBILE",
      "source": "email",
      "campaign": "spring-launch"
    }

    curl -sS "https://api.10x.in/v2/handles/{handle}/analytics?groupBy=segment" \
      -H "Authorization: Bearer <access-token>"

    curl -sS "https://api.10x.in/v2/handles/{handle}/analytics?groupBy=segment&campaignId=spring-launch" \
      -H "Authorization: Bearer <access-token>"

Required auth

Example: geo-targeting workflow

Goal: Route US visitors to a US landing page and everyone else to a global page.

1. Create the link

   Create a link with the global page as the default destination:

   Request

       curl -sS -X PUT "https://api.10x.in/v2/handles/{handle}/links/product" \
         -H "Authorization: Bearer <access-token>" \
         -H "Content-Type: application/json" \
         -d '{"destinationUrl": "https://example.com/global", "title": "Product Page"}'

   Body

       {
         "destinationUrl": "https://example.com/global",
         "title": "Product Page"
       }

2. Add the US variant

   Create a personalization rule for US visitors:

   Request

       curl -sS -X PUT "https://api.10x.in/v2/handles/{handle}/personalization-rules/us-variant" \
         -H "Authorization: Bearer <access-token>" \
         -H "Content-Type: application/json" \
         -d '{"enabled": true, "when": {"countryIn": ["US"]}, "variant": {"destinationUrl": "https://example.com/us"}}'

   Body

       {
         "enabled": true,
         "when": { "countryIn": ["US"] },
         "variant": { "destinationUrl": "https://example.com/us" }
       }

3. Verify with route preview

   Test with a US visitor — expected destination: https://example.com/us.

   Test with a non-US visitor ("country": "DE") — expected destination: https://example.com/global (default).

Personalization layers at a glance