New Twitter Universal Website Tag

[ahrasch]

Hi,

a few weeks ago Twitter created a new tag which is able to track pageviews in addition to only conversions (as the existing Twitter tag does).

The code looks as following:

<!-- Twitter universal website tag code -->
<script>
!function(e,n,u,a){e.twq||(a=e.twq=function(){a.exe?a.exe.apply(a,arguments):
a.queue.push(arguments);},a.version='1',a.queue=[],t=n.createElement(u),
t.async=!0,t.src='//static.ads-twitter.com/uwt.js',s=n.getElementsByTagName(u)[0],
s.parentNode.insertBefore(t,s))}(window,document,'script');
// Insert Twitter Pixel ID and Standard Event data below
twq('init','12345');
twq('track','PageView');
</script>
<!-- End Twitter universal website tag code -->

Do you plan to include this new tag in the tag marketplace in the near future or do I have to use the Tealium Custom Container to implement this?

Greetings,

Andreas

[kathleen_jo]

Excellent question @ahrasch. Let me see what I can find out. Stay tuned...

[kathleen_jo]

Hello again @ahrasch. We are aware of the update to the Twitter tag and are working diligently towards a resolution. In the interrim I would suggest that you do use the Tealium Custom Container as we do not have a completion date established for this update.

Would you like me to ask your Account Manager for assistance as well? Please let me know. I look forward to your reply. 

[ahrasch]

Hello @kathleen_jo,

I think I managed to implement this with the Custom Container on my own. However, after doing this I realized that although the calling code and the adress of the script to load of the new Twitter tag looks different, the content of the script and the url of the actual Twitter pixel is the same.

This may change in the future, but for the moment it seems that just using the Twitter Conversion tag from the marketplace and loading it on every page is doing the same pixel call than the new tag.

[kathleen_jo]

Thank you for letting us know about this behavior @ahrasch. Great information. I will let the appropriate teams know.

[tom_butkevich]

Are there any updates to the template for the new Twitter Universal tag?

[chris_horne]

@tom_butkevich,

It is still not available; however, engineering is working hard on getting this out as soon as possible and it should be available in the very near future. 

[steve_fernandez]

I'm seeing the Twitter Universal Website Tag in the marketplace now, so I assume it's complete and ready to be used. However, when I try to implement, I don't see that it's calling the analytics.twitter.com pixel. I have not examined the profile to see if anything is out of place. I wanted to use this universal tag for both pageview and purchase functions instead of having to use two different twitter tags.

[meng_lim]

@steve_fernandez,

The new Twitter Universal Tag is using a new library (https://static.ads-twitter.com/uwt.js).

I believe you will need to get a new code snippet to replaced the old one that still uses (analytics.twitter.com).

[adam_wolfers]

We have some configuration docs on the way.

In the mean time, I can help you get these two events to work.

You'll need event triggers set up in your mappings to get the tag to fire. One for the Page View event and one for the Purchase event. Let me know if event trigger mappings are new to you, and if you need more details on setting these up.

The Purchase event requires these parameters: content_ids, content_type, event_value, and currency

If you have the E-Commerce extension configured, it will fill in all of those Purchase event params except for content_type. You'll want to set that to "product".

[kathleen_jo]

Hello @ahrasch, @steve_fernandez, and @tom_butkevich. Please find the tag documentation and data mappings for the Twitter Universal Website Tag here:

https://community.tealiumiq.com/t5/Tags/Twitter-Universal-Website-Tag-Basic-Configuration-and-Data/t...

Thank you for your patience and let us know if you have any further questions.