diff --git a/src/connections/destinations/catalog/actions-klaviyo/index.md b/src/connections/destinations/catalog/actions-klaviyo/index.md
index e848f5b49a..b8f5b6356d 100644
--- a/src/connections/destinations/catalog/actions-klaviyo/index.md
+++ b/src/connections/destinations/catalog/actions-klaviyo/index.md
@@ -82,13 +82,13 @@ To add and remove profiles in Klaviyo with Engage Audience data:
 
 ## FAQ
 
-### Dealing with Error Responses from Klaviyo's API
+#### Dealing with Error Responses from Klaviyo's API
  
-#### 429 Too Many Requests
+##### 429 Too Many Requests
 
 If you're encountering rate limiting issues, consider enabling batching for the Action receiving these errors. To enable batching, navigate to the mapping configuration and set "Batch data to Klaviyo" to "Yes". This adjustment might help alleviate the rate limiting problem.
 
-#### 409 Conflict
+##### 409 Conflict
 In most cases, you can safely ignore a `409` error code. 
 
 When you use the [Upsert Profile](/docs/connections/destinations/catalog/actions-klaviyo/#upsert-profile) mapping to send Identify events, Segment first attempts to [create a new profile in Klaviyo](https://developers.klaviyo.com/en/reference/create_profile){:target="_blank”}. If the first request returns with a `409` error code, Segment sends a second request to [update the existing profile with the given profile ID](https://developers.klaviyo.com/en/reference/update_profile){:target="_blank”}.
@@ -99,12 +99,11 @@ Some customers experience 403 errors when sending audience data to Klaviyo throu
 
 To reduce the number of `403` errors that you encounter, enable [IP Allowlisting](/docs/connections/destinations/#ip-allowlisting) for your workspace. For more information the range of IP addresses Klaviyo uses for integration traffic, see Klaviyo's [How to allowlist Klaviyo integration traffic IP addresses](https://help.klaviyo.com/hc/en-us/articles/19143781289115){:target="_blank”} documentation. 
 
-
-### Can I send Engage Audiences to a pre-created Klaviyo List?
+#### Can I send Engage Audiences to a pre-created Klaviyo List?
 
 No. Engage audiences are designed to initiate the creation of new lists in Klaviyo when you use the "Add Profile to List - Engage" mapping. You cannot link Engage lists to existing Klaviyo lists and cannot edit the List ID for Engage audiences.
 
-### How can I unsuppress a profile when adding it to a list?
+#### How can I unsuppress a profile when adding it to a list?
 
 When adding a user to a list, our action make use of the [Bulk Profile Import](https://developers.klaviyo.com/en/reference/spawn_bulk_profile_import_job){:target="_blank”} endpoint (when batching is enabled), and the [Add Profile To List](https://developers.klaviyo.com/en/reference/create_list_relationships){:target="_blank”} endpoint for non-batched requests. Both of which will not update a users suppression status if they were previously suppressed. 
 
@@ -112,6 +111,18 @@ To unsuppress a previously suppressed profile in Klaviyo, use the **Subscribe Pr
 
 If this approach doesn't address your use case, [reach out to Segment](mailto:friends@segment.com) to discuss your specific requirements.
 
-### Can batching be enabled for the entire Klaviyo (Actions) destination?
+#### Can batching be enabled for the entire Klaviyo (Actions) destination?
+
+Batching is only available for events sent through the Upsert Profile action mapping. Other actions in the Klaviyo (Actions) destination don't support batching.
+
+####  Do I need to configure these event names in Klaviyo?
+
+Yes. Event names, including Event Name, Metric Name, and Product Event Name, must be preconfigured in Klaviyo. If an event name isn't set up in Klaviyo, it won’t be processed or linked to user profiles.
+
+####  How do I configure event names in Klaviyo?
 
-Batching is only available for events sent through the Upsert Profile action mapping. Other actions in the Klaviyo (Actions) destination don't support batching.
\ No newline at end of file
+To configure event names in Klaviyo:
+1. Log in to your Klaviyo account.
+2. Go to **Analytics > Metrics**.
+3. Add or verify the event names (Event Name, Metric Name and Product Event Name) you plan to use in Segment.
+4. Event names are case-sensitive. Ensure the names exactly match the ones used in your Segment integration.