You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/moloco-rmp/index.md
+35-4Lines changed: 35 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -142,9 +142,40 @@ Stringification Logic is: {key}:{value}s concatenated by ";"
142
142
143
143
As page_id has a higher priority, **Page Identifier Token** will be ignored if page_id is passed
144
144
145
-
Here’s an example of Page Identifier Token that could be tracked in a mobile app:
145
+
Here’s an example of **Page Identifier Token** that could be tracked in a mobile app.
146
146
147
-

147
+
Say the input had the following schema:
148
+
149
+
```js
150
+
...
151
+
"event":"Product List Viewed",
152
+
"vertical":"fruit"
153
+
...
154
+
```
155
+
156
+
and user chose the following mapping:
157
+
158
+
```js
159
+
// "event" represents the name of the event
160
+
event:properties.event
161
+
// "vertical" represents which vertical the event happened on
162
+
vertical:properties.vertical
163
+
164
+
// The combination of those two tokens can repsent
165
+
// "Which action happened on which vertical"
166
+
```
167
+
168
+
The tokens be stringified into:
169
+
170
+
```js
171
+
"event:Product List Viewed;vertical:fruit"
172
+
```
173
+
174
+
Logic:
175
+
176
+
```js
177
+
{key}:{value} concatenated by ";"
178
+
```
148
179
149
180
_Note_: if you decided to use the **Page Identifier Token** in your mobile app, please make sure you reuse the same **Page Identifier Token** in place of page_id when calling other Moloco’s APIs like Decision API.
150
181
@@ -160,6 +191,6 @@ Default Mappings are not hard rules. They can be modified to your convenience.
160
191
161
192
## Monitoring
162
193
163
-
Once the mappings are configured correctly, you can verify the flow of events from your source to Moloco’s destination in the “**Delivery Overview**” tab.
194
+
Once the mappings are configured correctly, you can verify the flow of events from your source to Moloco’s destination in the “**Delivery Overview**” tab. If things are configured correctly, it should show a growing **Successful delivery** count.
164
195
165
-

196
+
For more details about the monitoring tool, take a look at the [Delivery Overview](https://segment.com/docs/connections/delivery-overview/) docs.
0 commit comments