Lesson 6 of 15

The One-Page Cheat Sheet

Pin this. It compresses the course into something you can run in ten seconds, then adds the half everyone forgets: naming the event well once you've chosen how to catch it.

1dataLayer?→2Built-in?→3DOM?→4Listener→5Name it well

PICK THE METHOD (stop at first yes)
  1. In the dataLayer, or a dev can add it?  -> DLV + Custom Event trigger
  2. Can a built-in trigger observe it?      -> Click / Form / Scroll / Visibility
  3. Is the value in the DOM?                -> DOM Element / Custom JS (patch + ticket)
  4. None of the above?                      -> Custom HTML listener -> dataLayer push

THEN NAME IT WELL
  - Reuse a GA4 recommended event name when one fits (purchase, generate_lead,
    sign_up, search, select_item) so reports and audiences work out of the box.
  - snake_case, lowercase, no spaces. Be consistent across the container.
  - Carry context as parameters (value, currency, item_id), not in the name.

Why naming belongs in the same decision

Choosing a reliable capture method and then inventing a one-off event name like btnClick2 wastes half the win. A predictable name is what lets the data flow straight into GA4 reports, audiences and the Container governance conventions without a rename later.

Key takeaway

Method first, name second, in one motion: climb to the highest reliable rung, then give the event a recommended, snake_case name with its context in parameters. That's a capture you won't have to redo.