Skip to content

Commit a6b215a

Browse files
authored
Merge pull request #3406 from segmentio/PR-3405
MoEngage Actions Updated Deploy
2 parents b16e88b + 9460763 commit a6b215a

File tree

1 file changed

+4
-10
lines changed
  • src/connections/destinations/catalog/actions-moengage

1 file changed

+4
-10
lines changed

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

Lines changed: 4 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -63,14 +63,12 @@ Additional Context
6363
Include additional information that you think will be useful to the user here. For information that is specific to an individual mapping, please add that as a comment so that the Segment docs team can include it in the auto-generated content for that mapping.
6464
-->
6565

66-
### Mapping the User ID and Anonymous ID
66+
### Default Mapping
6767

68-
To map the User ID to the Anonymous ID, make sure you the correct values. Scroll down to the **Define mappings** section and change the following keys from sentence case to Camel Case. Make sure you select the new values from the dropdown.
68+
> warning ""
69+
> Don't change the preset values.
6970
70-
Key | Default Value | New Value
71-
---------|----------|---------
72-
User ID | `user_id` | `userId`
73-
Anonymous ID | `anonymous_id` | `anonymousId`
71+
MoEngage provides preset values to all mappings. You don't need to make any changes to the Identify User Actions and Track Event Actions.
7472

7573
<!-- The line below renders a table of connection settings (if applicable), Pre-built Mappings, and available actions. -->
7674

@@ -93,7 +91,3 @@ If successful, the data starts flowing into your MoEngage account in 3-5 minutes
9391
<!-- Include any pertinent information here. -->
9492

9593
{% include content/ajs-upgrade.md %}
96-
97-
Follow the table below to map your existing MoEngage destination configuration to MoEngage (Actions).
98-
99-
{% include components/actions-map-table.html name="moengage" %}

0 commit comments

Comments
 (0)