Skip to content

Commit 28a8678

Browse files
authored
Merge pull request #4375 from segmentio/Panandhan22-patch-3
Adding a note on Iterable destination page
2 parents 9840f38 + 5e56294 commit 28a8678

File tree

1 file changed

+6
-0
lines changed
  • src/connections/destinations/catalog/iterable

1 file changed

+6
-0
lines changed

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

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,9 @@ When you call `identify` with one of Segment's sources, Segment calls Iterable's
2424

2525
Iterable keys users by `email` or a user ID. This user ID will be the Segment `userId` if sent. To use a Segment `userId` for identify calls, first call identify with both a `userId` and `email`. Iterable won't accept the request and throws an error if you fail to send one of either the `userId` or `email`.
2626

27+
> info ""
28+
> You must send the `email` parameter to Segment as `email`. The `email` value can't be passed in with any other key name in the payload. Sending `email` in with a different key name (for example, `customer_email`, `mail`) will not allow Iterable's processes to understand that key holds the `email` value you want to use. The same condition applies to the `userId` field. Using keys other than `email` and `userId` cause payloads to be silently rejected by Iterable.
29+
2730
<!-- commented out because this functionality isn't currently working ZD#355518
2831
### Merge Nested Objects
2932
@@ -58,6 +61,9 @@ When you call `track` with one of Segment's sources, Segment calls Iterable's [t
5861

5962
If a user does not already exist in Iterable, calling `track` for a user event will add that user into the system. You can track with either an `email` or userId (if a `userId` exists for that email).
6063

64+
> info ""
65+
> You must send the `email` parameter to Segment as `email`. The `email` value can't be passed in with any other key name in the payload. Sending `email` in with a different key name (for example, `customer_email`, `mail`) will not allow Iterable's processes to understand that key holds the `email` value you want to use. The same condition applies to the `userId` field. Using keys other than `email` and `userId` cause payloads to be silently rejected by Iterable.
66+
6167
### Example steps:
6268

6369
First `track` event with `userId` and `email`; user will be created

0 commit comments

Comments
 (0)