Competitor Price

Competitor price data captures pricing information for your competitors' products or services, including per-unit prices over time. This can include average selling prices, promotional discounts, or standard rates for comparable offerings in the market.

Sourced from market research, price tracking tools, public data, or third-party providers, this data enables Alviss AI to model price elasticity, competitive pricing effects on your sales, demand forecasting, and market share dynamics. For example, it can quantify how a competitor's price drop impacts your KPIs, supporting more accurate attributions, simulations, predictions, and optimizations. By incorporating competitor prices, you can refine pricing strategies and respond to market changes effectively.

Data Requirements

The Competitor Price Data file must include the following columns (headers). All columns are required unless marked as optional:

• Country (string, required): A three-letter country code per ISO 3166 standard (e.g., "SWE" for Sweden), indicating where the pricing applies.
• Region (string, required): The region within the country (e.g., "all" for nationwide or a specific ISO 3166-2 code like "SE-AB" for Stockholm County in Sweden).
• Grouping (string, optional): For additional segmentation, such as product categories, demographics, or sales territories (e.g., "all" if not applicable).
• Date (date, required): The date the price was observed or effective in ISO 8601 format (YYYY-MM-DD).
• Competitor (string, required): The name or identifier of the competitor company (e.g., "Competitor1").
• Product (string, required): The name or identifier of the product or service (e.g., "Health", "Life", "Pc").
• PricePerUnit (float, required): The price per unit in local currency (e.g., 294.00). Use a period (.) as the decimal separator. Handle missing values with NaN or blanks—Alviss AI will flag inconsistencies during upload.

Supported Formats

Data can be uploaded in long (tidy) or wide (pivoted) format. Choose based on your data pipeline:

• Long Format (Recommended for flexibility): Each row represents a single observation (one price per competitor, product, date, etc.).

• Wide Format (Useful for spreadsheets): Columns represent combinations of Competitor and Product, with rows as dates. The first few rows define fixed attributes (e.g., Country, Region).

Best Practices

• Consistency: Ensure dates align with your project's periodicity (e.g., weekly data if the project is set to weekly granularity). Mismatched granularity will cause upload errors.
• Data Quality: Check for outliers, missing values, or inconsistencies before upload. Use the Activities dashboard to visualize and validate post-upload.
• Granularity Alignment: All data in a project must match the chosen periodicity (set during project creation). For details, see Projects.
• Competitor Tracking: Include multiple competitors and products for comprehensive analysis. Use clear, consistent naming for Competitor and Product fields to enable easy filtering and comparison.
• Currency and Units: Prices should be in local currency. If converting from other currencies, apply consistent exchange rates. Specify if prices are average, minimum, or promotional in metadata.
• Integration with Models: Reference competitor prices as drivers in attribution models to account for price competition. Combine with your own pricing data, competitor media, competitor brand, or competitor distribution for holistic insights. Use in the Basic Model Builder or [Advanced Model Builder](../../Models/Advanced Model Builder/Advanced Model Builder).

For uploading instructions, see Upload Data. If you encounter issues, contact support or refer to the API for programmatic uploads.