Tracking codes

Add your tracking codes

Open Widgets in your site's editor and find Tracking codes. Paste the ID of each tool you use. If you paste a whole code snippet, Shingle keeps only the ID in it.

• Google Analytics: your measurement ID, which starts with G-. In Google Analytics, open Admin, then Data streams, and choose your website's stream. An old ID that starts with UA- no longer works; Google retired those in 2023.
• Google Tag Manager: your container ID, which starts with GTM-. It's at the top of your workspace in Tag Manager.
• Meta Pixel: your pixel ID, a number of 15 or 16 digits. In Meta Events Manager, choose your pixel; the ID is under its name.
• Google Ads: your tag ID, which starts with AW-. In Google Ads, open Goals, then Conversions, and look at your Google tag. Add a Conversion label to count each form sent on your site as a conversion: it's the part after the slash in your conversion's send_to, as in AW-123456789/AbC-D_efG.

Save widgets makes a new version of your site, with no credits used. Tracking codes run only on your published site, never on its preview, so your own visits while you edit are never counted. Publish to start using them.

Ask visitors first

These tools set cookies and send what visitors do to Google and Meta. In the EU and the UK, visitors must agree first. Turn on the cookie banner and each tool waits for the visitor's answer:

• Google Analytics waits until they allow Statistics.
• Google Ads and the Meta Pixel wait until they allow Marketing. The banner offers Marketing once your site has one of them, or Tag Manager.
• Google Tag Manager waits until they allow either. It tells Google's own tags inside it what the visitor chose, through Google's consent mode. Give any other tag in your container a consent check of its own in Tag Manager.

If a visitor changes their mind later, the tools they turned off stop, and their cookies are removed. A visitor whose browser sends Do Not Track or Global Privacy Control gets none of these tools, banner or not.

Count your leads

When someone sends one of your site's forms, Shingle tells the tools that are running: Google Analytics and Tag Manager get a generate_lead event, the Meta Pixel gets a Lead event, and Google Ads counts a conversion if you added a conversion label. They're told which form was sent, never what anyone wrote in it.

In Google Analytics, mark generate_lead as a key event to see your leads in its reports.

Tag Manager needs your own domain

A Tag Manager container runs whatever you put in it, so Shingle runs it only when your site is on your own domain. At your shinglesites.site address, your other tracking codes still run.

What visitors are told

Your site's privacy page lists the tools you added, what each is for, and links to Google's and Meta's privacy policies. The cookie banner's words name them too, in your site's language.

You need a member role or higher to change tracking codes. Changes you ask Shingle for keep them as they are, and restoring an earlier version brings back that version's tracking codes.