• Javier Socarras

    SEO strategist and AI search specialist

    Who builds it
  • Documented work

    Projects from our parent company

    View case studies
  • 24 tools

    Free planning tools with visible assumptions

  • Growth audit

    Growth audit for your website and inquiry process

What should GA4 conversion tracking count?

GA4 conversion tracking should count a clearly defined action and preserve what that action does not prove. AI Growth Systems can distinguish a contact click, accepted form and confirmed booking before installing events. The measurement plan ties each reported outcome to a test and an identifiable record in the receiving system.

A phone-link click shows an attempt to call; the call system may hold the conversation record. A browser success message may appear before staff receive a request. A purchase needs the appropriate order information rather than a button interaction alone. Define each step before comparing their totals.

The project should leave your team able to explain the numbers. More events are not automatically better measurement, and an attractive dashboard does not resolve a mismatch between a web interaction and the business record it supposedly represents.

Which parts of tracking can be set up?

Conversion tracking work can include event definitions, agreed installation and checks of the recorded parameters. AI Growth Systems identifies the accounts and customer paths in scope after the audit. Each implementation task should state what triggers the event, where it is sent and which evidence will confirm the intended behavior.

Begin with a small number of actions tied to real decisions. A quotation request may need separate reporting from a newsletter subscription. A booking system may confirm acceptance outside the main website. A store may require purchase information that the platform already sends. Duplicate installations can obscure those distinctions.

Record the existing configuration before adding tags. If a form fails to deliver, fixing that connection is a different task from counting a successful delivery. Website development, customer-system connections and advertising changes need their own agreed responsibilities.

How do you investigate numbers that do not agree?

A conversion measurement review compares the same action, time period and destination before deciding why reports differ. AI Growth Systems can follow a controlled test from the website to analytics and the business receiver. We preserve the difference between a missing event, duplicate event and inquiry that never reached staff.

Choose one case with an invented reference your team can find. Note the page, action and expected receiving record. Check what happens on a valid submission, an invalid attempt and a repeated action when those cases apply. A passed browser test alone cannot prove the inbox or customer record received the right information.

Use the conversion tracking QA checklist to frame the review. The proposal should distinguish a confirmed configuration fault from differences that require more data or access before they can be explained.

Who is accountable for the measurement work?

The provider is AI Growth Systems, operated by SOCARRAS WEBSITE DESIGN AND SEO LLC in Deerfield Beach. Javier Socarras, its SEO strategist and AI search specialist, leads the work. The public Google business profile gives your team an external place to check the business before commissioning measurement changes.

Deliverables, exclusions and the schedule appear in the written proposal. For tracking, ask that the account owner, test approver and person checking receiving records are named too. Service coverage across the United States does not replace those specific project responsibilities or imply a branch office.

What should a tracking handoff contain?

A conversion tracking handoff should describe the installed events and the tests supporting them in language the business can use. AI Growth Systems agrees the test scope after the initial audit. Each event needs a definition, trigger and destination so a future editor can tell whether a website change affects the measurement.

Request these acceptance records for the paths included. They describe how to verify the setup; they do not establish that every visitor is measurable or that reported actions are profitable.

  • Event name, business meaning and exact triggering condition.
  • Receiving analytics property and any agreed advertising destination.
  • Permitted parameters, with personal contact details excluded from Analytics.
  • Dated tests for successful, invalid and repeated actions where applicable.
  • Comparison with the business receiver for the outcomes claimed.
  • Known limitations, account ownership and instructions for retesting after changes.

How much does tracking setup cost?

Conversion tracking setup services start with the required $300 Growth Audit and a separate custom written implementation quote. The price depends on the actions, platforms and connections involved. A simple site event, an externally confirmed booking and a purchase tied to an order record can require different installation and testing work.

List the existing analytics and tag setup along with the receiver for each enquiry or order. Ask whether the quote includes the website change, parameter checks and reconciliation with staff records. Ongoing reporting, call tools and customer-system integrations should be specified separately when needed.

