Skip to content

Commit de44580

Browse files
Merge pull request #5304 from segmentio/snap-products
adding description for support of product arrays with Snap CAPI
2 parents e91faa7 + e84dfc4 commit de44580

File tree

1 file changed

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

1 file changed

+8
-0
lines changed

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

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -70,6 +70,14 @@ If you want to send a Snap Event Type that Segment doesn’t have a prebuilt map
7070

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

73+
### 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" and "Brand" fields.
76+
- **Multiple products/items**: Use the "Products" field which accepts an array of products / items.
77+
78+
### Specifying the total value of a purchase
79+
The "Price" field should be used when specifying the total value of a purchase, and should contain a numeric value only. e.g. 99.5.
80+
7381
### Required parameters and hashing
7482
To match visitor events with Snapchat ads, Snap requires that one or a combination of the following parameters are sent to the Conversions API:
7583
- Email

0 commit comments

Comments
 (0)