How to insert JavaScript codes in articles?


Traffic tracking and traffic analysis codes do not differ in the way they are inserted. Such code can be a script that counts traffic based on Google Analytics, an internal WhitePress statistics system, or another proprietary solution. It is getting more popular that the code is to enable remarketing activities.
All websites run on the basis of an HTML editor. To correctly place the javascript code in the body of the article, you must first switch to the HTML editing mode, i.e. the document source.
Depending on the content editor used in the portal administration panel where the article is published, the buttons may look different. Sometimes you may need to find this option in the editor's menu or by right-clicking.
After switching, we should see the HTML tags. We don't need to understand them, just make sure that there are acute <> brackets that will surround our text:
The last step is to paste the traffic tracking code, preferably at the very end of the article.
Correctly pasted code looks like this:
After inserting the code, we can turn off the HTML source and save our article. If everything went well, the traffic tracking code will be included in the article body, and the statistics should count.
Possible problems that should be consulted with the person technically responsible for the website:
- Code pasting is disabled in the editor (the appropriate parameter must be set in the editor configuration).
- The editor does not have any source switching button (an appropriate parameter must be added in the editor configuration).
- After saving, the code is not inserted in the article (perhaps the editor has a restriction in placing <script> tags in the content. You will need to change the options in the editor allowing for placing these tags).
- After saving, the code looks the same, the quotation marks are changed (the editor may have the function of replacing quotation marks and angle brackets with entities that are only printable, but do not fulfill any function. You should disable the parameter responsible for converting special characters to entities in the editor configuration).