Each Amevia website connection maps to one public domain pattern. The install snippet is tied to that connection — opening a different hostname in the browser will not show the agent you configured elsewhere.
Match domain to connection
- Open Websites and note the exact domain on the website card
- In the browser, compare protocol, hostname and www vs non-www to that entry
- If you need the agent on staging, add staging as its own website and install there
- After fixing the URL, View Page Source on the correct host and Recheck installation
Typical mismatches
- Connected www.example.com but testing example.com without redirect alignment
- Preview URLs from Vercel or Netlify while production is the connected site
- Shop path on another subdomain that was never added under Websites