Skip to content

Commit 49560d8

Browse files
authored
Merge pull request #4340 from segmentio/tanjinhong72-patch-3
Added information that Iterable perform check on phone number field
2 parents 81816fb + 78d6c2c commit 49560d8

File tree

1 file changed

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

1 file changed

+2
-0
lines changed

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,8 @@ Iterable keys users by `email` or a user ID. This user ID will be the Segment `u
2727
> info ""
2828
> 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.
2929
30+
If you send `phone` in traits, Iterable performs checks on the phone number before showing them User Profiles. Read more about [Iterable's phone number field](https://support.iterable.com/hc/en-us/articles/211970843-SMS-Overview-#contact-phone-numbers){:target="_blank"}.
31+
3032
<!-- commented out because this functionality isn't currently working ZD#355518
3133
### Merge Nested Objects
3234

0 commit comments

Comments
 (0)