Search documentation...



Build more robust campaigns on Moengage with up-to-date customer data from your data warehouse



In this mode, new users will be inserted into MoEngage and all user attributes will be kept up-to-date within MoEngage.
This mode is good for the following scenarios:
  • You want to push objects into MoEngage and want to keep the data up-to-date
Upsert has three configuration parameters:
Hightouch Column Containing MoEngage User IDThe name of the Hightouch column (id, created_at, first_name) that acts as unique user identifier in MoEngage.
Hightouch to MoEngage Default Field MappingsA list of common user attributes that will be pushed to new users in MoEngage.
Hightouch to MoEngage Custom Field MappingsA list of custom user attributes that will be pushed to new users in MoEngage.
There are reserved keywords that are blocked and should not be used as user attribute names in MoEngage. They are "id", "_id", "". These keywords must not be used in any Custom Field Mappings from Hightouch to MoEngage.
In addition, Hightouch will assign the property ht_query_{{queryId}} = true to a user when it is part of a query, and false when it is not.

    Need help?

    Our team is relentlessly focused on your success. We're ready to jump on a call to help unblock you.

    • Connection issues with your data warehouse?
    • Confusing API responses from destination systems?
    • Unsupported destination objects or modes?
    • Help with complex SQL queries?


    Feature Requests?

    If you see something that's missing from our app, let us know and we'll work with you to build it!

    We want to hear your suggestions for new sources, destinations, and other features that would help you activate your data.

On this page


Was this page helpful?