Skip to content

Guide 157 · Events · GA4 + Tag Manager

Create a custom event in the GA4 interface: no code, from an existing event, with the 50-event limit

Checked 11 November 2026 · Verification: event reference validated structurally (event, parameters, rules, worked example); worked example recomputed · Steps traced to Analytics Help, opened 11 November 2026 · 6-minute read

Not every new event needs a tag. When the event you want is a slice of one GA4 already collects, the Create event feature in the GA4 interface builds it from the existing event, with matching conditions and no code change. This guide builds thank_you from page_view on the confirmation URL, and records the limits that bound the feature: 50 created events, no history, and up to an hour before it shows.

Expected signal

After the event is created, a test visit to the confirmation page shows the new thank_you event in DebugView and, within about an hour, in the Events report — while the original page_view keeps counting every page as before.

Download the reference: the create-event reference (JSON) (2079 bytes, MD5 83b4869b073452c6b0add19cac74de23). It lists the worked example — thank_you built from page_view on the confirmation URL — the matching conditions, the limits (50 created events per property, up to 1 hour to appear), and the rules that bind it. The matching tag work is not in the file: this method needs no tag at all.

What you need

  • Viewer access or above at the property level. Google's page says Viewer or above can create the event; marking it as a key event needs Marketer or above.
  • A source event GA4 already collects. The feature only builds from an event that is already arriving. Here the source is page_view, which the Google tag sends on every page.
  • A condition that singles out the new event. Here the condition is the confirmation URL: the page location contains /thank-you.

The worked example

The worked example is Google's own: thank_you built from page_view on the confirmation URL. The limit that bounds the feature is the budget of created events per property.

MeasureCount
Created events allowed per property50
Created events already used12
Created events remaining38
Share of the budget used12 / 50 = 24.00%

Those figures were recomputed here before publication: 50 minus 12 is 38 events remaining; 12 divided by 50 is 0.24, so 24.00% of the budget is used. The rule for the new event is the standard form:

Event name: thank_you
Source event: page_view
Condition: page_location contains /thank-you

The trace

  1. Open the Events page. In Analytics, go to Admin, then under Data display, click Events. You must be signed in to a Google account, and the property selector at the top must show the right property. This step needs a Google sign-in, so it was traced to Google's documentation, not run here.
  2. Start the creation. Click + Create event. The page shows the events already created in the property; click Create at the top to start a new one.
  3. Name the new event. In Event name, enter thank_you. The name follows the same rules as any event name: letters, numbers, and underscores, starting with a letter, no more than 40 characters. The naming-rules guide covers the full list.
  4. Mark it as a key event, if it is one. Optionally, click the toggle next to Mark as key event, and select a default key event value and a counting method. The key event guide covers what each choice means. This needs Marketer access or above.
  5. Choose how to create it: without code. In Choose how to create an event, select Create without code. Choose page_view from the Event name dropdown. Enter the confirmation URL in the URL field — for example https://www.example.com/thank-you.html — so the new event fires only when the page view is on that URL.
  6. Create it, then wait. Click Create. The new event appears in the Custom events table at once, but it does not appear in the Recent events tab until Analytics processes the event, and it can take up to an hour before it starts to show. Visit the confirmation page yourself, then check DebugView for the thank_you event.

Dead ends

DEAD END — THE SOURCE EVENT DOES NOT EXIST YET. The feature builds only from events GA4 already collects. Creating a new event from a custom event that has never fired fails, because there is nothing to match against. Send the source event first, then build on it.

DEAD END — EXPECTING HISTORY. A created event never applies to data collected before it was created. The thank_you count starts at zero on the day of creation, and the past page views on the confirmation URL stay page views. The rename guide explains the same rule for names.

DEAD END — THE 50-EVENT BUDGET SPENT ON SLICES. Every created event uses one of 50 slots. A property that builds a separate created event per page, per campaign, and per button fills the budget on slices that a parameter could have carried instead. Parameters are free; created events are not.

End state

One new event, no tag, no code change. A visit to the confirmation page fires thank_you in DebugView within a minute and in the Events report within about an hour, while page_view keeps counting every page as before. If the slice ever needs to change — a different URL, a different condition — the modify guide covers editing a created event, and the rename guide covers what happens to the name.

Sources

Checked 11 November 2026. The click paths above are the ones in Google's help and developer pages, opened 11 November 2026. No step in this guide was run inside a live Analytics property or a live Tag Manager container, because both need a Google sign-in and this site does not sign in as anyone. What was run: the reference file was validated structurally in Python 3.12.3 — it parses, the event is thank_you, the source event is page_view, and the limit fields are present — and the budget arithmetic was recomputed: 50 - 12 = 38 events remaining; 12 / 50 = 24.00% of the budget used. Google moves menu items without warning; if a path on this page no longer matches, the linked help page is the current map.