MoEngage is committed to providing you with robust solutions for data privacy and compliance. To support your data residency and localization needs, MoEngage offers Personally Identifiable Information (PII) Data Centers (DCs) where MoEngage doesn't have its primary data center.
What is a PII Data Center?
A PII DC is a specialized, physically isolated DC designed to store and process Personally Identifiable Information (PII) within a specific geographical region. This ensures that your customers' sensitive data remains within their country's borders, which helps you comply with local data residency and privacy regulations. PII DCs come into play only when there is no main DC already present in your region. For the main DCs list, please refer to this article.
PII DCs act as intermediaries between your systems and the main DCs of MoEngage. While the main DCs store and process non-PII data, the designated PII DC securely handles all PII.
Key Features
| Feature | Description |
|---|---|
|
Data Residency |
Guarantees that all PII data is stored and processed within the specified country's borders, ensuring compliance with local regulations. |
| Secure PII Handling |
Implements robust security measures, including encryption at rest and in transit, to protect all PII data. |
| Seamless Integration |
Integrates with the main DCs of MoEngage with minimal disruption, allowing for smooth campaign orchestration and execution. |
| Real-time Processing |
Maintains low latency and real-time processing capabilities for timely and efficient customer engagement. |
| Scalability |
Designed for easy expansion to other regions, providing a flexible solution for your growing business needs. |
Data Ingestion
You can send PII data to the PII DC and non-PII data to the MoEngage main DC. The customer number is a must to send PII data, as it is used to find a particular customer's email address or phone number.
Message Sending
All communications are initiated from the main DC of MoEngage, where segmentation is first performed to identify the users to whom the communication needs to be sent. After a user is identified for communication, the communication message is constructed and will be sent to PII DC, as the main DC will not have an email address, mobile number, or any other PII. The communication message and the customer number are sent to PII DC.
With the customer number, the PII DC can identify the actual email address or mobile number, and along with the communication message, it can now request the providers to send the message.
Available PII DCs
You can choose the DC that best aligns with your geographical and regulatory requirements from the following options:
|
Data Center Code |
Provider | Location |
|---|---|---|
| PII DC01 | AWS | UAE |
| PII DC02 | GCP | Qatar |
| PII DC03 | GCP | Saudi Arabia |
Integration and Configuration
To get started with the PII DCs of MoEngage, you must configure your data ingestion process to point to the correct regional endpoint.
Data Ingestion Endpoint
The URL for data ingestion into a PII DC is:
Method: POST
https://pii-dc0X.moengage.com/v1/transition/<Workspace_ID>Note:
- Replace X in pii-dc0X with the number of your designated PII DC (for example, 1 for AWS UAE).
- Replace <Workspace_ID> with your specific MoEngage Workspace ID.
For more information on working with the Bulk Import API, refer to the Bulk Import API documentation.
Frequently Asked Questions (FAQs)
This section addresses common questions and potential issues to ensure a smooth integration.
General and Security
MoEngage PII DCs adhere to the same high-security standards as its main DCs, which are ISO certified and SOC2 Type 2 compliant. The PII is encrypted at rest and also in transit for internal communication.
MoEngage solution architects will contact you for a PII DC setup while you are onboarded to MoEngage. PII DC is only suitable for you if there isn't already a main DC present in your region.
Contact your dedicated MoEngage account manager or sales team for details on pricing and commercial terms for PII DCs.
Integration and Data Management
No, MoEngage only accepts PII into the PII DCs through the data APIs.
Yes, you can send a maximum of 20 PII attributes to the MoEngage PII DC.
Mobile numbers sent through the data APIs should be in the E.164 format.
No, personalization is not supported in the first phase of the PII DC release.
The data will be processed in the main DC of MoEngage, not the PII DC. It is critical to ensure all PII is routed only through the correct PII DC endpoint to meet data residency requirements.
Common errors include using an incorrect Workspace ID, a malformed API endpoint URL, or authentication issues. An HTTP 4xx error code usually indicates a client-side problem with your request.
PII DC supports 1K RPM for data ingestion.