​
Overview

Destination Type:

Client-side

​
Installation Instructions

This is a client-side-only destination, meaning that you will need to be tracking all events client-side (including Placed Order) for this destination to work properly.

1. Set up the Converge Destination

  1. Navigate to your Twitter Ads account and choose Tools > Events Manager.

  2. Copy your Twitter Pixel ID

    1. If you already have an events source, at the top of the page, find the ‘Twitter pixel’ section and copy the ID. (e.g. obarl)
    2. If not, you will be prompted to create a new event source, follow the instructions and copy the ID when you are done.

  3. In the Converge dashboard, under Destinations, click

    Create New Destination
    and fill in your Pixel ID.

  4. See below for instructions on how to configure your conversion events.

2. Create your conversion events

  1. In the Twitter Ads > Tools > Events Manager, click on the Create Event button.
  2. Give your event a name, e.g. ‘Placed Order’ when you are setting up a purchase conversion.
  3. Pick a Twitter event type, e.g. ‘Purchase’. You can find a suggested mapping of Converge to Twitter Ads event types below.
  4. Configure your attribution settings and click on Next.
  5. Choose the ‘Define event with code’ setup method and click on Next.
  6. Click ‘Save’ to finish the setup.
  7. You can now find the event in the Events table in the Twitter Ads Events manager. Under the event, the ID is composed as tw-{pixelID}-{eventID}. Copy the eventID into the ‘Twitter Event IDs’ section of the Converge destination configuration.

Repeat the steps above for all the events you want to report on in Twitter Ads
Once you have installed your Converge Destination, you should pause or remove all existing Twitter Ads tracking. Leaving these on will lead to duplicate tracking.

​
Modify your Content ID

The Converge X Connection will use the Product ID by default. However, you can configure the connection to use explicity the Variant ID or SKU instead.

  1. Navigate to your X Connection, click on Configuration.
  2. Click on the Advanced-subtab
  3. Click on Edit configuration
  4. Pick your desired Content ID, and click on Save

List of available Content ID Modes

Content ID ModeBehavior
Product IdAlways use the product_id
Variant IdAlways use the variant_id
SKUAlways use the sku

​
Converge functionality

This integration supports the following Converge destination functionality.

Converge FeatureSupported
Custom Events
Filters
Server-side Conversions

​
Event Mapping

Events are not automatically mapped, you need to configure the mapping of the Converge Event Spec to your Twitter events manually. We recommend the following mapping to the Event Type:

Converge Event NameTwitter Event Type
$page_loadPage view
Viewed ProductContent view
Added To CartAdd to cart
Started CheckoutCheckout initiated
Added Payment InfoAdded payment info
Placed OrderPurchase

Was this page helpful?

TikTok AdsGoogle Analytics 4