> For the complete documentation index, see [llms.txt](https://omegatheme-contact.gitbook.io/omega-multi-twitter-pixels/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://omegatheme-contact.gitbook.io/omega-multi-twitter-pixels/twitter-x-conversion-api.md).

# Twitter/X Conversion API

The Conversion API (CAPI) enables a direct <mark style="color:blue;">**server-to-server**</mark> connection to share conversion data for <mark style="color:blue;">**better measurement of ad campaigns**</mark>.&#x20;

It enhances data control, complements the existing pixel, and can be used with or without pixel. CAPI allows <mark style="color:blue;">**multiple data signals**</mark> (such as click ID, email, or IP address) to send conversion events for <mark style="color:blue;">**more accurate tracking**</mark>.

{% hint style="info" %}
The Conversion API also enables tracking of offline conversion events, where conversions may begin online but conclude offline.&#x20;

By leveraging an offline Conversion API solution, you can measure these offline conversions alongside your online ones, providing a complete view of campaign performance.
{% endhint %}

### 👉 FYI: [Conversion Tracking for Websites](https://business.x.com/en/help/campaign-measurement-and-analytics/conversion-tracking-for-websites)

## Step-by-step guide to turn on Twitter Conversion API:

Follow these 2 simple steps:

### Step 1:  Turn on CAPI when setting up the pixel

When adding pixel, there is an option to turn on Twitter Conversion API here. Turn on this toggle, additional UI elements related to the Conversion API will be displayed, allowing you to configure it.

<figure><img src="/files/bEYNKpxqlKn4xHYWvBEK" alt=""><figcaption></figcaption></figure>

### Step 2:  Connect to Twitter Account

To use CAPI, just simply connect to your Twitter Account, then authorize permission to enable connection between Omega & your account:

<figure><img src="/files/I2zZPuS0Q21Q5IFAjcXF" alt=""><figcaption></figcaption></figure>

You can add multiple Twitter account & switch here to know which events are tracked with which account:&#x20;

<figure><img src="/files/e4sDuuSuGBp6VOkc0sVr" alt=""><figcaption></figcaption></figure>

Upon setting up done, click Save then start tracking server-side events seamlessly 😎

<figure><img src="/files/5Nt4RFecRM7MinqOT5VQ" alt=""><figcaption></figcaption></figure>

When events recorded, your pixels will be shown <mark style="color:green;">**Active**</mark> right in your Events Manager:

<figure><img src="/files/IJPaeechFCJGGCMe2yk1" alt=""><figcaption></figcaption></figure>

## 😎How to notice server-side events on Twitter Events Manager?

Go to your Twitter Events Manager, and select the event you want to check. Choose **View activity** here:&#x20;

<figure><img src="/files/iB4A1LK8vZG4rmHZZLdr" alt=""><figcaption></figcaption></figure>

With Server-side tracking (Conversion API), it will help detect hidden domain that is not tracked by Twitter Pixel only as Pixel is limited by ads blocker and device limitations for privacy reasons.

So if you see no host appears (as in the image), that is the server-side event fired successfully by Omega:

<figure><img src="/files/iNCsrsQ6wZjBCKOn4ctl" alt=""><figcaption></figcaption></figure>

## ❗❗ NOTE

1. Due to Shopify updates, **Purchase events** are **no longer visible in Twitter Pixel Helper**, but rest assured that you can still view them in Twitter Events Manager.<br>
2. Please be noted that if you log out 1 Twitter account from Omega, pixels connected with this account will **STOP tracking Server-side events** from then.

<figure><img src="/files/rhOosnL8ZdLc2y8qLtBU" alt=""><figcaption></figcaption></figure>