Use this guide to ensure your user-generated content (UGC) program is ready, and your systems run smoothly during the peak holiday season.
Freeze dates
-
Black Friday:
November 27, 2026 -
Cyber Monday:
November 30, 2026 -
Christmas Day:
December 25, 2026
Code freeze periods for 2026
Code freeze windows
| Period | Start date | End date |
|---|---|---|
| General code freeze |
Mon, Nov 09, 2026 |
|
| Deep code freeze 1 (Hard) |
|
|
| Deep code freeze 2 (Hard) |
|
|
Application criticality list
Bazaarvoice applications are grouped into High, Medium, and Low tiers. The criticality tiers dictate change restrictions during soft code and deep freeze windows.
High criticality (5 applications)
- Bazaarvoice API Gateway (APIGEE X)
- Bazaarvoice APIs
- Hosted Display
- Integration Bulk
- Shopify Experience
Medium criticality (15 applications)
- Actionable Insights
- Scaled Insights
- Catalog Ingestion Services
- Portal Experience
- Identity Services
- Privacy APIs
- Integration API
- Email/ SMS Notifications
- Self-Service Configuration
- Data Operations
- Data Strategy & Enablement
- Content Authenticity
- Content Moderation
- Content Processing
- AI Platform
Low criticality (1 application)
Internal System Integration Tools
Code freeze scope
Code freeze period: Mon, November 9, 2026 12:01 AM CST through Mon, January 4, 2027 11:59 PM CST
During the code freeze, Bazaarvoice will:
- Maintain a cache period between 55 and 110 minutes for our edge network to optimize the hosted display and the Ratings & Reviews (Conversations) API.
- Not make changes to any applications classified as high or medium criticality, except to fix critical issues or make minor changes that do not impact your consumer site or mobile app experiences.
- Enforce strict review and approval workflows for all proposed updates based on application criticality tiers [High/Medium/Low].
Our normal release cadence will resume Tue, January 5, 2027 at 12:01 AM CST.
Deep freeze
During the deep freeze, Bazaarvoice will further lock down our systems and make only critical system changes. Critical system changes are infrastructure or configuration changes required to restore service or prevent service disruption.
-
Deep freeze 1:
Nov 20, 2026 12:01 AM CST through Dec 01, 2026 11:59 PM CST -
Deep freeze 2:
Dec 18, 2026 12:01 AM CST through Jan 04, 2027 11:59 PM CST
The following image shows the correlation between API calls, product page views, and order count from July 2025 to January 2026 and how they spiked during the BFCM 2025 holiday shopping season.
Holiday preparedness tasks
To prepare for the holiday season, review the following tasks and identify items that are relevant to you:
General
- Sign up for system status notifications
- Update emergency contact information
- Ensure your product catalog is up to date
- Schedule load testing, if needed
- Send us scaling forecast data
Hosted display for Ratings & Reviews and Questions & Answers
- Optimize display
- Verify your review requests (formerly post-interaction email or PIE)
- Optimize review submission
- Verify schema.org markup for SEO
- Verify BV Pixel, if implemented
- Verify syndication
- Enable Ask a Product Owner, if wanted
Ratings & Reviews (Conversations) API
- Verify your data caching strategy
- Optimize display
- Optimize review submission
- Review our security imperatives
- Check your API usage (see details directly below)
Wednesday, November 4, 2026 , Bazaarvoice will double the Conversations API and Product Sentiment API keys rate limit by default.
Important: If your expected traffic exceeds the doubled rate limit, submit a temporary limit increase request to Bazaarvoice Support in advance. If you do not contact Bazaarvoice and exceed your API call rate limit, your calls may be throttled to the defined limit.
Sampling
Social (aka Vibe)
- Verify your account connections
- Verify your Google Analytics or Adobe Analytics connection
- Verify Instagram Like2Buy and TikTok Like2Buy
- Verify your Galleries, Reveal, and Showroom displays
- Verify your product catalog connection
We encourage you to use your social and display features during the holiday season. However, we recommend that you do not make changes to your product catalog, analytics connections, or on-site code during the code freeze period listed above.
affable.ai
- Create your holiday campaigns before your launch date and add creators to them early
- Optimize your Creator Portal by configuring product details, tasks, and affiliate settings
Product catalog updates
If you plan to update your product catalog, do so as soon as possible. Updates might include:
- Changes to the product hierarchy to align with preferred reporting at brand, category, or product levels
- Addition of new products or deletion of old ones
- Updates to the product information required for syndication including brand name, UPC, EAN, ISBN, product page URL, product image URL, or manufacturer part number
Updates through Portal
Use Portal to quickly view and manage your product catalog. Common tasks include correcting errors that originate in your feed and adding missing product data.
Product feeds
If you provide product catalog data in a single feed file, send the updated feed to Bazaarvoice by October 31. We strongly recommend this for retail clients with large product catalogs.
We also recommend that you send updated feeds before the products are live on your website. This will allow us to set up syndication connections and ensure that all systems are properly indexed.
Large-scale product catalog changes
During the code freeze and deep freeze, Bazaarvoice will closely monitor all incoming product catalog feeds. If we detect large-scale changes in an incoming product catalog feed, we may pause its import if it could negatively impact overall system performance. We do this to ensure no degradation in the performance of the hosted display, API, and feed export systems. We will resume importing the feed when we determine it is appropriate to do so.
Maximize conversion rates
During the holidays, every click counts. One of the most effective ways to convert a browser into a buyer is to build immediate trust. The Bazaarvoice Intelligent Trust Mark provides a visible, dynamic badge on your product pages that signifies the authenticity of your customer reviews. This can give you a crucial competitive edge.Find out how to get it enabled in this article: Bazaarvoice Intelligent Trust Mark.
Brands syndicating to retailers
If you are a brand that syndicates content to retailers, ensure your retail channel partners have correct and complete product information.
Pre-holiday load and advance performance testing
Bazaarvoice proactively scales our systems to handle increased holiday traffic and leverages a content delivery network (CDN) to ensure optimal performance during periods of high demand. Because we serve many of the world's largest retailers and brands, we add significant load capacity for the entire holiday season. Our capacity scaling strategy considers factors like network growth, online shopping popularity, and mobile shopping, based on historical data from the Bazaarvoice Network.
You must schedule load and performance tests at least three weeks in advance because of the stress that the holiday season puts on our systems. All requests will be assigned an available testing slot. Requests will be assigned a testing slot based on the order in which we receive them. Testing slots fill up quickly, so we can't guarantee that you will receive a testing slot.
We do this because tests conducted outside of an approved testing slot may be negatively impacted when other tests are occurring at the same time, making the results invalid. Testing slots are limited. Contact Bazaarvoice Support as soon as possible to schedule load or performance testing of your systems that incorporate Bazaarvoice products. Depending on the scope of your agreement, service fees may apply. Contact your Client Success Director with any questions.
Security
The number of security attacks against online retailers peaks during the holiday season. Our priority is protecting you and your customers' data while supporting safe and secure shopping. To prevent malicious activity, Bazaarvoice continuously monitors and blocks application layer attacks.
We will alert you to known security threats affecting Bazaarvoice systems through the system status notification system. Contact Bazaarvoice Support to report a security incident.
System status notifications
If you've subscribed to Bazaarvoice system status notifications, we will send email and SMS alerts about incidents and security threats.
To receive email and SMS alerts about issues affecting Bazaarvoice systems, go to status.bazaarvoice.com and select Subscribe to updates.
Technical emergency contacts
Accurate contact information is crucial so we can reach you during the holiday season if we detect an issue. Contact Bazaarvoice Support to verify and update your technical emergency contacts. Your emergency contacts should include at least one person on call during the peak holiday season.
Contacting Bazaarvoice
With offices across the globe, the Bazaarvoice Support team has holiday schedules in place to ensure you have 24/7 coverage for critical issues. Bazaarvoice defines a critical issue as an outage impacting the following services:
- Submission or display in production
- Publication to social networks
- CAS, Social Commerce, or affable.ai dashboards
- Influenster app
Reaching out to Bazaarvoice Support directly is especially important during the holiday season because it's the quickest way to resolve any issues you encounter.
1. Live chat
Available from the Support Community at the following times:
- 8:30 AM to 5:00 PM CST UTC-5 on regular US business days
- 8:30 AM to 5:00 PM GMT on regular UK business days
-
9:00 AM to 5:00 PM AEST on regular APAC business days
2. Telephone
Available 24/7 for critical issues. If your call is not answered, you must leave a voicemail with your name and phone number (including country code) to ensure a return call. All other requests will be managed during regional business hours.
| Region | Toll-Free / Support Number |
|---|---|
| Americas | 888-984-1381 (toll free) or 866-522-9227 (option 4) |
| United Kingdom | 0800 368 0991 (toll free) |
| France | 08 05 08 94 80 (toll free) |
| Germany | 0800 188 8904 (toll free) |
| EMEA (other than Germany) | +44(0)20 8080 1100 (option 4) |
| Australia | 1300-089-962 (toll free) or 02 9362 2200 (option 4) |
| APAC (other than Australia) | 061 2 9362 2200 (option 4) |
3. Online
- Sign in to the Bazaarvoice Portal.
- On the Portal homepage, select Access the Support Community.
- Select Open a Case.
- Select your client instance (BV site).
- From the drop-down menu, select Production Outage/Legal/Privacy Breach.
- File a case describing the details of the problem, steps to reproduce, and example links.
- Select Confirm.
- If available, attach a screenshot as a case comment.
You will receive an automated response to confirm receipt of your request. A service representative will respond to your case in accordance with the Service Level Objective (SLO). For more information on how to create a support case, read our support article.
Application criticality & freeze policy
Bazaarvoice classifies applications by criticality (High, Medium, Low) to determine what changes are permitted during each freeze period.
Application criticality levels
| Level | Definition |
|---|---|
| High | Applications that directly impact clients’ revenue and consumer-facing experience. For example, Hosted Display, Shopify Experience. |
| Medium | Applications that affect data freshness or clients’ ability to monitor and act on performance. For example, Actionable Insights. |
| Low | Applications that support internal functions and don’t affect clients’ experience. |
Freeze policy by criticality
| Freeze period | High criticality | Medium criticality | Low criticality |
|---|---|---|---|
|
Code freeze (soft freeze) |
Only critical (P1) and high-priority (P2 & P3) fixes with formal approval can be released. | All priority changes with formal approval. | No restrictions. |
|
Deep freeze (hard freeze) |
Only blocking (P1) fixes with formal approval can be deployed. |
Only blocking (P1) fixes with formal approval can be deployed. |
Only blocking (P1) fixes with formal approval can be deployed. |
All exception releases require strict review and internal approval from Bazaarvoice.
Common Code Freeze FAQs
To help you prepare for a seamless holiday shopping season, we have assembled answers to the most common questions asked during this period.
Platform Performance & Monitoring
What monitoring tools does Bazaarvoice use to measure availability and performance?
Bazaarvoice monitors system availability and performance using a combination of industry-standard tools, including CloudWatch, Datadog, and PagerDuty, alongside custom internal monitoring tools. During peak Black Friday/Cyber Monday (BFCM) periods, continuous 24/7 dedicated engineering oversight supplements our standard monitoring framework.
What Service Level Indicators (SLIs) and Key Performance Indicators (KPIs) are monitored to ensure platform reliability?
We monitor all core services 24/7 using automated enterprise tools. Key metrics include:
- Availability and uptime: Tracking system responsiveness across all service levels.
- Latency and response times: Ensuring optimal API and page performance.
- Error rates: Detecting and resolving system anomalies instantly.
Do you have predictive monitoring in place?
Yes. All client systems are continuously monitored using a unified monitoring stack and standardized alerting thresholds to detect anomalies proactively.
Incident Management & Reliability
How do you handle an outage?
Bazaarvoice follows an established global incident management process managed by our 24/7 Engineering Support team. Our priority is restoring service as quickly as possible, followed by thorough root-cause analysis (RCA) and post-restoration remediation.
Does your system degrade gracefully during high-traffic events or outages?
Yes. Where applicable, our architecture includes fault tolerance, graceful degradation, failover, and disaster recovery capabilities to maintain core functionality under extreme traffic loads.
Do you have automatic event notifications in place?
Yes. Our Support team maintains real-time updates and incident communications on status.bazaarvoice.com.
What are your response times for support and technical issues?
Bazaarvoice publishes standard SLA response times through the Bazaarvoice Support Community. Contact Bazaarvoice Support for specific details based on your support tier.
Are system timeout values configurable on the fly?
Bazaarvoice does not offer client-configurable timeout values. However, our systems utilize built-in resilience and throttling mechanisms to handle latency variations and protect upstream performance.
Architecture & Infrastructure Dependencies
Does the Bazaarvoice service depend on third-party cloud providers?
Yes. Bazaarvoice relies on Amazon Web Services (AWS) and Google Cloud Platform (GCP) for underlying cloud infrastructure and server hosting.
Which Content Delivery Networks (CDNs) are used in your environment?
Bazaarvoice utilizes enterprise CDNs, primarily Cloudflare and Amazon CloudFront, to cache and deliver display content globally with ultra-low latency.
What other downstream systems could impact service delivery?
Primary downstream dependencies include core cloud providers (AWS, GCP) and global CDN networks (Cloudflare, CloudFront, Akamai).
Do downstream systems have manual or automatic failover capabilities?
System failover utilizes a hybrid approach. Depending on the component, failovers may be manually initiated by engineering teams, with automated failover and scaling processes taking over execution. The primary Display path and core APIs operate across multiple redundant regions and availability zones.
Is platform failover automatic or manual?
Core services run across multiple availability zones. While automated processes handle traffic distribution and localized zone recovery, full cross-region failover triggers are manually verified by engineering to prevent data split-brain conditions.
Code Freeze & Operational Policies
What is your SLA on availability, including maintenance windows?
For critical Display path services, Bazaarvoice maintains weekly maintenance windows that do not exceed two hours and are scheduled during minimal traffic periods. These scheduled windows are excluded from uptime SLA calculations. Note that no routine maintenance is scheduled during the BFCM period.
Can configuration changes be made during the Code Freeze window?
Minor non-impacting configuration changes (such as Portal settings or administrative updates) are permitted during Soft Freeze, subject to internal review. However, no configuration changes are permitted during Hard Freeze unless required to resolve a P1 service outage.
How does Bazaarvoice prepare for extreme Black Friday/Cyber Monday traffic spikes?
Bazaarvoice conducts advance infrastructure scaling, doubles default API rate limits starting early November, and institutes strict code freeze controls to ensure maximum stability and zero unexpected site disruptions.
What happens if an emergency fix is needed during Deep Freeze?
Emergency fixes during Deep Freeze require executive engineering sign-off (P1/Critical blocking issues only) and undergo rigorous sandbox testing prior to deployment.
Will scheduled product catalog feeds continue to process during the holiday freeze?
Standard daily catalog imports will continue as normal. However, large-scale catalog restructuring or schema changes should be completed prior to the start of Code Freeze.
How do I request temporary API rate limit increases for the holiday season?
API limits are automatically doubled starting early November. If your traffic projections exceed this doubled limit, submit a ticket to Bazaarvoice Support at least 3 weeks prior to Black Friday.
How far in advance should custom load testing be scheduled?
Custom load testing requests must be coordinated with Bazaarvoice Support at least 3 weeks in advance to ensure environment availability and dedicated monitoring resources.
Regional Compliance & French Code FAQs
Is the Date of User Experience field mandatory for French locales?
Yes. To comply with the French Consumer Code, all reviews displayed in *_FR locales must include this field to distinguish between the review date and the actual date of product use.
Can I edit or delist the Date of User Experience question for French (*_FR) locales?
No. For French-native locales, the field labels are locked and the question cannot be removed. This prevents accidental non-compliance with transparency regulations.
Is the Date of User Experience field mandatory for non-French locales (e.g., en_US, en_GB)?
No. For regions outside of France, the field is available but not mandatory. You can edit the labels or remove the question entirely based on your business needs.
Will the Date of User Experience field appear in my editor if I only have one French locale?
Yes. If your implementation includes at least one *_FR locale, the field is added to all implementations and catalog categories by default to ensure account-wide compliance.
Can I still reject reviews that only mention Customer Service (CS) or Shipping (SI) in France?
No. Under the updated moderation alignment, reviews focusing on CS or SI can no longer be rejected as "irrelevant” for French sites. They must be published locally to ensure 100% transparency.
Do API clients need to contact Bazaarvoice Support to enable this?
Yes. While hosted clients can manage this in the Submission Form Editor, API clients must contact support to ensure the option is correctly enabled in their custom implementation.
Can my historical custom date data be migrated to the new field?
Yes. If you currently use a custom date question, Bazaarvoice will work with you to migrate that data into the new standardized field to maintain your review volume.
Can I restrict my display to show only reviews that include a date of experience?
Yes. Bazaarvoice Support can enable a setting to hide reviews that lack this field.
Will restricting the display reduce my total review volume?
Yes. Enabling this restriction will hide legacy reviews that do not have a date of experience recorded.