> ## Documentation Index
> Fetch the complete documentation index at: https://docs.runconverge.com/llms.txt
> Use this file to discover all available pages before exploring further.
# MGID
> An introduction to the MGID Ads Destination
export const OutboundLink = ({linkText, linkTarget}) => {
return {linkText}
;
};
## Overview
Destination Type:
***
## Installation Instructions
1. Navigate to your and go to your campaign settings.
2. In your campaign settings, enable **Conversion sensors** and select the **Postback** condition.
3. Fill in the event name field (e.g., `purchase`, `lead`, `signup`). You'll map Converge events to these MGID goal names later.
4. Copy your postback URL from MGID. It will look like:
```
https://a.mgid.com/postback/123456?c={click_id}&e={event_name}&r={revenue}
```
5. Note down the **Postback ID** (the digits at the end of the URL path, e.g., `123456` in the example above).
6. In the Converge sidebar, click on and then click **Create new Destination**.
7. Select the **MGID** destination and click **Next**.
8. Give your destination a **name** (e.g., MGID Destination) and click **Next**.
9. Enter your **Postback ID** from step 5.
10. In the **Set up your conversion events** section, map your Converge events to MGID event names:
* **Converge Event**: Select the event you want to track (e.g., `Placed Order`)
* **MGID Event Name**: Enter the exact event name you configured in MGID (e.g., `purchase`)
11. Add additional event mappings as needed for your other conversion goals.
12. Click **Next**.
13. Select the sources you want to forward events from, then click **Next**.
This is a server-side destination, meaning that only server-side sources can be used with this destination. You can still select client-side sources but the events will not be sent to MGID.
14. Review any issues and click **Submit**.
For this destination to work, you must add the click ID parameter to **all** of your MGID campaigns following step 15 below. **You should add this parameter for every new campaign as well**.
15. In your MGID campaign settings, navigate to **Tracking Tags** > **Add custom tracking tag** and add the following parameter:
```
mgidcid={click_id}
```
***
## Converge functionality
This integration supports the following Converge destination functionality.
| Converge Feature | Supported |
| :--------------------------------------------------- | :-------------------: |
| Custom Events | |
| Filters | |
| Server-side Conversions | |
| [Conversion amount](/destinations/conversion-amount) | |
***
## Event Mapping
MGID uses custom event mapping, meaning you define which Converge events should be forwarded and what they should be called in MGID.
During the destination setup, you configure:
* **Converge Event**: The event from your Converge tracking (e.g., `Placed Order`, `Added To Cart`)
* **MGID Event Name**: The corresponding event name in your MGID campaign goals (e.g., `purchase`, `lead`)
### Revenue Tracking
The MGID destination automatically includes revenue data when available:
* Revenue is taken from the `total_price` property of your Converge events
* Revenue is sent as the `r` parameter in the postback URL
* You can configure whether to use gross or net revenue in the advanced settings
### Click ID Requirements
For attribution to work correctly, MGID requires a click ID to connect ad clicks to conversions:
* The click ID is captured when users click on your MGID ads with the `mgidcid={click_id}` parameter
* This click ID is stored as the `$mgid_click_id` profile property in Converge
* Events will only be forwarded to MGID if this click ID is present
Events without a valid MGID click ID will be skipped and not forwarded to MGID.