> ## Documentation Index
> Fetch the complete documentation index at: https://moengage.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Event forwarding extension
# Introduction
The MoEngage Event Forwarding Extension in Adobe does not currently support [Unified Identity (Identity Resolution)](https://moengage-user-guide.mintlify.app/user-guide/data/user-data/unified-identity-identity-resolution).
[Adobe's event forwarding extensions](https://experienceleague.adobe.com/docs/experience-platform/tags/extensions/overview.html?lang=en) allows marketers to send collected events to a 3rd party destination. This is S2S i.e. data is collected using from client application and sent to Adobe servers, and then to the destinations.
# Scope
MoEngage and Adobe RT CDP integration allows you to connect and map their Adobe data (user attributes, segments and events) to MoEngage in real-time. Customers can then act on this data, delivering personalized, targeted experience.
With Adobe, the integration is very simple and intuitive. Simply take any Adobe [events](https://experienceleague.adobe.com/docs/experience-platform/identity/namespaces.html?lang=en), and map it to a MoEngage user events.
# Integration Prerequisites
* Access to your MoEngage and Adobe Experience platform.
* The Data API ID and Data API Key are available at **Settings** -> **Account** -> **APIs**. The Data API ID is the same as the **Workspace ID.** The Data API Key is available on the same screen in the **API Keys** -> **Data** section.
* MoEngage data cluster.
# Step 1: Configure MoEngage extension
1. On your Adobe platform, navigate to Event forwarding, and click *Extensions*
2. Search for MoEngage. Click Configure. 
3. Enter the following details about your MoEngage platform.
| Field | Action |
| ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| App ID | Copy and paste the Workspace ID. The Workspace ID of your MoEngage account is available at **Settings - > Account -> APIs ->Workspace ID**. The Data API ID and the Workspace ID of your MoEngage account are the same. |
| API key | Copy and paste the Data API Key. The Data API key of your MoEngage account is available at **Settings - > App Settings -> APIs -> API Keys -> Data**. |
| Data cluster | MoEngage data center. Read more about [Data centers in MoEngage](https://moengage-user-guide.mintlify.app/user-guide/data/key-concepts/data-centers-in-moengage). |
4. Click *Save.*
## Portfolio Support
This feature allows you to route events from a single Adobe RTCDP source to specific projects within your MoEngage workspace using attribute mapping.
### Configuration Requirements
To route events to specific projects, you must configure the following in your Adobe workspace:
* **Map the project identifier**: When forwarding events to MoEngage, map your source property (for example, `brand_name` or `app_id`) to the MoEngage event attribute `moe_project_name` in your event forwarding rule actions.
* **Ensure an exact match**: The value in your source field must exactly match the project name configured in your MoEngage portfolio. Matching is case-sensitive.
### Event Ingestion Rules
MoEngage handles event ingestion based on the following logic:
* **Successful routing**: If the value in `moe_project_name` matches a configured project name, MoEngage ingests the event at that specific project level.
* **Fallback behavior**: If the `moe_project_name` attribute is missing, blank, or does not exactly match a configured project name, MoEngage ingests the event at the global portfolio level.\
**Note**: Data ingested at the portfolio level is not associated with any specific project. This data is unusable for project-specific analysis, segmentation, or campaign targeting.
For more information, refer to [Portfolio](/docs/user-guide/settings/account/portfolio/portfolio) and [Portfolio: Data Ingestion and Management](https://www.moengage.com/docs/user-guide/data/key-concepts/portfolio-data-ingestion-and-management#event-attributes-project-level).
**Limitations**
Project-level routing for Adobe is available only for events. The following features are managed at the global portfolio level:
* **User sync**: Not supported at the project level. Users are tracked at the global portfolio level by default during outbound user syncs.
* **Cohort sync**: Not supported at the project level.
# Step 2: Setup extension rules
1. Navigate to *Rules* from the sidebar.
2. Click *Add Rule* on the top right. You can now define your rule and set up conditions and actions. 
3. Under actions, select *Extension* as MoEngage event forwarding, *Action type* as Send events and provide any name to your action. 
4. To correctly send your events data from the Adobe Experience Platform to MoEngage, you must complete the field mapping step. Mapping creates a link between the Adobe Experience data model fields and the corresponding MoEngage event fields.\
**Note**- You can add custom events attributes under custom data. Use the data icon (at the right of the custom data field) to choose specific fields from your Adobe data model. 
5. Click *Save.*
Now, the events will start flowing into your MoEngage platform.
# Step 3: View events on MoEngage
On your MoEngage dashboard, navigate to *Test & Debug* >> *Recent events* to see the list of events flowing in MoEngage platform from Adobe RT CDP.
# Rate Limits
To maintain platform stability, MoEngage limits ingestion of Adobe data to a maximum of 500 requests per second (RPS) per workspace. If your workspace exceeds this limit, MoEngage returns an HTTP `429 (Too Many Requests)` status code.
Although Adobe handles most of these rate-limiting instances automatically through its default retry policy, note the following behavior:
**Retry Exhaustion:** If Adobe exhausts all retry attempts for a batch of data, you must contact the Adobe Support Team to replay the failed requests.