Skip to content

Commit 56ef8f8

Browse files
committed
Removed the screenshots in the doc.
1 parent 7f034cb commit 56ef8f8

File tree

4 files changed

+35
-4
lines changed

4 files changed

+35
-4
lines changed
Binary file not shown.

src/connections/destinations/catalog/moloco-rmp/index.md

Lines changed: 35 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -142,9 +142,40 @@ Stringification Logic is: {key}:{value}s concatenated by ";"
142142

143143
As page_id has a higher priority, **Page Identifier Token** will be ignored if page_id is passed
144144

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.
146146

147-
![A screenshot of a Page Identifier Token example.](images/page-identifier-token-example.png)
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+
```
148179

149180
_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.
150181

@@ -160,6 +191,6 @@ Default Mappings are not hard rules. They can be modified to your convenience.
160191

161192
## Monitoring
162193

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.
164195

165-
![A screenshot of MCM Destination Monitoring.](images/mcm-destination-monitoring.png)
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

Comments
 (0)