Account Structure

What is account structure in Raptor?

In Raptor, an account is the top-level container for all data collection, recommendation logic, analytics, and product catalog content. Your account structure determines how data is segmented across your markets. Raptor recommends setting up one account per country to keep analytics accurate, recommendations relevant, and product content correctly localised.

Why one account per country?

Running multiple countries or currencies through a single account causes data quality issues across several parts of the platform. The sections below explain how each area is affected.

Analytics

Raptor Analytics tracks revenue by reading the value passed in the Subtotal parameter during tracking. If orders from different countries are recorded in different currencies within the same account, revenue figures will be aggregated incorrectly and your analytics data will be unreliable.

🔍 Note: Ensure the currency sent in the Subtotal parameter is consistent for all events within a given account. Mixing currencies in a single account cannot be corrected retroactively.

Recommendation engine

The recommendation engine learns from the behavioural data collected within a specific account. Shopper behaviour varies significantly between countries - purchase patterns, browsing habits, and popular categories differ by market. Keeping accounts separate allows the engine to build accurate, market-specific models rather than blending signals from different audiences.

Email recommendations and product catalog

Email recommendation content is served directly from your product catalog. If your catalog contains products in multiple languages or with prices in multiple currencies, the wrong language or currency may be shown to a given recipient.

For markets where multiple languages are spoken, create a separate account for each language variant. For example, a Belgian operation should use two accounts:

BE-NL for Dutch-speaking customers
BE-FR for French-speaking customers

👀 Use case: A Nordic retailer operating in Denmark, Sweden, and Norway would set up three separate accounts (DK, SE, NO) to ensure each market receives recommendations trained on local behaviour, analytics reported in the correct currency, and email content in the correct language.

How accounts map to your markets

As a general rule, use the following to decide whether a separate account is needed:

Different currency: Always use a separate account.
Different language: Always use a separate account, even within the same country.
Different domain or subdomain: Consult your Raptor implementation contact to confirm whether a separate account is required.
Different brand under the same market: Depends on whether product catalogues and audiences are shared. Consult your Raptor implementation contact.

Notes and limitations

Account structure is defined during implementation and is difficult to change after go-live. Confirm your structure before launching tracking.
Each account requires its own Product Catalog, tracking setup, and recommendation configuration.
If you are unsure whether your current structure is correct, contact your Raptor account team before making changes.