Skip to main content

GTM, the dataLayer and Your First Conversion · Part 1: What web analytics is, and why tracking breaks on its own

Chapter 1.2 · 2 of 25 · 3 min

Business goal, customer journey, conversion event: which comes from which

The most common mistake beginners make: they open GTM and then wonder which events they could add.

Free to read

The most common mistake beginners make: they open GTM and then wonder which events they could add. That is backwards.

There are three steps, in order. Business goal, then customer journey, then conversion event. Skip a step and you will build events nobody ever looks at.

Business goal

Ask the client one question: what is your biggest worry this month? The answer is either about money or about people.

For the clothing shop, the goal is more orders and fewer COD returns. For a tutoring business, the goal is more enquiry calls. For a SaaS product, the goal is trial to paid.

The important point is that there is one goal. Not two, not five. A client who names five goals really has one, and the other four are that one goal wearing different clothes.

Customer journey

Next, write down everything the person does from first seeing you to paying. Write it by hand, in your notebook, left to right.

A WooCommerce clothing shop's journey looks like this: saw the ad on Facebook, clicked, landed on the product page, looked at the photos, picked a size, added to cart, went to the checkout page, entered name and address, chose bKash or COD, confirmed the order.

Each of these steps is a possible event. You do not need to measure all of them.

Conversion event

Now decide which steps to measure. There is one rule: measure a step if measuring it lets you make a decision. Drop the rest.

For that shop I measure four: view_item, add_to_cart, begin_checkout, purchase. Those four form a funnel, and the funnel shows you where people are dropping out.

If add_to_cart is 100 and begin_checkout is 12, the problem is on the cart page. If begin_checkout is 80 and purchase is 9, the problem is at payment. Those are two different problems with two different solutions, and without the events you would know about neither.

Settle the names now

You cannot rename an event later. If you do, the old data and the new data become two separate things, and reports show them as two separate lines.

So use GA4's recommended names where they exist: view_item, add_to_cart, begin_checkout, purchase, generate_lead. Lowercase, underscores between words, no non-Latin characters, no spaces.

Steps

  1. Ask the client, or yourself, what this month's business goal is. Write it in one line.
  2. Draw the customer journey in your notebook, from first sight to payment, each step in its own box.
  3. Mark 3 to 5 of those steps that you will measure.
  4. Next to each, write the GA4 name. If you do not know the name, look it up in GA4's list of recommended events.
  5. Keep this list. In Parts 2 and 3 you will work from exactly this list.

What not to do

  • Do not try to measure everything. I once saw a container with 61 tags, and the client did not know what any of them did. 61 tags means 61 places to break and zero decisions.
  • Do not give events names in Bangla or any other non-Latin script. If you name an event "purchase complete" written in Bangla script, GA4 will accept it, but BigQuery, Looker Studio and Meta will give you trouble. Event names in English, report text in the client's language: that is the rule.

Proof

Your notebook has one goal, one journey and 3 to 5 event names written to GA4's conventions. That page is the map for the rest of this book.

Want the full chapter list, or to jump to another chapter?

All chapters in the book