# X Ads V2 Conversion API

> Send server-side conversions to X Ads with an authenticated X account and your configured event mappings.

Source: https://docs.oursprivacy.com/docs/x-ads-v2

Send conversions from your configured events to X Ads. Choose the ad account and pixel, map the conversion identifiers, and publish when you are ready to start delivery.

## Connect your X account

1. Open **Destinations**, select **Add destination**, and choose **X Ads V2**.
2. Select **Connect**, sign in with the X user who manages your ads, and approve the requested access. Your user needs **Ad Manager** or **Ad Admin** access to the ad account.
3. Select the ad account and enter its **Pixel ID**, found under **Tools → Events** in X Ads.

Ours Privacy refreshes your connection automatically. If it asks you to reconnect, select **Reconnect** and sign in with the X user who manages your ads.

## Configure conversion events

1. Create the conversion events you want to track in X Ads Events Manager.
2. Configure the destination's event mappings. Set **Conversion Event ID** to the matching ID from X Ads.
3. Include at least one supported identifier: the X click ID (`twclid`), email, phone number, or IP address together with user agent.
4. If you send a value, map a whole dollar amount such as `225`. Set the currency for that value.
5. Add this destination to the allowed events you intend to deliver and publish your changes.

Review the destination's dispatch results after publication to check delivery.

## Replace an existing destination

If you already use [X Ads](https://docs.oursprivacy.com/docs/x-ads), contact `support@oursprivacy.com` for help setting up X Ads V2. Review the ad account, pixel, event mappings, and allowed events before publishing the replacement. Disable the previous destination when you enable the replacement to avoid sending the same conversion twice.