Skip to content

Commit 7608ab2

Browse files
author
markzegarelli
committed
markdown table and more edits.
1 parent d37b306 commit 7608ab2

File tree

1 file changed

+27
-126
lines changed
  • src/connections/sources/catalog/cloud-apps/iterable

1 file changed

+27
-126
lines changed

‎src/connections/sources/catalog/cloud-apps/iterable/index.md

Lines changed: 27 additions & 126 deletions
Original file line numberDiff line numberDiff line change
@@ -42,132 +42,33 @@ The default behavior is for Iterable to pass the `userId` associated with the em
4242

4343
Collections are the groupings of data Segment pulls from your Source. In your warehouse, each collection gets its own table, as well as a `tracks` table that aggregates all the events into a single table. 
4444

45-
<table>
46-
<tr>
47-
<td>**Collection**</td>
48-
<td>**Type**</td>
49-
<td>**Description**</td>
50-
</tr>
51-
<tr>
52-
<td>Email Bounced</td>
53-
<td>Event</td>
54-
<td>Receiving server could not or would not accept message</td>
55-
</tr>
56-
<tr>
57-
<td>Email Delivered</td>
58-
<td>Event</td>
59-
<td>Message has been successfully delivered to the receiving server</td>
60-
</tr>
61-
<tr>
62-
<td>Email Link Clicked</td>
63-
<td>Event</td>
64-
<td>Recipient clicked on a link within the message. You need to enable Click Tracking for getting this type of event
65-
</td>
66-
</tr>
67-
<tr>
68-
<td>Email Marked as Spam</td>
69-
<td>Event</td>
70-
<td>Recipient marked message as spam</td>
71-
</tr>
72-
<tr>
73-
<td>Email Opened</td>
74-
<td>Event</td>
75-
<td>Recipient has opened the HTML message. You need to enable Open Tracking for getting this type of event
76-
</td>
77-
</tr>
78-
<tr>
79-
<td>Hosted Unsubscribe Click</td>
80-
<td>Event</td>
81-
<td>User navigated to email preference center through a `hostedUnsubscribeUrl` link
82-
</td>
83-
</tr>
84-
<tr>
85-
<td>In App Clicked</td>
86-
<td>Event</td>
87-
<td>An in-app click event indicates that a user tapped a link or button in an in-app message
88-
</td>
89-
</tr>
90-
<tr>
91-
<td>In App Delivered</td>
92-
<td>Event</td>
93-
<td>Indicates that an in-app message arrived on a user's device. It does not mean that the user viewed the message.
94-
</td>
95-
</tr>
96-
<tr>
97-
<td>In App Opened</td>
98-
<td>Event</td>
99-
<td>Indicates that an in-app message displayed in an app, either because it appeared on arrival or because the user selected it in the inbox.
100-
</td>
101-
</tr>
102-
<tr>
103-
<td>In App Sent</td>
104-
<td>Event</td>
105-
<td>Indicates that Iterable sent an in-app message to a user. It does not mean that the user received the message.
106-
</td>
107-
</tr>
108-
<tr>
109-
<td>Mobile App Uninstalled</td>
110-
<td>Event</td>
111-
<td>Ghost message sent 12 hours after original push delivered results in rejection from receiving server
112-
</td>
113-
</tr>
114-
<tr>
115-
<td>Push Bounced</td>
116-
<td>Event</td>
117-
<td>Receiving server could not or would not accept message</td>
118-
</tr>
119-
<tr>
120-
<td>Push Delivered</td>
121-
<td>Event</td>
122-
<td>Message has been successfully delivered to the receiving server</td>
123-
</tr>
124-
<tr>
125-
<td>Push Opened</td>
126-
<td>Event</td>
127-
<td>User has been shown push notification by client app</td>
128-
</tr>
129-
<tr>
130-
<td>SMS Bounced</td>
131-
<td>Event</td>
132-
<td>Receiving server could not or would not accept message</td>
133-
</tr>
134-
<tr>
135-
<td>SMS Clicked</td>
136-
<td>Event</td>
137-
<td>User has clicked link within SMS message</td>
138-
</tr>
139-
<tr>
140-
<td>SMS Delivered</td>
141-
<td>Event</td>
142-
<td>Message has been successfully delivered to the receiving server</td>
143-
</tr>
144-
<tr>
145-
<td>SMS Received</td>
146-
<td>Event</td>
147-
<td>User has sent an inbound SMS that was received by server</td>
148-
</tr>
149-
<tr>
150-
<td>Subscribed</td>
151-
<td>Event</td>
152-
<td>User subscribes to a messaging channel</td>
153-
</tr>
154-
<tr>
155-
<td>Unsubscribed</td>
156-
<td>Event</td>
157-
<td>Recipient clicked on message's subscription management link</td>
158-
</tr>
159-
<tr>
160-
<td>Web Push Clicked</td>
161-
<td>Event</td>
162-
<td>User clicked on web push notification</td>
163-
</tr>
164-
<tr>
165-
<td>Web Push Delivered</td>
166-
<td>Event</td>
167-
<td>Web Push has been successfully delivered to the receiving server
168-
</td>
169-
</tr>
170-
</table>
45+
| Collection | Type | Description |
46+
| ------------------------ | ----- | ----------------------------------------------------------------------------------------------------------------------------------------- |
47+
| Email Bounced | Event | The receiving server could not or would not accept message. |
48+
| Email Delivered | Event | The message was successfully delivered to the receiving server. |
49+
| Email Link Clicked | Event | The recipient clicked a link within the message. Enable Click Tracking to receive this event. |
50+
| Email Marked as Spam | Event | The recipient marked message as spam. |
51+
| Email Opened | Event | The recipient has opened the HTML message. Enable Open Tracking to receive event |
52+
| Hosted Unsubscribe Click | Event | The user navigated to the email preference center through a `hostedUnsubscribeUrl` link. |
53+
| In App Clicked | Event | An in-app click event indicates that a user tapped a link or button in an in-app message. |
54+
| In App Delivered | Event | Indicates that an in-app message arrived on a user's device. It does not mean that the user viewed the message. |
55+
| In App Opened | Event | Indicates that an in-app message displayed in an app, either because it appeared on arrival or because the user selected it in the inbox. |
56+
| In App Sent | Event | Indicates that Iterable sent an in-app message to a user. It does not mean that the user received the message. |
57+
| Mobile App Uninstalled | Event | Ghost message sent 12 hours after original push delivered results in rejection from receiving server. |
58+
| Push Bounced | Event | The receiving server could not or would not accept message. |
59+
| Push Delivered | Event | The message was successfully delivered to the receiving server. |
60+
| Push Opened | Event | The user was shown a push notification by the client app. |
61+
| SMS Bounced | Event | The receiving server could not or would not accept message. |
62+
| SMS Clicked | Event | The user has clicked a link within an SMS message. |
63+
| SMS Delivered | Event | The message was successfully delivered to the receiving server. |
64+
| SMS Received | Event | The user has sent an inbound SMS that was received by server. |
65+
| Subscribed | Event | The user subscribes to a messaging channel. |
66+
| Unsubscribed | Event | The recipient clicked a on message's subscription management link. |
67+
| Web Push Clicked | Event | The user clicked on a web push notification. |
68+
| Web Push Delivered | Event | A web Push was successfully delivered to the receiving server. |
69+
70+
71+
17172

17273
<!-- Example: To query the Email Delivered table, you'd write a query like this:
17374

0 commit comments

Comments
 (0)