BIA STUDIO / ANALYTICS

Analytics BiA Studio

Analytics for an architectual office

BiA Studio analytics built from scratch with GTM, GA4 and Microsoft Clarity: measuring interest in projects, contact choices, form usage and on-site search.

Digital analytics

00 / Starting situation

The BiA Studio website presents the practice’s body of work and prepares prospective clients for a conversation about an investment. Analytics needed to distinguish interest in specific projects, contact choices and the way users interact with the enquiry form.

01 / SCOPE

Configuration

We built the analytics configuration for biastudio.pl from scratch using Google Tag Manager, Google Analytics 4 and Microsoft Clarity. Measurement covered interest in the practice’s projects, the choice of contact method and the way users moved through the enquiry form.

We matched the analytics to the role of the website in selling architectural services: helping people discover BiA Studio’s work and preparing prospective clients for a conversation about an investment.

02 / MAIN CHALLENGE

Types of signals

BiA Studio’s portfolio presents different areas of the practice’s expertise. A person browsing projects may be looking for inspiration, checking the team’s experience in a particular type of investment or considering working together. Measurement had to account for actions with different meanings along that path.

The important part was separating interest in specific projects, attempts to make contact and a submitted enquiry. Each of these signals answers a different question about user behaviour and needs to be interpreted separately.

03 / EXPERTISE

Our way of implementation

We connected portfolio measurement with project selection and category filtering. Clicking a project passes its identifier, while selecting a filter passes the category of interest. Events also include information about the type of page where the interaction occurred. This makes it possible to relate analysis to specific parts of BiA Studio’s work and website.

We separately configured clicks on the phone number, email address and a selected route to the contact page. The form received measurement for the start of interaction, errors and confirmed submission. The enquiry event was tied to the form’s successful-send message. We also added event identifiers and safeguards against sending the same signal to the analytics tools more than once.

We mirrored the same key actions in GA4 and Microsoft Clarity using shared event naming. This makes it possible to combine event analysis with observation of how people use the website. We also covered the site search, including recognition of searches with no results - useful when assessing what information visitors are looking for.

04 / RESULT

Preserving context for events

BiA Studio received a measurement setup covering project selection, use of portfolio categories, contact actions and form handling. Individual events retain the context needed to interpret them.

This created a basis for assessing which projects attract clicks, how users initiate contact and whether they encounter difficulties when submitting an enquiry. In this way, analytics supports further work on a website designed to move visitors from discovering the practice to discussing a potential collaboration.

BIASTUDIO.PL

See the BiA Studio website

Explore the portfolio, project categories, site search and contact paths covered by the measurement setup.

Visit biastudio.pl
S.09 / ContactEnquiry / similar challenge

What in this case resembles your situation?

Describe the similarity and the result you need. We will not assume that the same scope is the right answer.

  1. 1Conversation scopeCurrent step
  2. 2Context
  3. 3Budget and timing
  4. 4Contact

We respond with a concrete recommendation by the end of the next business day.

Step 1 / 4

Which outcome matters most?