Agree on what each event means
Named around your funnel rather than the GA4 template. Each event has a definition and a purpose.
An event taxonomy designed around your funnel, implemented in GTM, verified against the platforms, and documented so it stays true after the next release.
view_itemProduct viewedbegin_checkoutCheckout openedpurchasePayment confirmedtransaction_idIllustrative tracking specification. No client data.
Named around your funnel rather than the GA4 template. Each event has a definition and a purpose.
What the front end must push, when, and with which parameters. The document your developers work from.
Tags, triggers and variables built and versioned in your container, with a QA pass against GA4 DebugView.
Illustrative interface with sample data. No live account is connected.
If you mainly need to know whether the current property is trustworthy, the $3,000 attribution audit answers that first.
Often, yes. The audit establishes which it should be. Rebuilding a taxonomy is disruptive and I would rather not recommend it when a correction will do.
Not on day one, but turn the export on regardless. It only collects from the moment it is enabled, so switching it on late costs you history you cannot recover.
Depends on whether your questions are marketing questions or product questions. I have written a full comparison at superapp scale rather than repeating it here.
Your developers, from the spec. If you would rather I did it, that is scoped as part of the project.
The attribution audit establishes whether your property needs a correction or a rebuild, before either is paid for.