Skip to main content

Choose a domain and custom back-half

Available now

Who this is for

This page is for users who want predictable naming before they create many links across campaigns, support operations, or team workspaces.

Before you start

  • Know whether your workspace already has a verified branded domain.
  • Decide whether the link should be generic, campaign-specific, or permanent.
  • Check whether your team already uses a naming standard for slugs.
  • Do not choose 2s.gg for new links, QR codes, pages, or forms. Existing 2s.gg assets continue to work, but new resources should use the current default domain or an active branded domain.
  1. Use the current first-party default domain when speed and simplicity matter more than branding.
  2. Use a custom domain when brand trust, campaign presentation, or client-facing polish matters.
  3. Choose a back-half that is short, readable, and directly tied to the campaign, content, or audience.
  4. Avoid unstable values such as internal ticket ids, temporary draft names, or abbreviations that only one person understands.
  5. Reuse naming conventions across campaigns so future edits, exports, and audits stay readable.

Use it well — Domain and naming best practices

  • A domain decision is partly operational, not only visual. Branded domains often change how stakeholders interpret trust and ownership.
  • Treat 2s.gg as legacy-only. If an old link uses it, leave it in place unless you are intentionally moving the audience to a new URL.
  • Good back-halves reduce errors in live reviews, legal checks, and analytics summaries because the link purpose remains clear even outside the app.
  • If you expect many URLs from the same campaign, move into Campaign Link Factory or Bulk Link Builder instead of manually naming every link.