Who this is for
Group digital director, group revenue office, group brand marketing, corporate systems team and the Suite Profit onboarding architect assigned to the portfolio. Individual property GMs are downstream reviewers of the pilot property configuration, not editors of the group-wide widget contract.
Prerequisites
- Each brand's public website reachable under the corporate DNS zone with edit access for the group web team.
- Design tokens for every brand codified in the corporate design system — primary palette, typography, radius and elevation.
- Corporate SSO connection between the group IdP and the Suite Profit operator console already live (see the corporate SSO connection playbook).
- Analytics destination for group conversions: Group Analytics & BI Connector, plus optional GA4 or Adobe Analytics for the brand marketing layer.
Step 1 — Author the central widget contract
The Suite Profit operator console holds a single contract per portfolio. The contract defines the search-form fields, the room-selection flow, the ancillary sequence and the payment methods available across the group. The group revenue office signs off on the contract once; brand marketing and property GMs then override only what is delegated to them. The default delegation model is brand palette and typography editable at brand level, everything else read-only.
Step 2 — Inherit brand palette and typography per brand
Each brand in the portfolio inherits the contract and overrides its own tokens. The widget reads the tokens at render time so brand marketing can rebrand a property without redeploying the widget. Typical brand-level overrides:
- Primary and secondary palette from the brand's design system.
- Display and body typography, either self-hosted or delivered through the corporate font CDN.
- Border radius, button shape and elevation to match the brand's public interface.
- Voice: currency labels, date locale and one of the preset copy voices attached to the brand.
Step 3 — Issue per-property widget keys
Every property in the portfolio receives a scoped widget key from the operator console. Keys are safe to embed in the public HTML — the Profitroom API call happens server-side on Suite Profit infrastructure. Keys are rotated automatically on a 180-day cadence and can be force-rotated per property from the console if the group revenue office suspects abuse.
Step 4 — Embed the script tag on each brand site
The group web team drops a single script tag on each brand site, referencing the property widget key. On multi-brand rollouts the tag is delivered through the group tag manager rather than hard-coded, so a new brand is added by publishing a container update, not a repo release. The widget is single-page-app aware; it will re-mount into any container element the brand site renders after client-side navigation.
Step 5 — Wire conversions back to Group Analytics
Every widget event — search, room select, ancillary add, payment intent, confirmation — emits a signed event to the Group Analytics & BI Connector. The connector attributes each conversion to the originating property, brand and referrer, and feeds the group RevPAR dashboard the same evening. A shadow copy of the event is optionally forwarded to the brand marketing GA4 or Adobe pipeline for campaign attribution.
Step 6 — A/B test against the native Profitroom Booking Engine per property
The Suite Profit deployment supports a per-property A/B split against the property's existing Profitroom Booking Engine landing page. The split is controlled from the operator console, defaults to 50/50 by session, and reports lift on direct conversion rate, ancillary attach rate and gross revenue per session. Group revenue reviews the split at week two, week four and week eight before promoting the winner.
Estimated timeline
For a portfolio of three to fifteen properties, initial rollout runs four to six weeks: one week to author the central contract, one to two weeks to codify brand-level token overrides, two weeks to embed and validate the widget on each brand site under corporate systems review, and a two-week measured A/B window per pilot property before the portfolio-wide switch.