IMPLEMENTATION CASE STUDY / ATLA
From website activity
to a confirmed booking.
Website and booked-call tracking for a creative agency focused on brand design and visual identity.
The starting point
The project account describes a website with no tracking in place. The goal was to make service and portfolio interactions, contact actions, and steps toward a call booking visible in the measurement setup.
What was configured
- GA4 and Meta events for service, portfolio, and blog clicks.
- Contact, email, phone, and social-link interactions.
- Separate events for form starts, submissions, and confirmed bookings.
- Web-container event tags for server-side routing, with a Facebook Conversions API tag in the server container.
- UTM tagging on the Instagram website link to identify visits through that specific link.
THE MEASUREMENT DECISION
A booking-button click is a step.
A confirmed booking is the conversion.
The Lead event was configured to represent a confirmed call booking. Keeping those actions distinct makes the event definition easier to understand.
How to read this case
This summary is based on Omar’s existing Atla project documentation. It describes implementation scope. It does not establish that every configured event passed testing or that the work increased revenue, lead quality, or advertising performance.
Instagram UTMs identify traffic through the tagged link. They do not identify every visitor who may have discovered the agency on Instagram.
What this means for your project
Start with a precise conversion definition. Then map the journey, configure the required signals, and test each scoped action. CRM qualification and revenue connections require their own records, access, and agreed implementation scope.
Discuss a similar setup ↗