← Blog
5 min read

Website analytics in Zynta: GA4, Search Console and GTM

A browser window under a magnifying glass, surrounded by a bar chart, a ranked list and tags with one check mark, in green on a light background.

Website analytics in Zynta answers a question that social media metrics can't: did your social accounts send people to the site, and is the site set up to measure it? You connect the brand's Google account and pick the GA4 property and the Search Console site. From there, Zynta reads the last 90 days. Below I cover what shows up on screen and how to connect; the limits come at the end.

The problem: social on one side, the website on the other

Social media reports usually stop at reach and engagement. When a client asks "did this bring people to the site?", the answer means opening Google Analytics and hoping the links had UTMs. And nobody checks whether Tag Manager is measuring correctly until the day the numbers disappear.

I wanted the website in the same dashboard as the social accounts, so the conversation with the client covers both sides. I wrote about what to measure in social media analytics: what to track.

What does Zynta show?

In Insights, the Site tab has three blocks.

Site visits (Google Analytics): sessions, users, new users, engaged sessions, engagement rate, key events, sessions per day, channels, source and medium, plus a table of traffic from social networks that separates what arrived with UTMs.

Google Search (Search Console): clicks, impressions, average position, clicks per day, top queries and top pages.

Site tags (Google Tag Manager): the container audit, covered in the next section.

Every day, Zynta stores the top 50 queries and pages from Search Console and the top 200 source and medium combinations from GA4.

The Google Tag Manager audit

The Site tags (Google Tag Manager) block reads the container and flags problems. Zynta checks the published version of the container, pending changes in the workspace, the GTM IDs that appear on the site's home page and the GA4 measurement IDs. Possible findings include:

  • a container that isn't on the site;
  • GA4 events without the Google tag;
  • a duplicate Google tag;
  • a connected GA4 property that isn't in the container;
  • Universal Analytics tags;
  • tags with no trigger;
  • use of document.write;
  • missing consent settings;
  • paused tags;
  • unused triggers and variables;
  • unpublished changes.

It also lists the platforms the container loads. The audit is read-only: Zynta never touches your tags.

How to connect, step by step

  1. Open Connections and find the Google Analytics + Search Console card.
  2. Click Connect and approve on Google's consent screen. The permissions requested are read-only access to Analytics, Search Console and Tag Manager.
  3. Choose the GA4 property and the Search Console site, then click Save. Zynta reads the last 90 days.
  4. Open Insights and go to the Site tab.
  5. In the Tag Manager block, click Pick container and then Audit.

After the first read, Zynta refreshes the last 3 days of GA4 and the last 7 days of Search Console every day, because those numbers change after they're published. Only the brand owner or an editor can change the connection. If you connected before the Tag Manager audit existed, reconnect to grant the new permission.

How much does it cost?

Today none of this spends credits: connecting, reading the first 90 days, the daily refresh and the Tag Manager audit.

The limits

  • Read-only. Zynta changes nothing in your Google account.
  • The GTM audit only looks at the home page of the site to find the IDs.
  • Search Console has a delay of two to three days, and that comes from Google.
  • Users are summed per day: someone who comes back on different days counts more than once.
  • The audit has a usage limit: up to 2 audits per minute per brand.

Frequently asked questions about website analytics in Zynta

What is website analytics in Zynta Flow?

It's the Site tab in Insights, which shows a brand's Google Analytics 4 and Google Search Console data next to its social media metrics. It also audits Google Tag Manager and lists configuration problems, always with read-only permissions.

Does Zynta change anything in my Google Analytics or Tag Manager?

No. The connection asks only for read-only permissions for Analytics, Search Console and Tag Manager. The GTM audit points out problems, such as a duplicate tag or an unpublished change, but the fixes in the container stay with you.

How much history does Zynta read from GA4 and Search Console?

When you save the connection, Zynta reads the last 90 days. After that, it refreshes the last 3 days of GA4 and the last 7 days of Search Console every day, because Google keeps adjusting those numbers in the days after the data is collected.

What does the Google Tag Manager audit check?

It checks whether the container is on the site and looks for a duplicate Google tag, GA4 events without the Google tag, Universal Analytics tags, tags with no trigger, missing consent settings, paused tags, unused triggers and variables, and unpublished changes in the workspace.

GA4 directly or through Zynta: what's the difference?

In GA4 you get every report, but without your social media next to it. In Zynta, the website data and the brand's social metrics sit in the same dashboard, which makes it easier to show a client whether social sent people to the site.

Do I need UTMs on my links to see traffic from social media?

They help a lot, because the table of traffic from social networks separates what arrived with UTMs. Without UTMs, part of your visits can show up grouped under other sources in GA4, and it gets hard to tell which network they came from. In Zynta, choosing a HubSpot campaign on a post applies its UTM when it publishes.

Put this into practice

Want to see your brand's website and social accounts in one dashboard? Start your 30-day trial.

Start your 30-day trial