What it answersNothing on its own. It is the container the other four live in, and the reason none of them has to be written into your website's code.
What it needs firstOne piece of code on the site, and a naming habit somebody actually keeps.
What skipping it costsEvery new tag becomes a developer ticket, and within two years nobody can say who installed what or why.
What it answersHow people found you, what they did, where they gave up, and which channels were involved in the sale rather than only the last one.
What it needs firstConversions defined per action with values attached. The default install measures almost nothing you care about.
What skipping it costsYou have traffic reports and no way to say which of that traffic produced a paying customer.
What it answersWho converted, so Facebook and Instagram can go looking for more people who behave like them.
What it needs firstA tag on the site firing the same handful of actions you agreed count as customers — not every page load.
What skipping it costsYou are paying Meta to guess, and the audiences you follow up with are built out of nothing.
What it answersThe same question the Pixel does, reported from your own server, for the growing share of visitors whose browser will not report it.
What it needs firstA server-side connection, and a shared reference with the Pixel so one sale never arrives as two.
What skipping it costsReported results drift further from your invoices every year, and the bidding optimises on a partial picture of your customers.
What it answersThe kind of company on your site — industry, size, seniority and function, in aggregate rather than by name.
What it needs firstEnough traffic for the reports to show anything, and a B2B sale worth the effort of reading them.
What skipping it costsFor a business selling to other businesses, the only signal about who is actually looking. For a consumer business, very little.
