Websites and Apps
Configurations → Websites and Apps is the control center for the properties CROForge can run on. Everyday meaning: this is the list of websites you have connected. In CROForge, each row is a named domain plus Smart Code, verification, and (when enabled) debug tools.
This is the primary install path. Do not start from Settings → Installation, which is a legacy page in some builds.
Words used on this page
| Word | Everyday meaning | Meaning in CROForge |
|---|---|---|
| Website / property | A site you own | A record with name, domain, and type that owns Smart Code and verify |
| Domain | The website address host (for example example.com) | Stored on the website; paste handlers strip https://, www., and paths so you save the host only |
| Allowlist | An approved list | Smart Code only runs when the live hostname is on this workspace’s domain list |
| Smart Code | A small program snippet to paste | Copied from the website’s Code tab (HTML or WordPress) |
| Snippet | A short piece of code | Preconnect plus init.js, or the WordPress wp_head helper |
| init.js | The file that starts experiments | https://app.croforge.com/{workspaceId}/init.js?ver=1.0.0, id cro-forge-experiments-js |
| Platform | The kind of CMS or stack | HTML and WordPress are ready; Next.js, Drupal, Shopify, Wix, PrestaShop, and Joomla keys exist but are incomplete |
| Verify | Check the snippet is live | URL checker on the Code tab using __smartcode_check and SMARTCODE_CHECK postMessage |
| postMessage | A note from one browser window to another | How the opened site proves Smart Code loaded |
| Cookie consent | Visitor agreement to cookies | A Smart Code control that may be hidden in the current tab |
| Debug | Inspect what went wrong | A tab to enter a URL and view debug history; the trigger may be commented out in the detail view |
| Domain settings | The gear next to the site name | Where you rename the property (see in-app FAQs) |
| Archive | Put something away | Removes the website from the active list (confirm dialog; treated as not undone) |
| FAQ | Short answers beside the screen | Install, verify, rename, and debugger questions in the website-app FAQs panel |
Screenshot
Use this screenshot filename when you add a capture: websites-apps.png in docs/assets/placeholders/. Do not embed an image in this file.
Purpose
From this screen you can:
- Add, rename, or archive websites (name, domain, type).
- Copy platform Smart Code snippets (HTML or WordPress today).
- Verify Smart Code on a URL.
- Read in-app FAQs (install, verify, rename, debugger).
Typical workflow
- Add new website. Enter Name and Domain (FAQs also mention Type). Domain should look like
example.com, not a full URL with path. - Open the site → Smart Code / Code tab.
- Choose HTML or WordPress.
- Copy the snippet and install it on the site (head /
wp_headpriority 0). - Verify with the URL checker on the same tab.
- Target campaigns at that host’s URLs. See Pages and URL targeting.
Domain settings
Use the gear / domain settings control beside the website name to rename the property. In-app FAQs describe this as: open Domain settings, edit the name, then Save.
Keep the stored domain aligned with the live hostname. Smart Code checks the host against the allowlist. A mismatch (for example registering example.com but testing on staging.example.com) looks like an invalid domain even if the snippet is present.
Code tab
The Code tab is where install actually happens:
- Platform buttons: only HTML and WordPress are shown as selectable today.
- Snippet editor with copy. HTML includes
preconnectplus theinit.jsscript. WordPress prints that script fromwp_headat priority0. - Async vs Sync and advanced flicker options can appear for HTML Smart Code. Start with Async unless engineers change it.
- Verification card: enter a full URL, then Check.
Debug tab
A Debug tab component exists for entering a URL and viewing debug history. In the current product build the Debug tab trigger may be disabled or commented out in the detail view — confirm with your release. FAQ text still describes the intended debugger flow: open Debug, enter a URL that starts with your domain, click Debug, and read Debug History.
Cookie consent
Cookie consent UI may be present but hidden in the current Smart Code tab. Do not document it as a required setup step until the control is visible in your build.
In-app FAQs to keep aligned
FAQs live beside the UI. Keep these docs and the FAQ answers aligned when install URLs change:
- How do I add a new website or app?
- Where do I install the CROFORGE SmartCode?
- How can I verify SmartCode is installed?
- How do I rename a website/app?
- How do I use Debugger?
