Twitter Ads (Cloud Destinations)
MetaRouter makes it easy to send your data to Twitter Ads. Once you follow the steps below, your data will be routed through our platform and pushed to Twitter Ads in the appropriate format.
Twitter Ads empower marketers to develop targeted ad campaigns on Twitter based on web visits, followers, engagement, and awareness.
With Twitter Ads, you pay for performance, target keywords, retarget engaged users, and tailor your audiences based on constraints such as language, gender, age, and geography. Plus, Twitter Ads automate new follower acquisition by targeting Promoted Accounts to audiences similar to current followers.
Sending Clickstream data to Twitter Ads will enrich the knowledge base that empowers your marketers with robust data about your user base.
As soon as you activate the integration, MetaRouter can load the Twitter ads script code to start recording page views. If you're already using our platform, you can map Twitter ad conversion IDs to those same event names to track them in Twitter Ads as well.
For e-commerce sites, you won't need to worry about creating custom code to track product browsing and checkout events - those events will be routed through MetaRouter and sent directly to Twitter Ads.
To get started, all you need is your Twitter Pixel ID, which you can retrieve by creating a Twitter Ads conversion tracking website tag.
Note: This connector supports client-side Analytics.js only. You also need to have instrumented MetaRouter inside your website prior to enabling this connector.
Generate your Universal Website Tag
Once you have a Twitter Ads account, choose Conversion Tracking from the Tools drop down menu.
A page will load asking you to accept Twitter Ads' conversion tracking policy. If you agree, check that box and choose Generate website tag for conversion tracking.
You'll be taken to a page with instructions on how to set up your universal website tag, along with a code snippet.
Generate your Universal Tag Pixel ID
If you want to use the universal tag, simply copy your Twitter Pixel ID from the code snippet (identified below).
Reminder: Twitter doesn't recognize custom events, just pixel IDs. Anytime that you
analytics.track(event, properties) an event that represents a Twitter conversion, you need to map the event name on the left to its corresponding Twitter Pixel ID on the right.
Single Event Website Tags
If you want to use Single Event Website Tags, you'll have to map the MetaRouter events to your tags' respective conversion pixel IDs.
If your events don't match the event names you're receiving from MetaRouter that have the Universal Website Tag, you'll want to use the Single Event Website Tags.
Paste your Twitter Pixel ID into the Twitter Pixel ID field in your MetaRouter Twitter Ads configuration, and give your new connection a unique name. Click Save and your pipeline will be activated.
If you’d like to use the Single Event Website Tags, you must map the event names to your Single Event Website Tags’ respective conversion pixel IDs.
You should now be able to refresh your website and see the Twitter Ads pixel firing for page views.
If you're using Single Event Website Tags and have those mapped in, you should see specific pixels fire when triggering your respective events.
analytics.track('Custom Event 1'), based on the input above, would fire the Twitter Ads pixel
pixel1, and so on.