Skip to content
Workflow · Track and forecast · Opening soon

GA4 landing page report, week on week

Export your GA4 landing page data for the last two weeks, then compare the latest week with the one before it. The report shows sessions, engaged sessions, key events, change % for sessions, and engagement rate for each landing page.

Early access opens shortly. Check back soon.

Someone typed

“ga4 landing pages by week: compare this week to last week, show sessions, engaged sessions, key events, change %, and engagement rate; status not set, sessions down if over a third drop, low engagement under 40%, otherwise Agrees”

The agent read it as

ga4 landing pages by week: compare this week to last week for GA4 landing page report by week, show sessions, engaged sessions, key events, change %, and engagement rate; status not set, sessions down if over a third drop, low engagement under 40%, otherwise Agrees, with change % for sessions only.

What the agent built

1 step, each one an ordinary Mammoth step you can open and change.

  1. File
    GA4 landing page report by week
    CSV export · 40 rows
  2. Step
    Compare the latest two weeks
    Step 1
  3. Result
    Landing Page Week Compare
    20 rows · 2 flagged
  4. Schedule
    Runs when you say
    Proposed

On the sample files, every step runs and the result has 20 rows.

What you get back

The result of that run, the rows to look at first.

Landing Page Week CompareSample data20 rows
18 agrees1 low engagement1 sessions down
Landing PageStatusThis Week SessionsLast Week SessionsThis Week Engaged SessionsLast Week Engaged SessionsThis Week Key EventsLast Week Key EventsSessions Change %Engagement Rate %
/blog/ga4-guideSessions down4509003396844896-5075.3
/webinarLow engagement30532077821719-4.725.2
(not set)Agrees12311876741094.261.8
/Agrees1,3051,2409969361961845.276.3
/aboutAgrees2522401861762524573.8
/blogAgrees45843032930456526.571.8
/case-studiesAgrees40439029928760583.674
/contactAgrees2862752081983331472.7
/customersAgrees43241031629866635.473.1
/docsAgrees36835026925441395.173.1
/enterpriseAgrees19218014113218176.773.4
/featuresAgrees7186905565311131094.177.4
20 rows in the result · 12 shown, problems first. Sample data: illustrative figures, not business results.

How it works

How to use the Landing Page Week Compare workflow

  1. 1Get early accessWe invite people in small batches, job by job. You'll land on this workflow, already built and working on sample files.
  2. 2Swap in your exportsUpload your own files as they come out of your tools. The agent checks the workflow on your rows.
  3. 3Change it in words, then turn it onSay what to change and see the new result before anything saves. Then choose when it runs.

Landing Page Week Compare: questions

How do you build a GA4 landing page report for the last two weeks?
Export your GA4 landing page data for the last two weeks, then compare the latest week with the one before it. The report shows sessions, engaged sessions, key events, change % for sessions, and engagement rate for each landing page. It also flags rows as Not set, Sessions down, Low engagement, or Agrees.
Which export should you use?
Use the GA4 export that includes landing page rows for the two weeks you want to compare. The file needs the fields for landing page, sessions, engaged sessions, and key events.
What happens to rows that do not match the rules?
Rows that do not meet any flag rule are marked as Agrees. Rows that are not set, have sessions down by more than a third, or have engagement rate under forty percent get the matching status instead.
How do you change the rules?
You change the rules by changing the words for the thresholds and labels in the workflow. For example, you can adjust the drop level, the engagement rate cutoff, or the status names.

Get early access to this workflow

It opens already built and working on sample files. Swap in your own exports to see your result.

Early access opens shortly. Check back soon.

Workflows like this

The number you report every month, rebuilt from the latest export, plus the forecast that follows from it.

All track and forecast workflows →