Media

Media data captures investments in advertising and campaigns, including groupings by product, media type, campaign, and metrics like impressions or clicks. This encompasses all promotional activities, such as digital ads, TV spots, or social media campaigns, broken down by taxonomy relevant to your business (e.g., media groups, publishers, or channels).

All advertising contributes to sales and KPIs, so providing detailed investment data allows Alviss AI to model media effectiveness accurately. For campaigns targeting all products/services, use "all" in the Product field. Sourced from ad platforms (e.g., Google Ads, Facebook), agency reports, or internal trackers, this data enables quantification of ROI, channel performance, and campaign impacts in attributions, simulations, predictions, and optimizations. With the extended specification (Channel, Format, Device, TargetGroup, Creative, Category), it also supports richer taxonomy and more granular analysis (e.g., separating paid search from display, or online from offline).

Data Requirements

The Media 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 media investment occurred.
• Region (string, optional, defaults to "all"): 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, defaults to "all"): For additional segmentation, such as product categories, demographics, or sales territories.
• Date (date, required): The date of the media activity in ISO 8601 format (YYYY-MM-DD).
• Product (string, optional, defaults to "all"): The name or identifier of the product/service targeted (e.g., "Brand", "Life"); defaults to "all" for broad campaigns.
• Media (string, required): A short identifier for the media placement or publisher (e.g., "Google", "Facebook", "TVConventional", "OOHSponsoringLFP").
• Campaign (string, optional, defaults to "all"): The campaign name (e.g., "Campaign-2018"); defaults to "all" if not campaign-specific.
• Metric (string, optional, defaults to "Investment"): The measurement type; must be one of: "Impression", "Investment", "GRP", "Reach", "Clicks", "Leads", "Gross".
• Channel (string, optional, defaults to "Other"): The marketing channel grouping for analysis. Must be one of the following values (exact text): "TV", "Radio", "Paid Search", "Paid Branded Search", "Paid Generic Search", "Social Media", "Display Ads", "Print", "Outdoor (OOH)", "Email", "Influencer", "Affiliate", "Organic Search", "Video Ads", "Direct Mail", "Partnerships", "Podcast", "Streaming Audio", "Mobile In-App", "Native Ads", "Events Sponsorship", "Content Marketing", "Cinema", "Magazine", "Connected TV", "Video On Demand", "Other".
• Format (string, optional, defaults to "all"): The ad format or placement type (e.g., "ad", "banner", "post", "30s").
• Device (string, optional, defaults to "all"): The primary device type (e.g., "search", "television", "outdoor").
• TargetGroup (string, optional, defaults to "all"): The target audience segment (e.g., "niche", "broad").
• Creative (string, optional, defaults to "all"): A descriptor of the creative type (e.g., "interactive", "visual").
• Value (float, required): The metric value (e.g., investment in local currency like 7204, or impressions like 107204). Use a period (.) as the decimal separator.
• Category (string, optional, defaults to "all"): A high-level classification such as "online" or "offline".

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 combination).

• Wide Format (Useful for spreadsheets): Columns represent combinations of Metric (and associated attributes), with rows as dates. The first few rows define fixed attributes (e.g., Country, Region, Product, Media, Channel, Format, Device, TargetGroup, Creative, Category).

Best Practices

• Consistency: Ensure dates align with your project's periodicity (e.g., daily data if the project is set to daily granularity). Mismatched granularity will cause upload errors.
• Data Quality: Check for outliers, missing values, or inconsistencies before upload. Always include "Investment" for every combination to enable ROI calculations. 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.
• Taxonomy and Grouping: Define Media, Campaign, and Product consistently to reflect your business structure. This aids in filtering and aggregation during analysis.

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