Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitb5a7071

Browse files
author
markzegarelli
authored
Merge pull requestsegmentio#2050 from umangmoe/develop
MoEngage documentation url update
2 parentscf8ae54 +f85337e commitb5a7071

File tree

1 file changed

+9
-11
lines changed
  • src/connections/destinations/catalog/moengage

1 file changed

+9
-11
lines changed

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

Lines changed: 9 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -184,7 +184,7 @@ The MoEngage SDK depends on the below Jetpack libraries provided by Google for i
184184
implementation("androidx.appcompat:appcompat:1.2.0")
185185
implementation("androidx.lifecycle:lifecycle-process:2.2.0")
186186
```
187-
Refer to the [SDK Configuration](https://docs.moengage.com/docs/android-sdk-configuration) documentation to know more about the build config and other libraries used by the SDK.
187+
Refer to the [SDK Configuration](https://developers.moengage.com/hc/en-us/articles/4401984733972-Android-SDK-Configuration) documentation to know more about the build config and other libraries used by the SDK.
188188
189189
### Register MoEngage with Segment SDK
190190
@@ -236,7 +236,7 @@ MoEHelper.getInstance(getApplicationContext()).setAppStatus(AppStatus.INSTALL);
236236
237237
### Configure Push Notifications
238238
239-
Copy the Server Key from the FCM console and add it to the MoEngage Dashboard.For more information about retrieving the Server Key, see [MoEngage - Getting FCM Server Key](https://docs.moengage.com/docs/getting-fcmgcm-server-key).To upload it, go to the Settings Page `Dashboard --> Settings --> Channel --> Push --> Mobile Push --> Android` and add the Server Key and package name.
239+
Copy the Server Key from the FCM console and add it to the MoEngage Dashboard. To upload it, go to the Settings Page `Dashboard --> Settings --> Channel --> Push --> Mobile Push --> Android` and add the Server Key and package name.
240240
**Please make sure you add the keys both in Test and Live environment.**
241241
242242
#### Add meta information for push notification
@@ -338,21 +338,19 @@ Add the following snippet and replace `[PARENT_ACTIVITY_NAME]` with the name of
338338

339339
You are now all set up to receive push notifications from MoEngage. For more information on features provided in MoEngage Android SDK refer to the following links:
340340

341-
*[Push Notifications](http://docs.moengage.com/docs/push-configuration)
341+
*[Push Notifications](https://developers.moengage.com/hc/en-us/sections/360013606771-Push)
342342

343-
*[Geofence](https://docs.moengage.com/docs/android-geofence)
343+
*[Location Triggered](https://developers.moengage.com/hc/en-us/articles/4403443036564-Location-Triggered)
344344

345-
*[In-App messaging](https://docs.moengage.com/docs/android-in-app-nativ)
345+
*[In-App messaging](https://developers.moengage.com/hc/en-us/sections/360013831431-In-App-Messages)
346346

347-
*[Notification Center](https://docs.moengage.com/docs/android-notification-center)
348-
349-
*[Advanced Configuration](https://docs.moengage.com/docs/android-advanced-integration)
347+
*[Notification Center](https://developers.moengage.com/hc/en-us/articles/4403878923284-Notification-Center)
350348

351349
*[API Reference](https://moengage.github.io/android-api-reference/index.html)
352350

353-
*[Compliance](https://docs.moengage.com/docs/android-compliance)
351+
*[Compliance](https://developers.moengage.com/hc/en-us/sections/4403894212116-Compliance)
354352

355-
*[Release Notes](https://docs.moengage.com/docs/segment-android-releases)
353+
*[Release Notes](https://developers.moengage.com/hc/en-us/articles/4403896795540-Changelog)
356354

357355

358356
###Identify
@@ -367,7 +365,7 @@ If your app supports the ability for a user to logout and login with a new ident
367365

368366
###Sample Implementation
369367

370-
Refer to[this](https://github.com/moengage/moengage-segment-integration)github repository for sample implementation
368+
Refer to[this](https://github.com/moengage/moengage-segment-integration)Github repository for sample implementation
371369

372370
##Web
373371

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp