Connecting Klaviyo to AI: profiles, lists and behaviour from the webshop
Klaviyo can be connected to AI. The assistant looks a profile up, records a new profile, names the lists that exist, puts someone on a list and can register an event on a profile. Those last two touch real customers: a list is a marketing list and an event can set a flow running, so both happen only on explicit request.
What the assistant can do in Klaviyo
Look a profile up
Find a customer by email address and report back what is known about them. That way a colleague without Klaviyo access still gets an answer to the question of whether someone is in the file.
Record a profile
Create a new profile with the details that belong to it. A profile is not yet a subscriber: the fact that someone is known in Klaviyo says nothing in itself about consent for marketing.
Name the lists
Say which lists exist in the account and which ones a customer is on. In an account that has been running for a few years that often reveals lists nobody looks after any more.
Put someone on a list
Attach a profile to a list. This is the act that makes someone a recipient of marketing, so it never happens as a by-product of another question and always after confirmation.
Register behaviour
Record an event on a profile, for instance that something was bought. Flows in Klaviyo listen to events, so a wrong or duplicate registration can set off a series of messages nobody intended.
What a webshop team does with it
E-commerce
- Situation
- A customer calls asking why he received a mail about an abandoned cart when he ordered long ago.
- What the agent does
- The assistant looks the profile up, names the lists it is on and the most recent registered events, and explains the sequence.
- Result
- The employee can answer without pulling in a marketer, and sees straight away whether something is going wrong in the registration.
Retail
- Situation
- In the shop a customer signs up for the newsletter on a paper form.
- What the agent does
- The assistant checks whether a profile already exists, records one if not and puts the customer on the newsletter list after confirmation.
- Result
- The sign-up is processed the same day, with the signed form as the record of consent.
Customer service
- Situation
- An employee wants to know before a call what is known about this customer, but has no Klaviyo account.
- What the agent does
- The assistant retrieves the profile with the details that were agreed and names the lists the customer is on.
- Result
- Context without an extra licence, and without the employee having to click around in a marketing tool.
Subscription services
- Situation
- A customer renewed outside the webshop and that is not recorded anywhere as an event.
- What the agent does
- On request the assistant registers the matching event on the profile, having first reported which flow is attached to it.
- Result
- The customer journey is accurate again, without a welcome series starting over by accident.
Connecting and bounding Klaviyo
-
1
Connecting through the platform
An administrator grants IntraGPT access to the Klaviyo account, with no more rights than the agreed tasks require. Read only is a fine start and can be widened later.
-
2
Setting permissions
You record which lists take part and which roles may use the connector. You also decide whether registering behaviour is included; most organisations deliberately switch that on later.
-
3
Using the assistant
After that you simply ask in plain language: is this customer in there, on which lists, what has she done. The answer comes from Klaviyo at that moment.
-
4
Following along in the log
Every consultation and every recording lands in the log. For an added profile or a registered event that makes it traceable when it happened and who asked for it.
Customer behaviour weighs more than an address
Klaviyo holds not only who someone is but also what they viewed and bought. That makes this connector more sensitive than an ordinary address list and calls for firm agreements about what may be recorded.
Where the data lives: Nederland of de EU
An event can start a flow
Flows react to behaviour. The assistant therefore registers something only on explicit request and reports which flow is attached to it. In case of doubt it records nothing.
A profile is not consent
Recording a profile and putting someone on a list are two different things, and that is no detail. Only the second makes someone a recipient of marketing, and the assistant does not do that unasked.
You decide who has access
Per role you record who may look things up and who may have something recorded. A customer service employee can get context this way without being able to write into the marketing file.
Processing on our own server
Profiles and behaviour are processed on our own server in the Netherlands with open-weight models. None of it is used to train a model.
Questions about Klaviyo and AI
Can I connect Klaviyo to ChatGPT?
That would mean a public service getting access to a file of customer behaviour, without roles and without a log. For a webshop that is hard to explain to your own customers. IntraGPT connects Klaviyo inside your own environment, limited to the agreed lists and actions, and processes the data on our own server.
Does IntraGPT work with Klaviyo?
Yes. Klaviyo is in the connector catalogue and in use at customers. The assistant can look profiles up and record them, name the lists, put someone on a list and register behaviour.
What is the difference between a list and a segment?
A list you fill yourself: someone lands on it because they signed up or because somebody put them there. A segment fills itself based on rules, for instance everyone who bought in the past three months. The assistant can put someone on a list, but it cannot push anyone into a segment: the segment's own rule decides that.
Can the assistant send a campaign or a flow?
Sending is not something it does. What it can do is register behaviour, and if a flow listens to that behaviour, the flow starts. That is the only path along which an act of the assistant can lead to a mail reaching a customer. Precisely for that reason registering behaviour is configured separately and is often switched on only later.
Is recording a profile the same as putting someone on the newsletter?
No, and that distinction matters in Klaviyo. A profile can exist because someone once bought something, without them wanting marketing. Only adding them to a list makes them a recipient. The assistant keeps those two apart and always asks for confirmation on the second.
Does the assistant see what a customer bought?
Only what has been recorded in Klaviyo as behaviour, and only if you allow it. That is useful for a service question, but it is also sensitive information. So you agree in advance which details may and may not appear in an answer, and which roles are allowed to ask the question at all.
What does a Klaviyo connector cost?
Connecting is part of the project we run together. The work depends on the number of lists taking part, whether it goes beyond looking things up to recording them, and whether registering behaviour is included. The Klaviyo subscription simply continues.
How long does setting it up take?
The connector is in place quickly and a first lookup question can be tested the same day. The lead time goes into taking stock of the lists and the flows, certainly in an account that has been running for years and still holds old segments and test lists.