What this checkpoint covers
The questions draw on the GA4 setup tutorial, the guide to tags, triggers and variables and the debugging and Preview mode tutorial. They test judgement in situations you will meet on a first real setup, not the names of menus.
Task
- Write a short answer to every question before opening the explanations.
- Compare each answer with its explanation and mark it right, partly right or wrong.
- Finish by writing a short list of the setup steps you would now do differently on a property or container you know, and why.
Questions
- An agency offers to create the client's Google Analytics property inside the agency's own account "to save time". What do you say, and why?
- A colleague has just defined the office's internal traffic rules and wants to switch the filter straight to active. What should happen first?
- After launch, a shop's referral report lists its payment provider as a source of sessions that ended in orders. What setting was missed, and what does the mistake cost?
- A lead form's tag uses a click trigger on the submit button. Analytics reports noticeably more leads than the CRM. What is the likely cause, and what is the better trigger?
- The Google tag is attached to the ordinary Page View trigger. Occasionally an event tag fires before it on a fast page. Where should the Google tag fire?
- In Preview mode, a tag's firing trigger shows every condition met, yet the tag is listed under "not fired". Where do you look?
- A container has many GA4 event tags, each with the measurement ID typed in by hand. One tag has a typo. What pattern would have prevented this?
- A new enquiry event is about to be marked as a key event. Which counting method should it use?
Answers explained
Question one
Decline. The property should be created in the business's own account, with access granted outward to the agency. Ownership is hard to move later, and the setup tutorial's first common mistake is exactly this. The GA4 setup checklist puts it as the first line for the same reason.
Question two
Leave the filter in its testing state, check in a report that only the expected visits are labelled, then activate it. An active filter drops data permanently and is not retroactive, so an over-broad rule would remove real visitors for good. The GA4 setup tutorial describes the test before activation.
Question three
The payment provider's domain was not on the unwanted referrals list. Visitors leave for the provider and return, and the return starts a session sourced to the provider, so the channel that actually brought the buyer loses the credit for the sale. Cross-domain measurement covers the business's own domains; unwanted referrals cover third parties a visitor passes through.
Question four
The click trigger counts every press of the button, including attempts that failed validation and repeated clicks. The better trigger is a custom event that the site pushes once the submission has been confirmed, which the guide to tags, triggers and variables recommends over scraping the page. If no push is possible, a form trigger with validation checking is the fallback.
Question five
On the Initialisation trigger for all pages. It fires earlier in the load sequence than Page View, which is where Google recommends placing the Google tag so it has run before any event tag. Raising a tag's priority does not do the same job, because priority orders tags without making one wait for another.
Question six
At the tag's exception triggers and its consent settings. A blocking trigger that matches the same event, or a consent requirement that has not been granted, holds the tag back even when the firing trigger matches. The debugging and Preview mode tutorial lists this as a standard symptom.
Question seven
A constant variable holding the measurement ID, referenced by every GA4 tag. The ID is then defined once, and a change or a typo is fixed in one place. The same guide treats constants for IDs as one of the patterns that keeps a container maintainable in GTMTag management system..
Question eight
Once per session. A double-clicked button, a refreshed thank-you page or a corrected resubmission is still one enquiry. Purchases use once per event, because two orders in one visit are two outcomes. The setup tutorial sets the counting method at the moment of marking because a later change does not restate history.
Where to go next
If you missed the questions on settings, work through the setup tutorial again with the checklist open beside it. If you missed the questions on triggers and Preview, repeat the sign-up form specification exercise. The next module on the beginner analytics level moves on to campaign tagging and first reports.
