Title: Editing the noscript code
Last modified: August 22, 2016

---

# Editing the noscript code

 *  Resolved [monk3](https://wordpress.org/support/users/monk3/)
 * (@monk3)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/editing-the-noscript-code/)
 * I am trying to edit the <noscript> code preview: under the Tracking Tab in your
   settings page so that Piwik can track those visitors with Javascript Enabled 
   in their web browser. However, that field is greyed-out and is not editable.
   
   How can I do this?
 * [https://wordpress.org/plugins/wp-piwik/](https://wordpress.org/plugins/wp-piwik/)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Author [braekling](https://wordpress.org/support/users/braekling/)
 * (@braekling)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/editing-the-noscript-code/#post-5529363)
 * The code in WP-Piwik is not editable, because it is delivered by Piwik itself.
 * What do you want to change in your noscript code?
 * If you like to use your own scrips/ your own noscript code, just disable adding
   it and put your own code in your templates footer file.
 *  Thread Starter [monk3](https://wordpress.org/support/users/monk3/)
 * (@monk3)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/editing-the-noscript-code/#post-5529440)
 * We were wanting to add the code as presented on the Piwik page: [http://piwik.org/faq/how-to/#faq_176](http://piwik.org/faq/how-to/#faq_176).
   It states:
    “You can however configure Piwik to also track users with Javascript
   disabled: to do so, edit the Piwik Tracking Tag <noscript> and change: `<noscript
   ><p><img src="http://piwik-server.com/piwik.php?idsite=1" style="border:0" alt
   ="" /></p></noscript>` Replace with the following: `<noscript><p><img src="http://
   piwik-server.com/piwik.php?idsite=1&rec=1" style="border:0" alt="" /></p></noscript
   >` After making this change and adding &rec=1, visitors with disabled Javascript
   will execute the noscript and will load the piwik.php image and will have their
   traffic recorded in Piwik.
 * Note: the most famous bots will still be ignored with this technique. To force
   Piwik to track all bots, add the parameter &bots=1 to the tracking URL, eg:
    `
   <noscript><p><img src="http://piwik-server.com/piwik.php?idsite=1&rec=1&bots=
   1" style="border:0" alt="" /></p></noscript>`
 * Therefore, that is what we were attempting to do, according to their well-written
   instructions.
 * Apparently, your plugin is not concurrent with the apps instruction set, and 
   at the least is lacking in adequate instruction.
 *  Plugin Author [braekling](https://wordpress.org/support/users/braekling/)
 * (@braekling)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/editing-the-noscript-code/#post-5529444)
 * And why don’t you just enable the plugin’s option to add rec=1 in its tracking
   settings?
 * It is named as
 * > Add rec parameter to noscript code
 * and described as
 * > Enable tracking for visitors without JavaScript (not recommended). See [Piwik FAQ](http://piwik.org/faq/how-to/#faq_176).
   > Disabled in proxy mode.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Editing the noscript code’ is closed to new replies.

 * ![](https://ps.w.org/wp-piwik/assets/icon-256x256.png?rev=3529668)
 * [Connect Matomo - Analytics Dashboard for WordPress](https://wordpress.org/plugins/wp-piwik/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-piwik/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-piwik/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-piwik/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-piwik/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-piwik/reviews/)

## Tags

 * [piwik](https://wordpress.org/support/topic-tag/piwik/)

 * 3 replies
 * 2 participants
 * Last reply from: [braekling](https://wordpress.org/support/users/braekling/)
 * Last activity: [11 years, 6 months ago](https://wordpress.org/support/topic/editing-the-noscript-code/#post-5529444)
 * Status: resolved