1 ᐧ Connect Klaviyo and Glu
2 ᐧ Set your primary trigger
The trigger you set relates directly to the event within Glu. To learn how to trigger a flow and understand what the main triggers do read this article first.
3 ᐧ Use the structured data attached to the trigger
Glu delivers a data payload* relating to the event that fired the trigger - this is called 'structured data' and it can be used to filter the way a message is delivered and/or to personalise the content of the email beyond a standard personalisation field.
You can use it to add context to an message, set delivery rules/filters and even perform calculations within Klaviyo.
✦ These are some of our most popular triggers, along with the data that we attach to the originating event...
✦ Joined Membership Plan
Data | In plain english |
new_tier_id | The member's #ID number. |
new_tier_name | The name of the membership tier, as set in Glu. |
✦ Changes Membership Tier
Data | In plain english |
old_tier_id | The #ID number associated to the previous tier. |
old_tier_name | The name of the previous tier, as set in Glu. |
new_tier_id | The #ID number associated to the new tier. |
new_tier_name | The name of the new tier, as set in Glu. |
✦ Received Credit
Data | In plain english |
Value | The amount of credit associated to the event. |
type | Top up, adjustment or activation. |
workflow_name | The name of the workflow, as set in Glu. |
reason | Why they're receiving credit, as set in Glu. |
✦ Used Credit
Data | In plain english |
Value | The amount of credit associated to the event. |
new_tier_id | The member's #ID number. |
new_tier_name | The name of the membership tier, as set in Glu. |
✦ Referral Completed
Data | In plain english |
referral_program_name | The referral programme's name, as set in Glu. |
Heads up - A payload is a 'chunk' of useful data. In this context it relates to useful information associated to a Glu event - these appear as 'Metrics' in Klaviyo which can be used as workflow triggers.