Measurement problems solved across analytics, consent, attribution, and CRM.

The situation

A direct-to-consumer eyewear brand changed from a single California-style consent experience across all US traffic to a state-tiered configuration.

Reported opt-in performance increased immediately. On the surface, the new number appeared to show that significantly more visitors were actively accepting tracking. That was only part of the story.

What we found

The change in the headline rate was being influenced by two separate factors: more total website traffic, and a change in how visitors were classified under the new regional configuration.

Some visitors were now entering a more permissive default state. That improved the reported consent metric, but it did not mean every additional visitor had actively opted in. Reporting the full increase as a change in user behavior would have overstated the result.

What we did

We separated the performance change into its actual components. The analysis reviewed:

• 01Traffic volume before and after the change
• 02Consent rates by region and configuration
• 03Active consent compared with default classification
• 04Tag behavior across consent states
• 05Effect of the revised experience on analytics and advertising measurement

The situation

A Shopify retailer believed its organic search performance had been penalized. GA4 sessions had declined, leads were down, and the existing reporting did not provide a clear explanation.

The team needed to know whether the problem was search visibility, user behavior, measurement, or a combination of all three.

What we found

Google Search Console showed that search impressions remained relatively stable while click-through rate declined sharply during a specific mid-June period. That pattern was more consistent with changes to the search results page and increased SERP competition than a broad ranking loss.

The audit also identified several unrelated measurement issues that were making the overall performance picture less reliable.

Measurement findings

• 01An additional GA4 measurement ID loading alongside the intended property
• 02Data retention set to two months, restricting long-term analysis in Explorations
• 03A high-value quote journey moving visitors to a third-party environment without reliable submission tracking
• 04Configuration and search findings being interpreted as one problem despite different causes

What we did

We reviewed the website, Google Tag Manager, GA4, Search Console, and the third-party quote journey. The final report separated:

• 01Organic search visibility
• 02Search-result click-through behavior
• 03On-site analytics configuration
• 04Lead-tracking gaps
• 05Data-retention limitations
• 06Recommended implementation priorities

The situation

A specialized healthcare organization wanted onboarding emails to reflect the partner network through which each new client registered.

The registration process occurred outside HubSpot. New accounts were created in an external system and later synchronized to the CRM through a backend integration. The partner identifier therefore had to survive the complete signup and synchronization process before HubSpot could use it for personalization.

The challenge

The existing onboarding workflow was already active. Changing it directly would have created unnecessary risk for contacts currently moving through the sequence.

The solution also needed to support additional partner networks without creating a separate workflow for every landing page.

What we did

We cloned the existing workflow and built a controlled routing structure. The revised setup used:

• 01One centralized HubSpot contact property
• 02Separate paths for partner and standard registrations
• 03HubSpot smart content for partner-specific messaging
• 04A shared onboarding sequence after the personalized welcome step
• 05A staged migration plan for contacts already enrolled

Post-launch monitoring

The framework was later extended to six partner networks. During monitoring, two referral lists remained at zero even though the HubSpot workflow logic was operating correctly.

We traced the issue upstream to the backend property synchronization, documented the affected cases, and escalated the defect to the development team. This prevented unnecessary changes to workflow logic that was already working as intended.