How to track custom (click) interaction events in the Qubit TMS OpentagFollow

Custom Event Pixel Tag [a.k.a Conversion Report]

This tag can be implemented via Opentag to capture non product/transaction based events such as button clicks that are not covered by the basket tags e.g. A download of a PDF Brochure, an interaction with a feature onsite that doesn't reload the page or redirect to a new URL. Play Video button etc


Login in to your Qubit Opentag Dashboard.

1. Locate the first container on which you wish to install the 'Conversion Report' Tag. This will be any container that fires on the page that the customer is able to commit to the event or interaction you are attempting record, such as a click of a button to download a PDF or Play a video.

2. Once located select the option '+Add New Script'

3. Find the VisualDNA Script library by selecting 'Web Analytics' within the category selector on the top left of the screen underneath 'Tag Categories'

4. Scroll down to Visual DNA and click.

5. This will reveal a list of our templates to the right of the screen. Select the template entitled: 'Conversion Report' and scroll down to see the parameters that will need populating.

6. Select the Drop-down beside the API Key value and choose 'Add New Custom Variable' This will open a new popup.

7. Under 'Variable Type' make sure the 'Hard coded value' is selected.

8. In the 'Value' box, paste in your unique VisualDNA API Key which is supplied by your VDNA Account Manager.

9. Select 'Save Variable'

10. The "Extra Data" parameter should be assigned a string. The format/value of the string should be agreed with VisualDNA in advance on a partner­ by ­partner, conversion­ by ­conversion basis. If no extra data is available, then an empty string should be assigned to that parameter.

11. Conversion ID - This value is produced when you setup the conversion based segment within the WHY platform. Once you have named your conversion when adding the new segment in WHY you will be able to save this and then click the '</>' next to that segment when it is listed in the left navigation. Within the code there will be a parameter called &id=

Everything in purple after that value will need to be copied and pasted into the Conversion ID parameter  e.g.


<!-- VDNA Conversion Pixel -->
(function(){function e(){(new Image).src="//"+Math.random()}if(window.addEventListener)
{window.addEventListener('load',e,false)}else if(window.attachEvent){window.attachEvent('onload',e)}})()
<img width="1" height="1" alt="" aria-hidden="true" src="//;id=campaign_action_501c5c15-401a-49a0-afb9-9f394aee92f7" />


12. To get this value into Qubit as a parameter select the Drop-down beside the Conversion ID value in Opentag and choose 'Add New Custom Variable' This will open a new popup.

13. Under 'Variable Type' make sure the 'Hard coded value' is selected.

14. In the 'Value' box, paste in the unique conversion id equivalent to the purple code above.

15. Select 'Save Variable'

16. Click to expand the '+ Advanced Features' section and click on the third tab to the right 'Dependencies'

17. You will need to add two dependencies to this tag. First add the VisualDNA Analytics tag to the right list of dependencies (you will need this tag installed across the site as per the instructions here:

18. The second dependency will be a piece of code that defines when this conversion/interaction event has taken place. If there isn't a suitable piece of javascript that defines this then you will need to speak to your Qubit Account Manager on how to proceed and define this action within Opentag.

19. Once the above steps are complete select 'Save Script'. You may need to define the Tags name before it allows you to proceed.

20. You will now be redirected back to the dashboard where you will see your tag listed within that container. Top copy this across to the other containers click the cog to the right of the tag listing and select 'Copy to' 

21. Select the next container and confirm the copy by pressing the 'Copy' button. The tag will now appear listed in the second container.

22. Repeat this process until you have all the containers covered where the conversion/interaction event may happen.

23. You will be prompted to 'Commit' the changes to each container by pressing the green 'Commit' button. Please test using your usual procedures before pushing fully live. 



Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk