Guides
Klaviyo events
The two ambassador events sent to a brand's Klaviyo account, with their properties.
Switching it on
A brand saves a Klaviyo private API key in Settings, Integrations. The key needs Events (full access) and Accounts (read access); we check it with Klaviyo before saving it, store it encrypted, and never show it again. If Klaviyo later refuses the key, sending stops until a new key is saved. Removing the key stops events at once.
The events
| Klaviyo metric | Sent when | Event properties |
|---|---|---|
| Applied to Ambassador Program | A creator applies to a program (invitations and imported creators do not count) | campaign_id, campaign_name, organization_slug, application_status |
| Joined Ambassador Program | A creator becomes active, about 2 minutes later so the code and link exist, and only if still active then | campaign_id, campaign_name, organization_slug, discount_code, affiliate_link |
Profile properties
Klaviyo finds or creates the profile by email and gets first and last name when we have them. The profile also gets growi_ambassador_applicant (applied), and growi_ambassador, growi_discount_code, growi_affiliate_link and growi_campaign_name (joined). Brands moving their program over keep these names, so existing flows and segments keep working (see compatibility). A program that hides creator links and codes sends no discount_code or affiliate_link.
Once per person
Each person gets each event once per program: a creator who leaves and comes back does not trigger the welcome flow again. Events start when the key is saved; earlier applications are not sent.