Goal Setting Goal setting aligns what the integration should achieve and where recommendations will appear. This step is done together with our Customer Success team so the technical work maps directly to business outcomes. Preparation List the brands, titles, or properties that need recommendations. Draft the list of channels and placements you want to personalize. Gather baseline KPI data for those placements. Identify any editorial, legal, or commercial constraints (for example, paid content rules). Main stakeholder Customer product owner (with input from editors and marketing/sales where applicable). Results Brands and environment structure agreed. Agreed channel and placement scope for phase one. Named module list for each placement. KPI definitions and measurement plan per placement. Initial constraints and filter requirements captured. Define environments and brands Every self-contained business entity — a brand, title, market, or property — maps to its own Froomle environment. An environment is a fully isolated workspace: it has its own item catalog, user interactions, model training, credentials, and API endpoints. This means recommendations for one brand never leak into another. Decide the environment structure early: One environment per brand or title is the default. If two brands share a catalog and you want cross-brand recommendations, they can share an environment; otherwise keep them separate. Test and production environments — create at least a test and a production environment for each brand so development work does not pollute live data. Capture this mapping in a simple table and hand it to the person responsible for account setup, where the environments will actually be created. Define the experience map Document the channels (web, app, email, push) and the exact placements where recommendations will appear. For each placement, capture the page type and the user context required to make the recommendations relevant. See Modules and placements for accepted channel/page_type patterns. Define modules and naming Each placement becomes a module with a stable list_name. The list name must remain consistent across requests, tracking events, and reporting. See Modules and placements for naming and structure guidelines. Align on constraints and filters Decide which business rules apply per placement, such as recency, category constraints, or excluding items already shown. These rules translate into module filters and constraints. See Filters and constraints. Define KPIs and benchmarking Choose KPIs that match the placement’s goal (for example, CTR, conversion, session depth, revenue). Decide whether you will run A/B tests or use benchmarking against a baseline. See AB testing and benchmarking and Performance & Metrics. Next step Continue with account setup.