Integrations
Twitter Ads
An introduction to the Twitter Ads Destination
Overview
Connection Type:
Client-side
- Includes support for passing User Parameters (email and phone number)
- Includes support for Dynamic Product Ads Campaigns
Installation Instructions
This is a client-side-only connection, meaning that you will need to be tracking all events client-side (including
Placed Order
) for this connection to work properly. 1. Set up the Converge Connection
-
Navigate to your Twitter Ads account and choose Tools > Events Manager.
-
Copy your Twitter Pixel ID
- 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
) - If not, you will be prompted to create a new event source, follow the instructions and copy the ID when you are done.
- If you already have an events source, at the top of the page, find the ‘Twitter pixel’ section and copy the ID. (e.g.
-
In the Converge dashboard, under Connections, click
Create New Connectionand fill in your Pixel ID. -
See below for instructions on how to configure your conversion events.
2. Create your conversion events
- In the Twitter Ads > Tools > Events Manager, click on the Create Event button.
- Give your event a name, e.g. ‘Placed Order’ when you are setting up a purchase conversion.
- Pick a Twitter event type, e.g. ‘Purchase’. You can find a suggested mapping of Converge to Twitter Ads event types below.
- Configure your attribution settings and click on Next.
- Choose the ‘Define event with code’ setup method and click on Next.
- Click ‘Save’ to finish the setup.
- 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 theeventID
into the ‘Twitter Event IDs’ section of the Converge connection configuration.
Repeat the steps above for all the events you want to report on in Twitter Ads
Once you have installed your Converge Connection, you should pause or remove all existing Twitter Ads tracking. Leaving these on will lead to duplicate tracking.
Converge functionality
This integration supports the following Converge connection functionality.
Converge Feature | Supported |
---|---|
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 Name | Twitter Event Type |
---|---|
$page_load | Page view |
Viewed Product | Content view |
Added To Cart | Add to cart |
Started Checkout | Checkout initiated |
Added Payment Info | Added payment info |
Placed Order | Purchase |