Merge branch 'catalog' into mixpanel-cohorts-fix

Author: forstisabella

src/connections/destinations/catalog/actions-google-analytics-4/index.md

@@ -214,6 +214,7 @@ Google reserves certain event names, parameters, and user properties. Google sil
 - fields or events with reserved names
 - fields with a number as the key
 - fields or events with a dash (-) character in the name
+- property names with capital letters
 
 ### Verifying Event Meet GA4's Measurement Protocol API
 **Why are the events returning an error _Param [PARAM] has unsupported value._?**

src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md

@@ -204,6 +204,10 @@ You may encounter this error if you use more than one identifier to update a con
 
 Events going to Google for this integration require a `GCLID` field, an `email`, or a `phone_number`. If one of those identifiers isn't being sent properly, then you may see the `The required field was not present., at conversions[0].gclid` error. To fix this, double check that at least one of those fields is being passed to Google on each payload.
 
+#### What type of import should I select when creating a conversion in Google Ads?
+
+When setting up conversions in Google Ads to upload data through Segment, select **Manual Import using API or Uploads** as the import type. This option allows Segment to send server-side conversion data through the Google Ads API, ensuring offline conversions and adjustments are uploaded correctly.
+
 ### What are the differences between the Upload Click Conversions and Click Conversion V2 Actions?
 The only difference between the Upload Click Conversions and Click Conversion V2 Actions is that the Click Conversion V2 Action has [sync modes](/docs/connections/destinations/#sync-modes).
 
@@ -223,4 +227,3 @@ If you're getting the following error:
 ```
 
 That generally means there is a conflict or problem between the account used for authorization through Segment and the Customer ID. You can read more about this in Google's [API Call Structure](https://developers.google.com/google-ads/api/docs/concepts/call-structure#cid:~:text=in%20the%20request%3A-,Authorization,must%20be%20set%20to%20the%20customer%20ID%20of%20the%20manager%20account.,-Key%20Term%3A){:target="_blank”} documentation. 
-

src/connections/destinations/catalog/actions-iterable-lists/index.md

@@ -0,0 +1,52 @@
+---
+title: Iterable Lists (Actions) Destination
+strat: iterable
+hide-boilerplate: true
+id: 66a7c28810bbaf446695d27d
+hide-dossier: true
+engage: true
+---
+
+The Iterable Lists destination allows users to upload lists of users to Iterable, in the form of audiences. For more information on this destination's features, visit [Iterable's lists documentation](https://support.iterable.com/hc/en-us/articles/115000770906-Adding-Users-and-Creating-Lists){:target="_blank"}.
+
+This is an [Engage Destination](/docs/engage/using-engage-data/#engage-destination-types-event-vs-list), which means it can be used to send data to Iterable Lists from Segment Engage Audiences.
+
+## How it works
+
+When you create an audience in Engage and connect it to the Iterable Lists destination, Segment automatically
+
+1. Creates a new list in Iterable using the audience key as the list name.
+2. Adds users to the list in Iterable when they enter the audience.
+3. Removes users from the list in Iterable when they exit the audience.
+
+{% include content/sync-frequency-note.md %}
+
+## Getting started
+
+### Prerequisites
+
+Before you begin, make sure you have:
+
+* An Iterable API Key, which you can find in your Iterable account under **Settings > API Keys**;
+* A configured [Engage Audience](/docs/engage/audiences/) that you want to connect to this destination.
+
+### Connect Iterable Lists to Segment
+
+1. From the Segment web app, go to **Engage > Engage Settings**.
+2. Click on **Destinations**, then click on **Add Destination**.
+3. Search for **Iterable Lists** and click on it.
+4. Click on **Add destination**, then click on **Confirm Source**.
+5. Under Basic Settings, enter a name for your destination (for instance, "Iterable Lists Prod Space"), your Iterable API Key, enable the destination, and click on **Save**.
+6. In your audience, on the Destinations panel, click on **Add Destination** and select the Iterable Lists destination you just created;
+7. Additional configurations can be provided in the destination settings, such as the Campaign ID, whether the unsubscribe operation is global, and whether only existing users can be updated in the list.
+8. This destination supports the Identify and Tracks methods, having `Audience Entered` and `Audience Exited` as the default events.
+9. This destination also supports a default setup (where `email` is considered as the primary identifier) or a custom setup (where you can define the primary identifier and additional fields to be sent to Iterable).
+10. Click on **Save** to apply the changes, then click on **Add 1 Destination** to save the destination configuration.
+11. Iterable Lists will appear under the Destinations table with 0 mappings. Click on the **Add mapping** button, that will open a side modal. On the side modal, click on **Add mapping**.
+12. Click on **Sync to Iterable Lists** (the only Action available).
+13. Under "Define event trigger", make sure to select the event the the proper conditions defined in the Destination Settings in the Audience, that will trigger the audience upload to Iterable Lists. It's a good practice to define a test event for the next mapping steps and testing.
+14. If needed, you can define Linked Events enrichments under step 2, "Linked Events: enrich event stream with entities".
+15. Under step 3 ("Map Fields"), you can map the event fields to Iterable fields, like `email`, `userId`, and additional fields.
+16. Optionally, you can test the mapping by clicking on **Test Mapping**.
+17. Click **Next**.
+18. Under the last step ("Settings"), give this mapping a name, and click on **Save and enable**, if you want to enable the mapping right away, or **Save**, if you want to enable it later.

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

@@ -1,5 +1,6 @@
 ---
 title: Iterable (Actions) Destination
+strat: iterable
 hide-boilerplate: true
 id: 645babd9362d97b777391325
 hide-dossier: true

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,19 +99,30 @@ 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. 
 
 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.
 
 If this approach doesn't address your use case, [reach out to Segment](mailto:[email protected]) 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.
+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.

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

@@ -149,3 +149,7 @@ Failing to generate a `messageId` that complies with Mixpanel's `insert_id` stan
 ### Why is Boardman, Oregon appearing in my users' profile location field?
 
 If you are seeing traffic from Boardman or see Segment as the browser, you might be sending server side calls to your Mixpanel (Actions) destination. To correctly populate your users' profile location field, manually pass the IP information in the context object from the server.
+
+
+### Why is the Operating System field empty in Mixpanel?
+Mixpanel captures the `Operating System` field from the "OS Name" field in Segment. For Analytics.js sources, ensure that `context.userAgentData.platform` is correctly mapped to the "OS Name" field in your destination mappings. If this mapping is missing or misconfigured, the Operating System field may appear empty in Mixpanel.