Which blog posts generate leads: how to see it in GA4

See which blog posts generate leads in GA4: how to mark the form as a key event, read the landing page report, find the posts that helped before the conversion and know the limits of this reading.
Written with AI, reviewed by humans

In this article

See how your brand shows up in AI answers

Book a demo and find out what to fix first, with a GEO specialist.

Book a demo

Reading time: 10 minutes

To see which posts generate leads in GA4, mark the form submission as a key event and open the landing page report. The Key events column then shows the posts that open visits with a contact. For the post read earlier, however, use an exploration with a segment.

In short

  • To see the posts that generate leads in GA4, the form submission must be a key event. So mark it before you analyze, because the mark does not apply to the past.
  • The GA4 landing page report shows the posts that open a session with a lead. In other words, it is the first touch of the session, not of the reader.
  • Attribution reports credit channels, not posts. So to find the post that helped earlier, use an exploration with a segment.
  • With few leads, read the result as a clue. Also, adjust the retention of explorations, which keeps only two months by default.

What does GA4 count as a lead?

GA4 counts as a lead only the action you mark as a key event. According to the Google Analytics help, a key event measures an action that is particularly important to the business. Also, any collected event can become one. For forms, the list of recommended events includes the name generate_lead.

Google recommends that name, but reading the posts that generate leads in GA4 only needs one key event per lead. Firing the event on the form is the step before this one. Therefore, the walkthrough for firing the form event and tagging links with UTM is left for a separate guide.

Before you look at the numbers, exclude internal traffic from GA4. After all, your team’s form tests become leads and distort the reading by post.

The walkthroughs in this text follow the official Google help. However, we did not run them in a real GA4 account, and menu names may change in your interface.

Posts that generate leads in GA4: arrows link each post to the landing page and the contact form

How do you mark the form as a key event?

Mark the form event as a key event in Admin. According to the Google help, you need the Editor role to mark an event that already exists. To create a new event, however, you need the Marketer role.

  1. Open the events. First, in Admin, under Data display, click Events.
  2. Find the event. Then, in the Recent events tab, look for the form event. If it has not appeared yet, click Create event and type the name.
  3. Click the star. Next, click the star icon next to the event. When you create an event, turn on the toggle next to Mark as key event.
  4. Choose the counting. Finally, when you create the event, choose the Counting method, as the help says.

The GA4 API reference describes two options: count every occurrence, or count at most once per session per user. For a form, then, the second avoids duplicating a contact who clicks Submit twice. The interface help does not list these options, and we did not check the labels on screen. This choice is ours.

The mark applies from now on. It does not change the history, and the event takes up to 24 hours to appear in standard reports. So mark it before you start to analyze. The limit is 30 key events in standard properties.

How do you see which posts generate leads in the landing page report?

Open Reports, then Engagement and Landing page. According to the report help, the dimension holds the first page of each session. Because the dimension is session-scoped, the Key events column of the GA4 landing page report shows the leads from sessions that started at each post. This reading is ours.

  1. Choose the event. First, open the All events menu and select your lead event. This way, the column stops adding up other key events.
  2. Filter the posts. Next, type the folder where your posts live in the search bar above the table. The help uses the example “/store”.
  3. See the source. Then add the secondary dimension Session source / medium, because it shows where the visits to each post came from.
  4. Compare with sessions. Finally, divide Key events by Sessions. This rate is our calculation, not a column of the report. Explorations have the Session key event rate, which counts sessions with an event, and ours counts events.

A post with many sessions and few leads, therefore, needs a better invitation in the text. A post with few sessions and several leads, on the other hand, deserves more traffic. To find out whether the reader reaches the invitation, see scroll depth in GA4.

If the form sits on a contact page, the lead should appear there in the Pages and screens report. This happens because, according to the list of automatically collected events, every event carries the page_location parameter by default. This deduction is ours. So the GA4 landing page report is the way to find the post.

How do you see the posts that generate leads after an earlier read?

Create an exploration with a segment of users who generated a lead and look at the pages they visited. According to the segment builder, a user segment with a purchase event returns all the activity of those people in the queried period. So the same applies to the posts that generate leads in GA4.

  1. Open the exploration. First, click Explore and choose the Free form template.
  2. Create the segment. Next, click the plus symbol beside Segments and choose to create a custom segment. In the top panel, select the user segment type.
  3. Set the condition. Click Add new condition and enter the name of your lead event. Use the scope Across all sessions. Then click Apply.
  4. Build the table. In Variables, import the dimension Page path + query string and the metrics Active users and Views. Then put the dimension in Rows and the metrics in Values.
  5. Apply the segment. Finally, apply the segment and use Filter to restrict the path to the posts folder.

