Weather Influenced Campaign

Use case description

The Weather Influenced Campaign use case automatically updates your catalog with the latest weather data for key customer locations, informing your campaigns to match your customers' current climate. This can help deliver relevant experiences by personalizing offers and messages for your customers using real-time weather data.

Use case items

With this use case, you’ll get:

• Aggregate
  • Most Recent City: Provides the last city where the customer created a session_start event.
• Report
  • Most frequent cities: Provides the names and counts of the common customer cities (cities with the most session_start events) for the last 7 days.
  • City Coordinates: Provides the names and coordinates of the most common customer cities for the last 60 days.
• Segmentation
  • Weather City segmentation: Segments System Customers (cities) into segments according to how many customers opened the client's website from them within the last 7 days.
• Snippet
  • Return City Weather: Provides a string with weather information and takes Weather Catalog Name and City Name as input.
• Scenario
  • Upload Weather to Catalog: Finds all system customers representing cities and updates their properties and corresponding weather catalog with current weather information.
  • Clear Sky Campaign: Example campaign.

How to deploy the use case

After downloading the use case, follow these steps.

Meet the requirements

Check if the data in your project meets the requirements. The Use Case Center lists requirements for each use case during the deployment process.

📘

Note

Webhooks are a hard requirement because this use case requires contact to external API to get the current weather for wanted cities.

Catalogs and Automated Imports are required to store the current weather.

Understand the use case logic

This use case regularly (by default daily) updates the customer's catalog with current weather data for the most common locations. The use case builds a report of the most common cities (the cities from where we receive most session_start events). Then, it takes at most 1000 of the cities and asks an external Weather API for weather forecasts in these locations.

This process is fully automated and doesn't involve any further intervention after the use case is deployed. However, you can change the frequency of weather updates and the number of cities you want to include.

Adjust the use case

Now that you understand the use case logic, you can set up the use case according to your needs.

Email settings

Access the email and go to the Settings tab to adjust the email settings.

If you decide to customize the email settings, follow this detailed guide to make the adjustments.

Design and copy

Customize the email visuals and copy to reflect your company's brand identity.

Follow this guide to adjust the email template with products in the email node.

A/B test

A/B test the use case to better understand the email performance and revenue generated.

This use case's A/B test traffic distribution is set to Bloomreach's best practices, where 50% of customers receive the 'Abandoned Cart Email with Recommendations' email (Variant A), and 50% of customers do not (Control Group).

Learn more about the do's and don'ts of modifying A/B test.

Test and run the use case

Test a use case before deploying it. Testing ensures you don't send unfinished or imperfect campaigns to your customer base.

Once the testing is over, run the use case. Open the banner and click Start to launch the campaign.

Evaluate the results

Remember to run the use case for a few days to see the impact.

After this initial period, use the prebuilt Data Overview to measure and analyze relevant data and press Refresh to see the results.

Check campaign results regularly to optimize performance.

Other resources

Learn how to enhance and optimize email performance with different tips and tricks from Bloomreach experts.