Brand

Provide Brand data in Alviss AI for metrics on perception like awareness, liking, and NPS, to quantify impact on sales and KPIs.

Brand data captures metrics about your brand's perception and performance in the market, such as awareness, liking, penetration, consideration, and recommendation. This category also includes customer experience-related tracking (e.g., satisfaction scores or Net Promoter Score).

These metrics are often sourced from third-party providers like YouGov. Alviss AI uses this data to estimate your brand's contribution to overall sales and other KPIs. By incorporating brand tracking, you can quantify how brand strength influences business outcomes.

Data Requirements

The Brand 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 metrics were collected.
  • 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 collection date in ISO 8601 format (YYYY-MM-DD).
  • Brand (string, required): The brand name or identifier (e.g., "AwesomeInsurance").
  • Metric (string, required): The metric type (e.g., "Unaided Awareness", "Aided Awareness", "Consideration", "Likeability", "Penetration", "Recommendation").
  • Value (float, required): The metric value (e.g., a percentage like 64.74).

Only the following characters are allowed when enter text values: 0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZåäöüøæÆÄÅÖÜߨ()_+-

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 metric per brand, date, etc.).

    CountryRegionGroupingDateBrandMetricValue
    SWEallall2018-01-07AwesomeInsuranceUnaided Awareness64.74
    SWEallall2018-01-07CoolInsuranceUnaided Awareness62.17
    SWEallall2018-01-07AwesomeInsuranceAided Awareness70.44
    SWEallall2018-01-07CoolInsuranceAided Awareness79.77
    SWEallall2018-01-07AwesomeInsuranceConsideration26.16
    SWEallall2018-01-07BestInsuranceConsideration30.74
  • Wide Format (Useful for spreadsheets): Columns represent combinations of Brand and Metric, with rows as dates. The first few rows define fixed metadata (e.g., Country, Region, Brand, ..), .

CountrySWESWESWESWESWESWE
Regionallallallallallall
BrandAwesomeInsuranceCoolInsuranceAwesomeInsuranceCoolInsuranceAwesomeInsuranceCoolInsurance
MetricUnaided AwarenessUnaided AwarenessAided AwarenessAided AwarenessConsiderationConsideration
Groupingallallallallallall
2018-01-0864.7462.1770.4479.7726.1632.77
2018-01-1555.3360.9782.2292.2530.7732.08
2018-01-2262.9355.1689.1577.4626.7927.84
2018-01-2964.3252.2179.0270.1330.5927.09
2018-02-0563.754.7181.4978.130.333.25
2018-02-1252.8661.2771.7373.530.5230.97
2018-02-1964.0865.5383.7274.4727.7126.84

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.
  • Multiple Brands: If tracking competitors, include them with clear identifiers to enable comparative analysis.