The table lists the posts seen by people who generated a lead, in any session of the period, including after the lead. For a specific post, create a user segment with a sequence, under Add sequence. Step 1 is the view of the post, and step 2 is the lead event. This setup is ours. Then select Indirectly followed, because the help says this type accepts other events between the two steps.

This result shows association, not cause. After all, someone who reads several posts may already be close to hiring. Also, this recipe is our setup from the documentation, and we did not run it in a real account.

First touch or assist: which reading should you use?

Use each reading for one question. The GA4 landing page report shows the post that opened the session with a lead. The first_visit exploration shows the post of the reader’s first visit, while the segment shows the posts read before converting. The totals, therefore, do not add up. The first reading comes straight from the GA4 landing page report.

QuestionWhere to see itWhat it counts
Which post opened the lead’s visit?Landing page reportFirst page of the session
Which post first brought the reader?Exploration with first_visitPage of the first visit
Which posts did they read before converting?Exploration with a segmentPages viewed in any session

For the second row, use the lead segment from the previous section. GA4 fires first_visit the first time a user visits the site, and this event carries the page_location parameter. Then filter the exploration by the Event name first_visit. This way, the Page path should show where each lead entered. The help does not confirm that the dimension reads the page_location of that event. This recipe is our setup, and we did not run it in a real account.

The help’s table of dimensions lists the first user’s source, but not a first user’s landing page. So first_visit is the workaround. However, people who entered outside the stored period do not appear.

Do attribution reports show the posts that generate leads in GA4?

No, because GA4 attribution reports credit channels, not posts. The report that compares attribution models splits the credit by channel group, source and medium, source, medium or campaign. This way, the post that helped stays inside the channel, such as organic search.

The attribution paths report shows which channels start, assist and close key events, in paths of up to 20 touchpoints. It does not split by page either.

According to the attribution settings, the chosen model does not change the first user dimensions or the session dimensions. The same text defines the lookback window, which decides how long a touchpoint receives credit. The default is 90 days for most key events. To understand the models, see the guide to the attribution model.

What are the limits of this reading?

Five limits weigh most when you read the posts that generate leads in GA4, and all of them apply to any blog. Some are solved with a setting, while others need care when you interpret. So check each item before you show the numbers to the board or the client.

  • Short retention: according to the explorations help, properties keep two months of data by default. According to the data retention help, this affects only explorations and funnels, not standard reports. To extend it, open Data collection and modification and then Data retention, in Admin.
  • Only from now on: the marked event does not change the history. So the reading starts when you marked it.
  • Person becomes device: on a website, the device ID comes from the client ID of the _ga cookie. So someone who reads on the phone and submits on the laptop counts as two users, which is our deduction.
  • Sampling: the explorations help says they may use sampled data above 10 million events. In that case, the exploration icon changes from green to yellow.
  • Association, not cause: the post that appears before the lead may not have influenced the decision.

How do you decide with few leads?

With few leads per post, treat the list as a clue, not a ranking. Add up a long period and group the posts by topic. In the GA4 landing page report, for example, filter each topic’s folder and add up the leads. Finally, compare only posts with similar sessions.

Instead of betting on a single post, look for patterns, such as a topic that always appears among the posts that generate leads. GA4 also cannot see what happens outside the site, such as a colleague’s referral or an AI answer without a click. For that gap, ask the lead, as in the guide to “how did you hear about us?”. Then cross the answer with the CRM, as shown in content marketing ROI. To separate the leads that arrive from AI assistants, see AI traffic in GA4. The full list of indicators is in the digital marketing KPIs.

Want to know how your brand shows up in AI answers today?

Book a demo and see how your brand shows up in AI answers, with support from a GEO specialist.

Main sources

About this articleWritten with AI and reviewed by humans, with verified sources. Found something out of date? Write to the NotHuman team.

Get new NotHuman articles by email

By subscribing, you agree to receive blog articles by email and to the Privacy Policy. Unsubscribe any time.

Keep reading

Demo

Want to know how your brand shows up in AI answers today?

Book a demo and see how your brand shows up in AI answers, with support from a GEO specialist.

Book a demo

Your privacy

We use necessary cookies to make the site work and Google Analytics and Microsoft Clarity statistics cookies to improve our content. You can decline the statistics ones; in the EU, UK and Switzerland they are only turned on after you accept. Cookie Policy.

Cookie preferences

Cookie Policy