Rebuilding Goals as Events

Two ways of describing the same success

In the old system, a goal was usually a destination: somebody reached the thank-you page, therefore something good happened.

That worked because a thank-you page is a proxy. Nobody arrives there without having submitted something.

The new model records the thing itself. A form was submitted, and that submission is an event with a name and some detail attached.

Which is a more direct description, and it means the translation is not automatic: you cannot import a goal, you rebuild the intent behind it.

List what you actually had

The first step, and it frequently turns out to be shorter than expected.

Open your goal configuration in the old system and write down each one: what it was, whether it had ever fired, and whether anybody looked at it.

Most small businesses find three or four goals, of which one or two work and the rest were configured years ago and have recorded nothing since.

Goals that never fire are usually pointing at a page that was renamed during a rebuild, which is worth knowing on its own.

Rebuild only the ones that were genuinely used, since a migration is a reasonable moment to stop carrying things nobody reads.

The four a small business needs

• Contact form submitted.
• Phone number tapped on a mobile.
• Email address clicked.
• Quote or booking request completed.

Between them those cover how somebody gets in touch, which is what a service business is measuring. Everything else is detail on top.

The thank-you page still works

Worth saying plainly, because the change sounds more disruptive than it is.

If your form redirects to a confirmation page, you can still record that page view and mark it as a conversion.

That is the direct equivalent of what you had, it takes a few minutes, and it is a perfectly legitimate approach rather than a workaround.

Recording the submission itself is better where you can, because it works for forms that do not redirect and captures more detail.

But if the choice is between a thank-you page conversion configured today and a proper event configured eventually, take the first.

Something recorded imperfectly beats nothing recorded correctly.

Some of it is already happening

A pleasant discovery that saves work.

The new system records a set of interactions automatically without anybody configuring them: page views, scrolling, outbound clicks, file downloads, and site searches among them.

Many form plugins also send a submission event by default once the property is connected.

So before building anything, look at what is already being collected, since the item you were about to configure may be arriving under a name you did not recognise.

Check by submitting your own form and watching the real-time view, which shows what actually fires.

That five-minute check regularly removes half the work people were planning.

A worked example

A business had five goals in the old system: two form submissions, a newsletter signup, a page-depth goal, and a time-on-site goal.

Reviewing them showed the newsletter goal had recorded nothing in two years because the form had been replaced, and neither the page-depth nor the time goal had ever been looked at.

So two of the five were worth rebuilding.

Submitting the contact form while watching the real-time view showed the plugin was already sending a submission event automatically.

They marked that event as a conversion, added a second for phone number taps, and were finished in about forty minutes.

Their remark was that reviewing the goals had been more useful than rebuilding them, since three of the five had been recording nothing for years.

Mark it as a conversion

The step people miss, because recording and counting are separate in the new model.

An event being collected does not mean it appears as a conversion. It is one of many events until you designate it.

There is a toggle in the events configuration for exactly this, and it takes a click per event.

Be sparing: marking twelve things as conversions means the number means nothing, and the discipline is the same as it was with goals.

Two to four conversions, all of which represent somebody trying to contact you, is the right shape for most small businesses.

Test it, then check again in a week

Because configuration and collection are not the same thing.

Submit your own form and confirm the event appears in real time, which proves the mechanism.

Then look again a week later and confirm the count is plausible against how many enquiries you actually received.

That second check is what catches a conversion firing on every page load, or firing twice, or not firing for people on phones.

Where the number does not match your inbox, trust the inbox and investigate the configuration.

Name them so they still make sense later

A small discipline that pays off the first time somebody else looks.

Event names are yours to choose, and the default suggestions are frequently generic enough to be meaningless in a report six months later.

Use names that describe the thing in plain terms: contact form submitted, quote requested, phone tapped.

Keep them consistent in style, since a report listing one name in capitals, one abbreviated, and one with underscores is harder to read than it needs to be.

Write the list down with a sentence each explaining what triggers it, because in a year the difference between two similarly named events will not be obvious from the names alone.

The counter-case

There is a limit to how much of this a small business needs.

A business receiving most of its enquiries by phone from a number nobody clicks, or by people walking in, is measuring a small slice regardless of how carefully the events are built.

Elaborate event configuration also produces data nobody uses: scroll depth, video engagement, and interaction tracking are genuinely useful at scale and pure overhead for a site with forty visits a day.

And there is a privacy dimension to recording more than you need, which is worth weighing rather than defaulting to collecting everything available.

Rebuild the two or three that reflect somebody contacting you, and leave the rest.

The forty minutes

1. List your existing goals and which ever fired.
2. Discard the ones nobody used.
3. Submit your own form and watch real time.
4. See what is already being collected.
5. Use the thank-you page if that is quicker.
6. Mark two to four events as conversions.
7. Check the count against your inbox a week later.

Step four is the one that saves the most time, since much of what people plan to configure is arriving already under a different name.

Counting the right thing is covered in counting enquiries instead of visits.

Frequently asked questions

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.