Your visual language
The company owner configures its name, colour and logo. The central Track351 Hub remains separate from the company’s identity.
Choose a company name, logo and colour. Give your members an address that belongs to your programme.
The company owner configures its name, colour and logo. The central Track351 Hub remains separate from the company’s identity.
A custom dashboard domain requires ownership verification, server routing and HTTPS before activation.
The Hub uses a shared application model. Product updates can be delivered centrally, with tenant-aware validation before rollout.
Create the preview company and confirm its designated access address.
Add the verification record provided by the Hub administrator.
Point the address to the correct application and install a valid certificate.
Check the domain, login and company context. Tracking domains remain reserved and inactive in the current preview.
The draft plan comparison distinguishes a programme address from custom dashboard and tracking domains. Confirm the final scope before subscribing.
No. Migration requires field mapping, click-ID reconciliation, commission validation and a controlled changeover.
No. The current Hub preview is for fictional data and validation. Production tracking, callbacks and billing require a separate release and onboarding process.