Setting Up Your Klaviyo Integration
LoudCrowd sends creator emails natively, so most brands won't need this. If your team already runs Klaviyo and wants creator emails composed there instead, you can connect it. LoudCrowd fires the trigger; Klaviyo handles the design and the send.
This guide covers the two simplest setups: sending a reward, and sending a scheduled email to a program.
How it works
LoudCrowd doesn't give you a fixed list of events to pick from. You name the event yourself, then use that same name on both sides:
Pick an event name — free text, like
LoudCrowd_Reward_Earned.Send it once from LoudCrowd, which creates it in Klaviyo as a metric.
Build a Klaviyo flow triggered by that metric.
Use the same name on a reward or scheduled message in LoudCrowd.
The name has to match exactly in both systems — same spelling, same capitalization, no extra spaces. A typo won't throw an error; it quietly creates a second metric and your flow never fires.
Step 1: Create your Klaviyo API key
In Klaviyo, go to Settings → API Keys. If you don't see API Keys, you don't have sufficient Klaviyo permissions — ask your Klaviyo admin.
Click Create Private API Key and name it
LoudCrowd.
Grant Full Access to these scopes:
Scope | Why LoudCrowd needs it |
Events | Firing the events that trigger your flows |
Profiles | Looking up and updating creator profiles so your templates can personalize |
Subscriptions | Adding creators to your consent list (only if you use one) |
Lists | List operations |
Copy the key. You'll only see it once.
Step 2: Connect Klaviyo in LoudCrowd
You'll need to be an Owner or Admin to see the Integrations page. If "Integrations" isn't in your left nav, contact your Client Strategist to upgrade your permissions.
Go to Integrations in LoudCrowd.
Under Outbound, click Add Integration.
Select Klaviyo and paste your API key.
Leave the two optional fields blank unless you have a reason to use them. Consent List takes a Klaviyo List ID and subscribes creators to that list when they receive a reward. Messaging Event Name sets a default event name you can otherwise set per message.
Click Save.
Editing later? When you edit an existing Klaviyo integration, you must paste a fresh API key before saving. The existing key is masked and won't carry through.
You can connect more than one Klaviyo account. Additional ones appear as "Klaviyo (1)", "Klaviyo (2)", and so on.
Step 3: Send your first event
This is the step that makes the metric appear in Klaviyo. Until an event actually lands, Klaviyo has nothing to offer you in the flow trigger dropdown.
Decide your event name now, and write it down. Examples:
LoudCrowd_Reward_Earned,LC_ProgramAnnouncement.On the Integrations page, click Test next to your Klaviyo integration.
Fill in: - Recipient Email — use your own - Event ID — your event name, exactly as you wrote it down - Test Discount Code — any letters or numbers - Instagram Username — optional
Click Test. A response of
{"response": 1}means it worked.
Repeat this once for every event name you plan to use. Test events aren't deduplicated, so you can fire them as many times as you like.
Heads up on test payloads. The test event carries only a few properties — discount code, Instagram username, TikTok username, email. A real send carries far more (program name, affiliate code, storefront links, and so on). Build your flow with the test event, but fire one real send before you finalize your template so you can confirm every property you're using actually arrives.
Step 4: Build the flow in Klaviyo
In Klaviyo, go to Flows → Create Flow → Create From Scratch.
Set the trigger type to Metric, then select your event name.
Drag in an email and design it.
If your reward delivers discount codes, you must include the discount code property in the body — otherwise creators get an email with no code.
Turn the flow Live. A draft flow will not send.
Turn Smart Sending off. Smart Sending suppresses creators who've recently received another email, which will silently drop reward deliveries.
Step 5: Wire the event to a real send
There are two ways to use your event name, depending on what you're sending.
A. Rewards
Two parts: create the reward, then attach it to a Klaviyo flow.
Create the reward — requires the Owner role.
Go to Settings → Rewards → + Add New Reward.
Name the reward and set Delivery Method to Klaviyo.
For Event ID, enter your event name.
Check the discount codes box and upload your code pool. (Your CSV can include an optional
pincolumn if your codes need PINs.)Click Save.
Upload codes even if your Klaviyo email is the main event. A reward with no code pool won't show up in the next step.
Attach it to a Klaviyo Flow:
Use the same event trigger from the reward to set up a Klaviyo Flow. Insert the correct dynamic property to pull in the reward code.
B. Scheduled program-wide emails
Requires the Main role.
Go to Messages → Create Message → Email Service Provider Message.
Fill in: - Message name — internal only - Message integration — your Klaviyo integration - Message event ID — your event name. Saving pushes this to Klaviyo automatically, so you can build the flow right after. - Email properties (optional) — custom key/value pairs available in your Klaviyo template. If a property value is a URL on your store, use the
customEcommUrlproperty to pull through a pre-authenticated version that logs the creator straight into their storefront. - Recipients — the program(s) to send to - Schedule — date and time. To send immediately, leave it at the current time. Messages go out every half hour.Click Save, then build the flow in Klaviyo and turn it Live.
You can reschedule and see send history any time by clicking Schedule on the message block. For recurring sends like a newsletter, reuse the same flow and just edit the template each time.
Dynamic properties reference
Use these in your Klaviyo templates to personalize. Event properties are only present when relevant — a manual gift with no program attached won't carry programName, for example.
Event properties
Property | What it is | Example |
| Your account name |
|
| Your logo, pulled from the program's store | (image) |
| Program attached to this event |
|
| Single-use reward code |
|
| PIN paired with the reward code, when used |
|
| The creator's affiliate code for this program |
|
| Their commission rate |
|
| Their commission tier name |
|
| Discount wording when a code is used |
|
| Discount wording when a link is used |
|
| Pre-authenticated link into their storefront editor | (link) |
| Pre-authenticated link to their Creator Hub | (link) |
| Pre-authenticated version of a URL you set on a scheduled message | (link) |
On a commission tier change, two extra properties carry the previous values: event.affiliatePrevCommissionPercentage and event.affiliatePrevCommissionTierName — useful for "you've been promoted" emails.
Profile properties
Looked up on the creator's Klaviyo profile rather than the event:
Property | What it is |
| Their storefront or affiliate link |
| Instagram username |
| TikTok username |
| How many posts they created in a given month |
You can also upload coupons directly into Klaviyo and reference them with Klaviyo's own coupon_code tag if you'd rather manage codes on that side.
Any other field can be exported from LoudCrowd and uploaded to Klaviyo manually.
Troubleshooting
My event doesn't appear in Klaviyo's flow trigger list. The metric only exists after an event has landed. Go back to Step 3 and fire the test event. Give it a minute to appear.
The flow exists but nothing sends. Work down this list: Is the flow Live? Is Smart Sending off? Does the event name in LoudCrowd match Klaviyo exactly? Do your flow filters exclude the creator?
Some creators don't receive anything. LoudCrowd can only fire an event for a creator who has an email address on file. Creators without one are skipped. If you can't get a creator's email, you can still deliver a reward manually — use Send Gift → Manual (Copy Code) and send the code over Instagram DM.
My email arrives with a blank discount code. The discount code property is missing from your Klaviyo template, or the reward's code pool is empty. Check both.
A creator earned a reward but got no email. The email sends on claim, not on earn. Until they hit Redeem in their Reward Wallet, nothing fires. If they have claimed it and the code appeared in the hub but no email arrived, the Klaviyo send failed on its own — the hub reveal is the primary delivery and doesn't depend on Klaviyo.
It stopped working after I edited the integration. Editing requires a fresh API key on save. Paste a new one.
FAQ
Do I still need Klaviyo for creator communications? No. LoudCrowd sends creator emails natively, with its own templates, branding, and sending domain — that's the simpler setup and what most brands use. Klaviyo is still supported if you'd rather compose creator emails alongside your consumer email program. See Transitioning to LoudCrowd Hub Messaging if you want to move off it. Running both is fine, but make sure the same message isn't going out twice.
Can I connect more than one Klaviyo account? Yes. Additional accounts appear as "Klaviyo (1)", "Klaviyo (2)", and so on, and you pick which one a given message or reward uses.
Does LoudCrowd send my creators' social usernames to Klaviyo? Yes — Instagram and TikTok usernames sync onto the Klaviyo profile automatically, so you can segment and personalize on them.
What happens to creators who are already in Klaviyo? They're matched by email address and updated rather than duplicated.








