4. Click on **Change** in the **Share data** submenu.
5. Turn the **Share data** switch **off** (it should be gray) and press **Save**.
***
## Modify your Content ID
The Converge Meta Ads Destination will use the **Default** content mode to define the Content ID forwarded by default.
However, you can configure the destination to use explicitly the **Product ID**, the **Variant ID** or **SKU** instead.
1. Navigate to your Meta Ads Destination, click on **Configuration**.
2. Click on the **Configuration**-subtab
3. Open the **Advanced configuration (optional)** section
4. Pick your desired Content ID, and click on **Save**
**List of Content ID Modes**
| Content ID Mode | Behavior |
| --------------- | ----------------------------------------------------------------- |
| Default | Use the `variant_id` if available, otherwise use the `product_id` |
| Product Id | Always use the `product_id` |
| Variant Id | Always use the `variant_id` |
| SKU | Always use the `sku` |
***
## Converge functionality
This integration supports the following Converge destination functionality.
| Converge Feature | Supported |
| :--------------------------------------------------- | :-------------------: |
| Custom Events | 
Meta is warning you here that not all of your events are receiving identifiable information (e.g. `email`).
Ideally, Facebook would have an email for every Added To Cart that ever happens on your website so they can easily attribute it.
However, many people on the website are anonymous (they have never given their email to your store and thus Converge cannot track it). If the user never gives their email or address, then we can never send that email back.
**Converge sends as many of these parameters as there are available.**
The only events where you'd expect a very high email match rate are events where the user always has to give an email (e.g., `purchase`).
For all events where certain parameters are not always available (e.g., you don't expect all `AddToCart` or an `InitiateCheckout` to have an `email`), you can safely ignore this warning.
When inspecting the Event match quality score in Meta Events Manager, it's common to see a low percentage for the `Click ID (fbc)` parameter. In most cases, this is an expected value given how the `fbc` parameter works.
The `Click ID (fbc)` is a parameter generated by Meta that's added to the URLs of your ads and used by Meta to track and identify events and conversions. See 
Meta asks you to send an IP Address as part of the Event Matching parameters when you send over events. There are currently two versions of IP addresses in use: IPv4 and IPv6.
Both are still widely in use, but the IPv6 standard is newer, which is why Meta flags that it's still receiving IPv4 addresses. Converge supports IPv6 and sends IPv6 addresses whenever they're available.
However, there's not always an IPv6 address available. In that case, Converge sends the IPv4 address instead. The IP address version is dependent on the customer's browser and network configuration. If the customer's network configuration and browser only support IPv4, then Converge will need to send an IPv4 address as well.
Note that Meta does accept IPv4 addresses—it just wants to make sure that all advertisers support IPv6 as well. Therefore, you can safely ignore this warning.