Skip to content

Commit 79118de

Browse files
authored
formatting stuff
1 parent 557250d commit 79118de

File tree

1 file changed

+12
-13
lines changed
  • src/connections/destinations/catalog/actions-klaviyo

1 file changed

+12
-13
lines changed

src/connections/destinations/catalog/actions-klaviyo/index.md

+12-13
Original file line numberDiff line numberDiff line change
@@ -82,13 +82,13 @@ To add and remove profiles in Klaviyo with Engage Audience data:
8282

8383
## FAQ
8484

85-
### Dealing with Error Responses from Klaviyo's API
85+
#### Dealing with Error Responses from Klaviyo's API
8686

87-
#### 429 Too Many Requests
87+
##### 429 Too Many Requests
8888

8989
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.
9090

91-
#### 409 Conflict
91+
##### 409 Conflict
9292
In most cases, you can safely ignore a `409` error code.
9393

9494
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,31 +99,30 @@ Some customers experience 403 errors when sending audience data to Klaviyo throu
9999

100100
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.
101101

102-
103-
### Can I send Engage Audiences to a pre-created Klaviyo List?
102+
#### Can I send Engage Audiences to a pre-created Klaviyo List?
104103

105104
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.
106105

107-
### How can I unsuppress a profile when adding it to a list?
106+
#### How can I unsuppress a profile when adding it to a list?
108107

109108
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.
110109

111110
To unsuppress a previously suppressed profile in Klaviyo, use the **Subscribe Profile** action. This action automatically removes the suppression status for the user when they are subscribed. You can also pair this action with other mappings to suit your workflow.
112111

113112
If this approach doesn't address your use case, [reach out to Segment](mailto:[email protected]) to discuss your specific requirements.
114113

115-
### Can batching be enabled for the entire Klaviyo (Actions) destination?
114+
#### Can batching be enabled for the entire Klaviyo (Actions) destination?
116115

117116
Batching is only available for events sent through the Upsert Profile action mapping. Other actions in the Klaviyo (Actions) destination don't support batching.
118117

119-
### Do I need to configure these event names in Klaviyo?
118+
#### Do I need to configure these event names in Klaviyo?
120119

121-
Yes, the event names (Event Name, Metric Name and Product Event Name) must be preconfigured in Klaviyo. Events that are not preconfigured will not be processed or associated with user profiles.
120+
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.
122121

123-
### How do I configure event names in Klaviyo?
122+
#### How do I configure event names in Klaviyo?
124123

125-
Follow these steps:
124+
To configure event names in Klaviyo:
126125
1. Log in to your Klaviyo account.
127-
2. Go to Analytics > Metrics.
126+
2. Go to **Analytics > Metrics**.
128127
3. Add or verify the event names (Event Name, Metric Name and Product Event Name) you plan to use in Segment.
129-
4. Event names are case-sensitive. Ensure the names exactly match the ones used in your Segment integration.
128+
4. Event names are case-sensitive. Ensure the names exactly match the ones used in your Segment integration.

0 commit comments

Comments
 (0)