We have a situation where we want to track purchases without a page load event and different URLs. It seems the Universal Website Tag with the Purchase event is what we need, but is firing it on a different URL enough for us to differentiate on the product that was sold?

Additionally, your documentation states:

Please note: The purchase tag must executed independently of ‘PageView’ tag type, otherwise the dynamic values will be overwritten.

What does this mean? Do we need a separate pixel ID for each event? Or would the following code execute successfully?

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

And then after an event on the page, this is triggered later (much like how Google Analytics works):

twq('track','Purchase', {
    //required parameters
    value: '29.95',
    currency: 'USD',
    num_items: '3',
});

Hi,

In general this forum is for Ads API related issues only so we’re unable to help with any tracking pixel related issues. We’d recommend reaching out to the Ads support team at ads.twitter.com/help. There are some historical threads discussing coded events and how our Universal Website Tag works - I’m not sure if you would find a hint of a potential solution but might be worth to search and see if you find any threads like this one: Do individual website clicks and conversion events actually differ or matter to customers? - #9 by jeffcunning

Thanks,

John