JavaScript Vs Iframe Within STG

STG supports all forms of online event marketing activities by giving administrators the opportunity to add various forms of tracking, remarketing or conversion pixels/codes/tags into your event forms.

This includes being able to add various tag types including JavaScript, Iframes, image pixels, Google and social scripts. We have also hard-coded areas to more easily manage Facebook and Twitter conversion activity which simply require the unique ID to be added into the event form in order to fire. 

Please be aware that STG readily supports JavaScript and would strongly suggest that clients utilise this source format to administer their marketing activities. Whilst Iframes can be added into the system for the same reason, you can often encounter difficulties imposed by internet browsers especially if they are going to a different domain. Potential issues which can arise include:

- They can cause accessibility problems.
- Some browsers will often display them incorrectly or even serve them blank.
- They cannot be seen by many hand-held devices.
- It can lower your SEO for the site.

Keep in mind that browsers impose these difficulties with Iframes in order to protect the end-user from click-jacking attacks and from unknowingly passing information such as their IP to an unidentified third-party.  

Here is an example of what an Iframe tag:

Any JavaScripts which feature variable attributes within the script will need to be approved and implemented by an STG Developer on your behalf in order for them to fire correctly. These scripts contain phrases such as 'insert event name' or 'insert entry type' within them. 

Any static JavaScripts, which have been created for specific events for example (and therefore contain no variables), can be simply added into the relevant area within your STG console depending on what they are targeting. 

Here is an example of what a JavaScript tag: