Weathercop help

Weathercop is set up with you during supported onboarding. Setup has six steps:

1. Connect your Shopify store. Weathercop synchronises Shopify customer and consent records, default addresses, products, inventory and orders. City and country are used to match a supported forecast location; the privacy policy explains the full data collected.
2. Check coverage. Weathercop works by city. We confirm which of your customers’ cities are covered during onboarding.
3. Set a trigger. Choose a weather scenario, or set your own conditions, and a cooldown for that trigger.
4. Choose products. Pick up to ten products from your Shopify catalog for the trigger, in the order you want them.
5. Connect Klaviyo. Build a Klaviyo flow that starts from the Weathercop event, and design the email in your own brand.
6. Review and launch. We review the setup with you during supported onboarding before anything goes live.

To begin, book a call or email hello@weathercop.io. We will walk you through installation and connection for your store.

Weathercop matches each customer to a weather city using the city and country on their default Shopify address, wherever that city is one we support.

• Matching is by city and country. Weathercop does not target by postcode.
• Coverage does not include every city. We confirm which of your customers’ cities are covered during onboarding.
• A customer whose city cannot be matched to a supported weather city is not included in weather matching, so they will not trigger a Weathercop event.

Not sure whether your customers are covered? Email hello@weathercop.io and we will check.

A trigger is a set of weather conditions you choose. Weathercop checks the daily forecast for each supported customer city, and when your conditions are met in the coming days it sends an event to Klaviyo.

Scenarios. Start from a built-in scenario such as hot and sunny, rain, or snow and ice, or set your own thresholds.

Weather variables. Conditions can use any of these:

• Temperature
• Precipitation
• Snowfall
• UV index
• Wind speed
• Humidity
• Weather condition

The threshold units and options available for each variable are confirmed with you during onboarding.

Cooldowns. Each trigger has a cooldown that limits repeat events for that trigger, so customers do not hear about the same weather too often. A cooldown applies to one trigger at a time; it is not a limit across all your triggers or campaigns, so plan your overall email frequency in Klaviyo.

You decide which products each trigger features. Choose them from your Shopify catalog and put them in the order you want them shown.

• Select up to ten products for each trigger.
• The products you select are the products sent with the event, so each trigger can feature products that suit its weather.
• Review your selection before you launch.

Weathercop does not send emails itself. It sends an event to your Klaviyo account, and a Klaviyo flow that starts from that event builds and sends the email.

The event carries:

• the customer’s email address, name and identifiers,
• the customer’s city,
• the forecast that met your conditions, and
• the products you selected.

Use those details in your flow so the email can be written in your brand and your voice, alongside the campaigns you already run. We confirm exactly what Klaviyo needs from you during onboarding. Please do not send API keys by email or chat; we will guide you through connecting securely.

Before a trigger goes live, we review the setup with you during supported onboarding: the conditions, the products, and the Klaviyo flow and email.

• Enable a trigger when you are ready for it to start sending events, and pause it when you want it to stop.
• Your Klaviyo flow can stay in draft until you are happy with the email.

The exact steps for testing and enabling are shared in onboarding. Email hello@weathercop.io if you would like to go through them again.

If an email you expected did not send, these are the usual places to look:

• Eligibility. Is the customer eligible to receive marketing? Their consent comes from Shopify.
• Coverage.Is the customer’s city and country matched to a supported weather city?
• Conditions. Did the forecast actually meet your conditions in the coming days? Thresholds that are rarely reached will rarely trigger.
• Cooldown. Has the trigger already sent an event recently, so its cooldown is still running?
• Klaviyo flow. Is the flow live, and does it start from the Weathercop event?

Still stuck? Email hello@weathercop.io with your store name and the trigger concerned, and we will help.

Weathercop works with the following information to match customers to a forecast and hand the result to Klaviyo:

• From Shopify: customer identifiers, names, email addresses, phone numbers, tags and marketing consent; full default addresses including street and postcode; products, inventory and store locations; and orders and line items used for campaign attribution.
• Weather forecasts for the supported cities where your customers are.
• To Klaviyo: an event containing the customer’s email address, name and identifiers, matched city/region/country, forecast and rule details, selected products and tracked links. Street, postcode, phone, tags and order records are not included in this weather-event payload. Sending and managing the email then happens in your Klaviyo account.

Read our app privacy policy for purposes, providers, retention, deletion and your rights. For privacy questions about your store, email hello@weathercop.io.