Skip to content

Commit 278466e

Browse files
chore: Escape <>
1 parent eb51a00 commit 278466e

File tree

1 file changed

+2
-2
lines changed
  • src/connections/destinations/catalog/moengage

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -458,7 +458,7 @@ The MoEngage WebSDK offers the ability to send push notifications to Google Chro
458458

459459
#### 1. Setup your MoEngage Web SDK settings at MoEngage Dashboard
460460

461-
Configure the [web settings](https://help.moengage.com/hc/en-us/articles/210224063){:target="_blank"} on the MoEngage dashboard to start using MoEngage <> Segment integration.
461+
Configure the [web settings](https://help.moengage.com/hc/en-us/articles/210224063){:target="_blank"} on the MoEngage dashboard to start using MoEngage \<> Segment integration.
462462

463463
If you have selected `HTTPS` mode of integration in the settings, complete the following steps:
464464

@@ -551,7 +551,7 @@ When connecting the calculated trait or audience to the MoEngage destination, yo
551551

552552
### Sync yime
553553

554-
The default integration for MoEngage <> Twilio Engage connection is **Real Time.** But there are some filters that disqualify the persona from syncing in real-time, including some time-based filters which restrict your audience’s size at the time of message send.
554+
The default integration for MoEngage \<> Twilio Engage connection is **Real Time.** But there are some filters that disqualify the persona from syncing in real-time, including some time-based filters which restrict your audience’s size at the time of message send.
555555

556556
### Computed traits using Identify calls
557557

0 commit comments

Comments
 (0)