Creator Messaging: Sending Hub Messages to Your Creators
Creator Messaging lets you send broadcast messages directly to your creators via the Creator Hub inbox. You pick the recipients (specific creators, a whole program, or a saved segment), write the message with optional personalization tokens (e.g., {{first_name}}, {{affiliateCode}}), choose which program the message appears to come from, and hit Send. Creators see it immediately in the Messages tab of their Hub. Use it for program announcements, affiliate code reminders, campaign kickoffs, or any time you need to reach creators outside of email.
Note: Creator Messaging is available upon request. Contact your LoudCrowd team to enable it for your account.
What Is Creator Messaging?
Creator Messaging is a broadcast tool in LoudCrowd that lets you send Hub-channel messages to any group of creators in your program. Each message lands in the creator's Messages inbox inside the Creator Hub — a read-only inbox where creators can view messages from your program.
This is separate from email (Klaviyo) delivery. When you send a Hub message, it appears inside the LoudCrowd Creator Hub regardless of whether the creator checks their email.
What Can Brands Do with Creator Messaging?
Use Case | Example |
Program announcements | "We're launching our summer campaign — here's what you need to know" |
Affiliate code reminders | "Your code |
Commission updates | "Great news: your commission rate just moved to |
Campaign kickoffs | Kick off a new challenge with creative direction and deadlines |
Welcome messages | Greet new program members as they join |
One-off outreach | Reach a specific creator or small group directly |
How to Send a Hub Message
Go to Messages in the left sidebar of the brand app, then click Create Message, then select Hub Inbox.
Step 1: Choose Your Recipients
You can target creators using one or more of the following filters — the system delivers to the union of all matching creators (no duplicates):
Recipient Type | How It Works |
Specific Creators | Search by name or email and add individual creators |
Program | Sends to all approved participants in the selected program(s) |
Segment | Sends to all creators in a saved audience segment |
You can combine these — for example, select a program and also add two individual creators who are not in that program.
Step 2: Choose the "From Program"
Every Hub message must be sent from a specific program. This is the program name creators see as the sender in their inbox — it gives the message context and connects it to their relationship with your brand.
Once you select at least one program as a recipient, the From Program selector defaults to that program. If you are sending to multiple programs or to a segment, choose the program that best represents the context of the message.
The From Program must belong to your account. The system validates that any personalization variables you use (like {{affiliateCode}} or {{shoppableAmbassadorLink}}) are actually resolvable by the program you choose — if the program doesn't have the required setup (e.g., no storefront capability), the send will be blocked with a specific error.
Step 3: Write the Message
Field | Notes |
Subject | Shown as the message title in the creator's inbox list view. Supports personalization tokens. |
Body | Full message content. Supports personalization tokens and URLs (auto-linked for creators). |
Use the Insert Variable button to add personalization tokens. The system will render each token with the creator's actual data at delivery time.
Step 4: Optionally Apply a Template
Click Use Template to pre-fill the subject and body from a saved message template. Templates can contain personalization tokens — they're resolved per-creator at send time, not when the template is saved.
Step 5: Send
Click Send. The message is queued and delivered asynchronously — you'll see a confirmation toast. Large sends (thousands of creators) may take a few minutes to fully deliver.
Personalization Tokens
Use {{tokenName}} syntax to personalize messages for each creator. All tokens are resolved at delivery time using the receiving creator's data.
Token | What It Inserts | Requires |
| Creator's first name | Creator account |
| Creator's last name | Creator account |
| Creator's email address | Creator account |
| Creator's Instagram handle | Creator account |
| Creator's TikTok handle | Creator account |
| Name of the From Program | From Program |
| Your brand name | From Program |
| Creator's active affiliate discount code | Active affiliate code in the program |
| Human-readable description of the affiliate code discount | Active affiliate code in the program |
| Human-readable description of the affiliate link discount | Active affiliate link in the program |
| Creator's commission rate or range | Active program participant |
| Name of the creator's commission tier | Active program participant |
| Creator's storefront affiliate link | Storefront-enabled program |
| Deep link for the creator to edit their storefront | Storefront-enabled program |
| Link to the creator's hub dashboard | Ecomm-connected program |
Important: If you use a variable that a creator doesn't have data for (e.g., {{affiliateCode}} for a creator without an active code), the token renders as blank — it does not block delivery. Make sure the token makes sense for all creators in your recipient list, or use tokens that apply universally (like {{first_name}} or {{programName}}).
Validation at send time: If your From Program lacks the integration required to resolve a variable (for example, using {{shoppableAmbassadorLink}} with a program that has no storefront capability), the send will be blocked with an error message before any messages are delivered.
How Creators See Messages
Creators see their Hub messages in the Messages tab inside the Creator Hub. The tab appears in their navigation alongside Dashboard, Earnings, and Programs.
The inbox has two panes:
Pane | What It Shows |
Inbox list (left) | All messages, sorted newest first. Shows sender (program name), subject, date, and a preview of the body. |
Message detail (right) | Full subject, full body, sender, and date. URLs in the body are auto-linked. |
Creators can filter their inbox by program using the All Partnerships dropdown — useful if they're in multiple programs and want to see messages from one brand at a time.
On mobile, the inbox and detail view stack — creators tap a message to open it and use the back arrow to return to the list.
Messages in the Hub inbox are read-only. Creators cannot reply. The message footer reads: "This is a read-only message. No reply is needed." If you want to enable two-way communication, use email (Klaviyo) alongside Hub messaging.
Delivery Channels
When composing a message, you can choose to deliver via Hub, Email, or both simultaneously.
Channel | Where It Lands | Best For |
Hub | Creator's Messages inbox in the Creator Hub | In-app announcements, links back to the Hub, affiliate code reminders |
Creator's email via your Klaviyo integration | Time-sensitive outreach, creators who don't log in to the Hub often | |
Both | Hub + Email simultaneously | High-priority messages you want creators to see regardless of which channel they check |
Email requires a Klaviyo integration. If you haven't connected Klaviyo, the Email channel toggle will be disabled in the composer. Hub delivery does not require any additional integration.
Message Templates
Message templates let you save and reuse message content across sends. Templates can include personalization tokens — they're resolved per-creator at delivery time.
Templates are managed from the Messages page in the brand app. When composing a new message, click Use Template to load a saved template into the subject and body fields. You can edit the content before sending.
Templates are saved at the account level and are available to all brand users on your account.
Recipient Logic: Who Gets the Message?
When you select multiple recipient filters, the system sends to the union of all matching creators — with duplicates removed. For example:
Program A has 50 approved participants
You also add 3 individual creators who are not in Program A
Total recipients: 53 unique creators
Recipient resolution rules:
Filter Type | Who Qualifies |
Specific Creators | The exact customer records you added by search |
Program | Creators with |
Segment | All customers currently in the saved segment |
Participant status is evaluated at send time, not when you compose the message. If a creator leaves a program between composing and delivery (unlikely for most sends), they would not receive the message.
Example Messages
Example 1: Affiliate Code Reminder (Program-wide)
Recipients: Your main ambassador program (e.g., 120 approved participants) From Program: Main Ambassador Program Subject: Your exclusive discount code is ready to share Body:
Hi {{first_name}},Just a reminder that your affiliate code {{affiliateCode}} is live and ready to share with your audience. Every order placed with your code earns you {{affiliateCommissionRange}} in commission.Share your link: {{shoppableAmbassadorLink}}Thanks for being part of the program,
{{brandName}}
Example 2: Campaign Kickoff (Segment)
Recipients: Segment "Active TikTok Creators" From Program: TikTok Ambassador Program Subject: Summer Campaign — action needed by June 1 Body:
Hi {{first_name}},Our summer campaign launches June 1 and we'd love your help. We're looking for 2 TikToks per week throughout June featuring the new collection.Head to your dashboard to see campaign details: {{viewDashboard}}Questions? Reply to this email or reach out to your account manager.— The {{brandName}} Team
Example 3: Personal Outreach (Individual Creator)
Recipients: 1 specific creator (searched by name) From Program: VIP Program Subject: Quick question for you Body:
Hi {{first_name}},We've been loving your recent content and wanted to connect directly. Would you be open to a collaboration outside your standard program perks?We'll follow up by email, but wanted to make sure you saw this.— {{brandName}}
Checklist Before You Send
[ ] Have you selected the right recipient scope — specific creators, a program, or a segment?
[ ] Is the From Program correct? Does it match the context of the message?
[ ] If you're using personalization tokens, do they apply to all creators in your recipient list?
[ ] If you're using affiliate or storefront variables (
{{affiliateCode}},{{shoppableAmbassadorLink}}), does the From Program have the required ecomm/storefront setup?[ ] Have you previewed the subject and body for clarity?
[ ] Do you want to send via Hub only, Email only, or both? Is your Klaviyo integration connected if you need Email?
[ ] Is this the right time to send? (Hub messages are delivered immediately — there is no scheduled send.)
Welcome Messages and Gift Notifications
When a program uses the WELCOME system template and the approved creator's tier includes a welcome gift, the welcome message automatically includes a gift notification at the end of the message body. This happens at delivery time — no manual configuration is needed.
What gets appended: - A line of text informing the creator they've earned a welcome gift - A link to the Earnings page where the creator can claim the reward
The link format depends on the delivery channel: - Email: An authenticated link (creator is auto-logged in when they click) - Hub inbox: An unauthenticated link (creator is already logged in to the Hub) - Klaviyo: The welcomeGiftEarned and earningsPageUrl properties are passed as event properties, allowing brands to customize the gift notification in their Klaviyo template
If the creator's tier does not include a welcome gift, the welcome message is delivered as normal with no additional text.
Limitations and Things to Know
Item | Detail |
No scheduled delivery | Messages are sent immediately when you click Send — there is no option to schedule for a future time. |
No reply capability | Hub messages are one-way. Creators cannot reply from the Hub. |
No read receipts | The platform does not track whether individual creators have opened or read a message. |
Delivery is async | Large sends are processed in batches of 100 creators at a time. Full delivery for a 1,000-creator send may take a few minutes. |
Variable blanks | If a token (e.g., |
From Program validation | The system validates that the From Program can resolve any integration-dependent variables you've used. If it can't, the send is blocked with a specific error before delivery starts. |