ver 0.1 (0.6)

Package Link: Click here.

This version introduces improved historical sync, achieved through increased batch size options and internal logic changes to the sync mechanism.

What's New?

The following are the new features and improvements introduced in this version:

Enhanced batch size options for historical sync

  • Introduced additional batch size options for historical sync functionality.
  • New batch sizes are now available with options: 1, 5, 10, 15, 20, 25, 50, 75, 100, 125, 150, 175, and 200.

Mandatory check for the customer_id field in User Sync to MoEngage

  • Updated historical and real-time sync logic to validate the customer_id attribute mapping.
  • Sync behavior: If the mapped Salesforce field for customer_id is blank, the record will not be synced with MoEngage. The record will be synced with MoEngage only if the field has a value.

Mandatory check for customer_id and action fields in event Sync to MoEngage

  • Enhanced logic for both historical and real-time event syncs to validate the presence of customer_id and action mappings.
  • Sync behavior: If the customer_id or the action mapped field is blank, the record will not be sent for syncing to MoEngage.
info

Information

Suppose a record was previously synced with MoEngage, and the mapped Salesforce field value for a mandatory MoEngage attribute (for example,customer_idor action) is later cleared (made blank). In that case, that record will no longer sync with MoEngage.
This may lead to data inconsistencies between Salesforce and MoEngage.

Previous

Next

Was this article helpful?
0 out of 0 found this helpful

How can we improve this article?