GR8 Faucet Script: Manage Site Scripts

These instructions apply to GR8 Faucet Script 70.1.73. The controls described are in your own installation; this public guide does not grant administrator access.

Content → Ads → Site Scripts stores named public snippets such as Analytics, Tag Manager, popup networks and pixels. It is shared across the installation. It is not a server API-key integration or automatic consent manager; third-party code can read and change the public pages where you enable it.

Get The Correct Public Snippet

Sign into the intended provider account and choose the registration for this project and hostname. Obtain its public website-installation snippet, not an API secret or another project’s tag. Check existing scripts and templates first to avoid installing the same tag twice. Resolve applicable privacy and consent requirements before enabling tracking; selecting All Public Pages does not itself implement consent.

Open Google Analytics

Read Google Analytics Website Setup

Open Google Tag Manager

Read Tag Manager Container Installation

Official setup destinations checked October 5, 2026 (America/Chicago). This installation’s Document Head hook is near the end of head, not immediately after its opening; Body Start is immediately after the opening body. Follow the provider’s current requirements and verify compatibility rather than assuming exact snippet placement.

Create A Disabled Script

1. Choose Add Script. Enter Script Name and Script Type. Use the project’s proper name for a project-specific registration.

2. Choose Public Pages: All Public Pages, Faucet Only, Content Pages Only or Shortlink Callback Only. Admin, installer and Help pages do not receive these snippets.

3. New scripts remain Disabled while you prepare and verify their code. They are added at the end of the current execution order.

4. Choose the Initial Provider Code Injection Point and paste its public snippet. Document Head, Body Start and Body End are separate fragments, not interchangeable fields. Choose Create Script.

5. Check the notice, Runtime badge and Enabled switch. Edit changes the metadata; Code opens one fragment editor. Use the Code menu to add the provider’s other required fragments, then Save Code.

Enable, Verify Or Pause

1. When the configuration and privacy setup are ready, use the intended row’s Enabled control. Paused Globally means the installation-wide pause still prevents enabled rows from running; enabling a row does not resume the installation.

2. Check the intended public page and the provider’s own verification console. Saving or an Enabled badge does not prove event delivery; avoid duplicate tracking and do not use a claim or payout simply as a script test.

3. Pause All Scripts requires confirmation and immediately suppresses every site script without changing individual Enabled values. Banner placements are unaffected. Resume Scripts reactivates every individually enabled script, not just the row you are viewing.

4. All Scripts clears discovery state. The counted footer keeps Previous and Next visible, including an empty table or search result.

Set Execution Order

Use Up and Down before Edit to move a script by one position. This is execution order, not random rotation: place a required library before the script that depends on it. Clear Search and return to the default order before moving a row, so its neighboring scripts are visible. Boundary controls are disabled. If another administrator changes the configuration, reload before trying again.

Removal And Recovery

Delete permanently removes the named script and all its fragments after confirmation. Keep a copy first. An empty fragment saved with Save Code removes that fragment. If code validation fails, the previous content is kept; correct the named error rather than repeatedly saving. Remote scripts are trusted provider content, not sandboxed or guaranteed safe by syntax validation. Nothing in this form transfers passwords, creates a provider account or proves provider delivery.

Read Ad Placements Help