X Ads (Twitter Ads)

​

Overview

• Includes support for passing User Parameters (email and phone number)
• Includes support for Dynamic Product Ads Campaigns

​

Installation Instructions

Set up tracking in Twitter Ads

1. Navigate to your X Ads account and choose Tools > Events Manager.
2. Copy your X Pixel ID
   1. If you already have an events source, at the top of the page, find the ‘X 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 Pixel ID when you are done.
3. Go to X Ads > Tools > Events Manager and click on the Create Event button.
4. Give your event a name, e.g. ‘Placed Order’ when you are setting up a purchase conversion.
5. Pick a X event type, e.g. ‘Purchase’. You can find a suggested mapping of Converge to X Ads event types below.
6. Configure your attribution settings and click on Next.
7. Choose the ‘Define event with code’ setup method and click on Next.
8. Click ‘Save’ to finish the setup.
9. You can now find the event in the Events table in the X Ads Events manager. Under the event, the ID is composed as tw-{pixelID}-{eventID}. Copy the eventID save it for the Converge destination configuration.

Repeat the steps 3-9 above for all the conversions you want to track in X Ads.

2. Set up your destination

10. In the Converge sidebar, click on
    Event streams
    and then click Create new Destination.
11. Select the X Ads (Twitter Ads) destination and click Next.
12. Give your destination a name (e.g. X Ads Destination) and click Next.
13. Fill in the Pixel ID you copied from X Ads and click Next.
14. Click on
    Add new mapping
    and select Placed Order as the source event.
15. In the Forward As value enter eventID you saved for the purchase conversion in X Ads.
16. Select Client as the Forwarding Mode and click Next.

Repeat the steps 14-16 above for all the conversions track in X Ads

17. Select the sources you want to forward events from, then click Next.

This is a client-side destination, meaning that only client-side sources can be used with this destination. You can still select server-side sources but the events will not be send to AppLovin.

18. Review any issues and click Submit.

​

Modify your Content ID

1. Navigate to your X 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

​

Converge functionality

​

Event Mapping