The Growth Audit covers the agreed review rather than an open-ended repair package. The later proposal confirms schedule, account access, taxes and outside charges before installation. Adding measurement does not by itself include advertising management or promise more customers.

Published guidance for event checks

Google's implementation guidance supports the event checks below. It does not prove that your account is configured correctly. An event appearing in a test report and a customer action confirmed by the business are separate observations; keep their definitions and dates with the test record.

Published guidance for event checks
Local evidenceVerified value or findingSourceSource dateWhy it matters for this service
Event verificationGoogle Analytics documents Realtime and DebugView for inspecting triggered events and their parameters.https://developers.google.com/analytics/devguides/collection/ga4/eventsUpdated 2026-06-09; GA4 implementation guidance.; Checked: 2026-11-15Check that an agreed test event reaches the intended property. Receiving an event does not prove that a sale or qualified lead occurred.
Purchase duplicatesGoogle explains that a repeated ecommerce event with the same transaction ID is ignored after the first collection.https://developers.google.com/analytics/devguides/collection/ga4/validate-ecommerceUpdated 2024-10-09; ecommerce validation guidance.; Checked: 2026-11-15Use controlled transaction identifiers when testing purchase events. This does not establish duplicate prevention for every form or business system.
Personal data exclusionGoogle Analytics guidance prohibits sending information Google could recognize as personally identifiable, including email addresses and personal phone numbers.https://support.google.com/analytics/answer/6366371?hl=enUndated product guidance; no statistical data period.; Checked: 2026-11-15Inspect event parameters and page URLs before release. This product-policy check does not replace a broader privacy or legal review.

Which action should we review first?

Start a conversion tracking review with the action you need to count and the place your team confirms it happened. AI Growth Systems begins with the mandatory $300 Growth Audit. Send the relevant public page and describe the expected outcome before granting access or choosing which installation work to commission.

State whether the concern is missing records, duplicate counts or a report that calls every click a lead. Identify the booking, form, call or order receiver. A controlled example with invented details can clarify the path without putting private customer information into the initial request.

Request the initial audit with the systems already in use and the decision the report must support. After reviewing the agreed setup, we quote event work, receiver connections and continuing reporting as distinct deliverables where they apply.

Frequently asked questions

Does a form success message prove that a lead arrived?

We check the receiving record as well as the browser message before describing an inquiry as received. A success display may only describe the website step. The agreed test should find its invented reference in the appropriate inbox or customer system and preserve the fields the responding team needs.

Can Analytics report every customer action?

We do not promise complete observation of every customer. Tool settings, permissions and the way customers move between systems can limit measurement. The scope records what each event captures and what remains outside it, allowing the business to distinguish observed activity from an assumed total or an attributed sale.

Is installation included in the $300 audit?

We start every client with the $300 Growth Audit; installing events and repairing connections are separately quoted work. The review defines the existing setup and priorities within its agreed scope. Your later proposal names the actions, platforms, tests and charges before you approve implementation or recurring reporting.

Can you fix duplicate purchase counts?

We investigate the trigger and order identifiers before recommending a correction. Google's purchase-event behavior depends on transaction information, while duplicate form events can have another cause. We test the agreed cases and document the result; one corrected sample does not establish that every historical report can be repaired.

Should an event contain the customer email address?

We exclude personal email addresses and similar contact information from the Analytics parameters we define. Google's product guidance prohibits sending recognizable personal information. A business receiver may need contact details for its task, but that is a separate destination; the measurement plan should preserve that distinction and identify permitted fields.

Request a review of your project

Send us your website and the goals you want reviewed. The $300 AI Growth Audit is the first step; any follow-up work is outlined in a written quote.

Request the audit

Decision guide

AI Growth Navigator

Describe the problem or choose a goal. This guide matches your question to published AI Growth Systems pages. Your question stays in this browser until you submit a contact request.

The first step for every client

Start with the $300 Growth Audit. You then receive a written quote.