Skip to main content
Version: v1

Klaviyo

Beam connects with your Klaviyo account to enable ongoing post-purchase storytelling and activations around your brand community’s impact. Each time a customer selects a nonprofit while checking out with Beam, they see the impact they’re making alongside the rest of your brand community towards tangible goals (e.g., the [Brand] community is 43% of the way to funding the removal of 10,000 lbs of plastic from the ocean). This tangible impact growth is extremely motivating to customers, and our Klaviyo trigger can be used to drive them to take key actions (e.g., make a repeat purchase, invite a friend) across the customer lifecycle as the community nears the completion of a goal.

You can preconfigure a threshold of progress towards a goal (best practices are 70% and 100%) for when Beam should notify Klaviyo of the progress. When the community reaches that threshold, our Klaviyo integration will trigger an email to send from you to each customer who participated in that goal automatically. Beam can also send a trigger upon the completion of the goal to congratulate community members on what they funded together.

This document outlines the email trigger options available through Beam as well as the quick steps to integration.

Klaviyo Profile Metadata

When Beam's system sends events to your Klaviyo account, Klaviyo Profiles are created, or updated based on email address, with helpful metadata to determine which storefront the user is associated with. This data can be used to filter flow triggers based on the user's location if needed.

Profile data included:

NameTypePurpose
mostRecentBeamStoreIdintegerThe Beam Store Id of the store at which the user contributed to a nonprofit's goal
mostRecentBeamStoreNamestringThe Beam Store Name of the store at which the user contributed to a nonprofit's goal
mostRecentBeamStoreCountryCodestringThe country code of the store at which the user contributed to a nonprofit's goal (e.g., US, CA)

Email trigger options

Community Progress

Triggers when the preconfigured percent of the community's progress bar is passed

Recipient: each of the users who placed an order and selected that particular nonprofit to support with the donation

Data included:

NameTypePurpose
nonprofitstringThe name of this nonprofit (e.g., LES Ecology Center)
causestringThe name of this nonprofit's cause (e.g., Sustainability)
community_goalstringThe goal description of this nonprofit's community goal (e.g., Fund supplies to compost 1,000 lbs of food waste, reducing 1,500 lbs of CO2 emissions)
community_goal_imagestring (url)The URL of the image for this nonprofit's community goal
times_completedintegerThe number of times the community has completed this nonprofit's community goal
has_completedbooleanWhether the community has ever completed this nonprofit's community goal
community_progressinteger (between 0 and 100)The percent progress the community has made toward the current community goal of this nonprofit, could be larger than the trigger percent (e.g. if one large transaction pushed the progress from 69% past the 70% trigger to 71%, this would be 71)
beam_nonprofit_idintegerThe Beam Id of the nonprofit (e.g., 123)
lastSupportedNonprofitstringThe name of the nonprofit most recently supported by the user on your site

Community Progress Restart

Triggers when the nonprofit's community goal is surpassed

Recipient: each of the users who placed an order and selected that particular nonprofit to support with the donation

Data included:

NameTypePurpose
nonprofitstringThe name of this nonprofit (e.g., LES Ecology Center)
causestringThe name of this nonprofit's cause (e.g., sustainability)
community_goalstringThe goal description of this nonprofit's community goal (e.g., Fund supplies to compost 1,000 lbs of food waste, reducing 1,500 lbs of CO2 emissions)
community_goal_imagestring (url)The URL of the image for this nonprofit's community goal
times_completedintegerThe number of times the community has completed this nonprofit's community goal
first_time_completedbooleanWhether this is the first time the community has ever completed this nonprofit's community goal
lastSupportedNonprofitboolean(v2 Only) The name of the nonprofit most recently supported by the user on your site

Setting up Beam’s Klaviyo integration

  1. Create a Klaviyo API Key and send it to Beam
    1. From the Klaviyo homepage, click “Account Plan” → “Account” → “API keys” → “Create Private API Key”
    2. From the permissions page, either:
      1. Option #1: Choose custom permissions. At minimum, we require full access to Events, Flows, List, Metrics, and Profiles.
      2. Option #2: Grant full access.
  2. Create Email Templates for Beam Community Progress Emails
    1. Beam can send metrics at any progress percentage. The team recommends sending the email at 70% completion and this is the default setting.
  3. Beam will send metrics to your Klaviyo instance to enable creating a Klaviyo flow trigger
  4. Create a Klaviyo flow (Flows > Create Flow > Create from Scratch > Enter any name & tag you like)
    1. Klaviyo will ask “what will trigger this flow?”, Select the Metric option and search the list for the beam metric. Beam will confirm the metric tag to search for; It will follow the convention of community_progress or community_progress_restart.
    2. Once your flow trigger is selected, drag the email action option & configure the email to use the template created in step 2.
  5. Take the Flow live and notify the Beam team Beam will send a test trigger to any emails specified by your team
  6. Sign off on the flow and Beam takes the trigger live!

Best practices and use cases

Use cases

  1. Community is close to completing a goal
    1. Purpose: Use gamification to drive key behaviors (e.g., referral + repeat purchase)
    2. Example headline: We’re 70% of the way to providing 1,000 lbs of produce to families in Chicago in food deserts! Invite a friend to help us get there faster
  2. Goal complete; Congratulations
    1. Purpose: Show customers the impact that they were a part of to deepen their emotional connection to your brand and community. Beam can supply imagery from the nonprofit
    2. Example messaging: We did it! The [Brand] community just reached our goal of funding the protection of 500 acres of the rainforest [Nonprofit]. You made this happen- thanks for being part of our community.

Best practice content in both use cases

Example CTAs

  • Share: To celebrate, share your impact to help us grow the movement. [pre populated social graphic that Beam can provide]
  • Referral: Invite a friend to help us grow the movement
  • Repeat order: Help us do it again--here’s a code to make 2x as much impact on your next purchase (codes to be pre-configured with Beam to have an impact boost)

Example content following storytelling

  • Aligned business practices: We’re passionate about protecting the planet—here’s a bit more on how we use only sustainably grown and harvested ingredients in our supply chain.
  • Leadership statement: Here’s a note from our CEO on why this matters to us