Skip to content

Commit f237362

Browse files
Apply suggestions from code review
1 parent 53d9096 commit f237362

File tree

1 file changed

+3
-3
lines changed
  • src/connections/destinations/catalog/actions-snap-conversions

1 file changed

+3
-3
lines changed

src/connections/destinations/catalog/actions-snap-conversions/index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -71,9 +71,9 @@ If you want to send a Snap Event Type that Segment doesn’t have a prebuilt map
7171
The Snapchat Conversions API only supports sending Event Types that are in the [predefined `event_type` list](https://marketingapi.snapchat.com/docs/conversion.html#conversion-parameters){:target="_blank"}. This includes custom events. You must use `CUSTOM_EVENT_1`, `CUSTOM_EVENT_2`, `CUSTOM_EVENT_3`, `CUSTOM_EVENT_4`, or `CUSTOM_EVENT_5` as the Event Type. Events sent with an invalid event type will fail with an `Unrecognized event type` error.
7272

7373
### Single or multiple products or items
74-
It's possible to send details of either single or multiple products / items in a single conversion event.
75-
Single product / item: Use the 'Item ID', 'Item Category', 'Brand', 'Number of Items' and 'Price' fields.
76-
Multiple products / items: Use the 'Products' field which accepts an array of products / items.
74+
It's possible to send details of either single or multiple products/items in a single conversion event.
75+
- **Single product/item**: Use the "Item ID", "Item Category", "Brand", "Number of Items", and "Price" fields.
76+
- **Multiple products/items**: Use the "Products" field which accepts an array of products / items.
7777

7878
### Required parameters and hashing
7979
To match visitor events with Snapchat ads, Snap requires that one or a combination of the following parameters are sent to the Conversions API:

0 commit comments

Comments
 (0)