How to Add a Custom Google Analytics Tracking Code in Weebly

Google Analytics gives Weebly site owners a clearer view of who visits, what pages attract attention and which marketing activities lead to useful actions. The standard dashboard is helpful, but a custom Google Analytics tracking code can provide more control over page views, events, campaigns and conversions.

For an Australian business or blog, accurate measurement is especially useful when visitors arrive from local search, Google Business Profile listings, Facebook groups or seasonal campaigns. Whether your audience is in Sydney, Melbourne, Brisbane or a regional town, the installation process is straightforward once you know where to find your Google Analytics 4 code and where Weebly accepts it.

Choose the right analytics setup

Google Analytics 4, usually called GA4, uses a Measurement ID that begins with G-. This replaced the older Universal Analytics property, whose tracking IDs generally began with UA-. If you are creating a new property, choose GA4 rather than looking for an outdated Universal Analytics code.

There are two common ways to add analytics to Weebly. The first is to paste Google’s global site tag directly into the site-wide header area. The second is to use Google Tag Manager, which places one container on your website and lets you manage analytics tags from Google’s platform. Direct installation is usually easier for a small blog, portfolio or local service website. Tag Manager is more suitable when you need several marketing tags, custom events or advertising pixels.

Before adding anything, confirm that you have access to the correct Google Analytics property. A business may have separate properties for a main website, an online shop and a test domain. Copying the code from the wrong property can produce confusing reports, especially if the same owner manages several websites.

It is also worth deciding what you need to measure. Basic tracking can record visits and page views. A more customised setup may track contact-form submissions, outbound clicks, downloads, video plays or important buttons. Defining these actions first prevents your Weebly website from filling up with unnecessary tracking code.

Find your GA4 measurement ID and tag

Sign in to Google Analytics and open the property connected to your website. Select the administration area, choose the relevant data stream under Data collection and modification, then open the web stream. Google displays a Measurement ID in the format G-XXXXXXXXXX. Keep this ID available because it identifies the property that should receive your Weebly data.

From the web stream details, use the option to view tagging instructions or install the Google tag. Google generally provides a script similar to the following:

<!-- Google tag (gtag.js) -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXXXXX"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());

  gtag('config', 'G-XXXXXXXXXX');
</script>

Replace both examples of G-XXXXXXXXXX with your own Measurement ID. Copy the complete snippet rather than only the ID. The script loads Google’s tagging library, creates the data layer and sends information to the selected GA4 property.

Google’s interface can change slightly, so the labels may differ from those shown above. The important parts are the web data stream, the Measurement ID and the installation instructions for the Google tag. Do not copy code from an unrelated tutorial if it contains another person’s ID.

Add the code through Weebly

Log in to Weebly, open the website editor or dashboard and look for the area used for site-wide header code. Depending on the account layout and editor version, this may appear under Settings, SEO or Advanced settings. A field called Header Code, Footer Code or Site Header is the correct place for the GA4 script when the code needs to load across the entire website.

Paste the script into the header field without changing its structure. Header placement allows the tag to load on each page and gives Analytics a better chance of recording visits when someone leaves quickly. Avoid placing the code inside a text element, an Embed Code element intended for visible page content or a single page section, since that can restrict tracking to one location.

Save the settings and publish the website. Saving the code in the editor is not always enough; the live, published site is what visitors and Google Analytics can access. Open the public version in a private browser window after publishing, then visit two or three pages to create fresh activity.

If you are adding another site enhancement, keep the header organised. For example, a countdown campaign can be measured alongside the site-wide tag, and a guide to add a countdown timer can help you create a time-sensitive promotion without placing analytics code inside the timer itself. Each function should have a clear role so that future editing remains manageable.

Test live data and custom events

GA4 usually shows new activity in the Realtime report within a short period. Open your published Weebly site in a private window, accept any required consent notice and browse a few pages. In Analytics, check whether your visit appears in Realtime. You can often see the page title, approximate location and traffic source, although information may be limited by browser privacy controls.

If no activity appears, check the public page source or use your browser’s developer tools to search for gtag or your G- Measurement ID. Confirm that the code was placed in the site-wide header field, that the site was published and that the ID matches the intended property. Ad blockers, consent settings and browser privacy protections can prevent a test visit from appearing, so test with more than one browser where practical.

Custom events can give your reports more meaning. A regular page view tells you that someone loaded a page, while an event can show that a visitor clicked a phone number, downloaded a PDF or completed a contact form. GA4 can automatically collect some events, but important business actions may need additional configuration through Google Tag Manager or a carefully written event script.

For example, an Australian tour operator could track clicks on a “Request a quote” button separately from ordinary page views. A Melbourne photographer might measure gallery downloads, while a Brisbane tradesperson could track taps on a mobile phone link. Name events clearly, such as contact_form_submit or brochure_download, and keep naming consistent so reports remain easy to interpret.

A preloader or animation can affect when visitors see a page, so test it after installing analytics. If your design uses a visual loading screen, review this guide to add a custom preloader and then confirm that the page still loads the GA4 tag correctly. Decorative effects should never prevent the tracking script, navigation or accessibility features from working.

Respect privacy and read the reports

Analytics settings should match the information you tell visitors about. Australian website operators need to consider the Privacy Act, the Australian Privacy Principles and any obligations that apply to their organisation or industry. The appropriate approach can vary according to business size, the information collected, advertising activity and the location of visitors.

Update your privacy policy so it explains the use of analytics, the types of information collected and the purpose of processing. If your website uses cookies or similar technologies, consider whether a consent banner or preference tool is appropriate for your audience and configuration. A consent platform should be configured so that analytics does not load before permission where your obligations require that approach.

Avoid placing personally identifiable information into page URLs, event names or Analytics parameters. A form submission should be counted as an event, but a visitor’s name, email address, phone number or message should not be sent to Google Analytics. Review referral exclusions and internal traffic settings too, particularly if several staff members regularly visit the site from the same office.

Australian reporting can be easier to interpret when you use the correct time zone and currency settings. Set the property’s reporting time zone to the location that best represents your business, such as Australian Eastern time for a company operating around Sydney, Canberra or Melbourne. Remember that daylight saving can affect AEST and AEDT comparisons, so do not mistake a one-hour shift for a sudden audience change.

Use the reports to improve decisions rather than chase every fluctuation. A local café may compare visits from “near me” searches with calls or directions, while an online seller may study product pages visited by people from Perth, Adelaide and the Gold Coast. If you promote a campaign through an Australian community group or use informal wording such as “arvo special”, add consistent campaign parameters so the resulting traffic can be identified.

You can also review resources and examples from independent web publishers such as Kizzy Online when considering how different sites present content, navigation and promotional features. The design lesson is useful, but keep your own analytics configuration focused on the actions that matter to your website.

Once the tag is working, check Realtime data again after making major changes to the theme, navigation or header code. Keep a private copy of the current script and record the date it was installed. This makes troubleshooting easier if a future Weebly edit, template change or third-party widget affects tracking.

Add the GA4 script to your Weebly site, publish it and verify a live visit before relying on the reports. Then define a small set of meaningful events, document your privacy approach and review the data regularly. A clean setup will help turn visits from Australian searchers and customers into practical insights for better pages, campaigns and conversions.