WorkCase study

Source to submission.

For iHeartMedia, we connected traffic-source attribution with progress inside an interactive credit application. The analytics team gained a clearer basis for understanding which sources led to submissions and where applicants stopped progressing.

Read the case
Event crew beneath an iHeartRadio stage display; not the credit application or engagement.
Client
iHeartMedia
Sector
Media & communications
Focus
Credit-application measurement
Our role
Analytics consulting & implementation
01 / Context

Understand which sources lead to completed applications.

iHeartMedia’s Director of Insights & Analytics engaged CM&P to address gaps in measurement for an online credit application. The team needed to understand where applicants came from, how they progressed, and which journeys ended in submission. That connection mattered to evaluating acquisition sources and deciding where the application experience warranted investigation. This was a defined analytics engagement for the credit application—not concert operations or consumer radio-listener acquisition.

02 / Challenge

One URL concealed a multi-step journey.

Applicants completed several interactive steps without loading a new page or changing the URL. The existing page-visit tracking did not adequately represent that progress. Separately, the journey crossed multiple subdomains, and the existing configuration lost the original referring source as users entered the application. Together, these gaps disconnected acquisition from application activity: a visit alone could not explain how far someone progressed, and a submission could not reliably be connected to its originating source.

03 / Our approach

Define the questions. Implement the measurement.

We combined analytics consulting, measurement design, custom programming, and implementation. The work connected the team’s questions about acquisition and application completion with the signals needed to answer them. It also included explaining why the previous setup had failed and how the measurement approach addressed those gaps.

  1. 01Diagnose the gaps

    Examine entry paths and interactive application stages. Identify where progress was invisible and where acquisition context was lost between subdomains.

  2. 02Define meaningful milestones

    Design measurement around completion of defined application stages and submission, rather than relying on page views to stand in for progress.

  3. 03Connect and explain

    Implement custom event tracking in Google Analytics and measurement across the relevant subdomains. Explain how source information, milestones, and submissions fit together.

04 / The solution

Acquisition and application progress, connected.

The solution joined referring source and medium with defined application milestones and completed submissions. It gave the analytics team a way to examine the journey as a whole, rather than interpret disconnected traffic and application activity.

IHeartRadio event scene, unrelated to the credit-application workflow measured in this case.
  1. 01Confirmed capability

    See meaningful progress

    Measure completed stages, not just page visits.

    Custom events recorded completion of the application’s defined stages even though the URL stayed unchanged. The team could examine where applicants advanced and where they stopped, giving further investigation a specific starting point.

  2. 02Confirmed capability

    Retain acquisition context

    Keep source and medium with the application journey.

    Measurement across the relevant subdomains preserved the referring information as users moved into the application. Completed submissions could be connected with the channels that brought applicants into the journey.

  3. 03Confirmed capability

    Ask better acquisition questions

    Connect a source with what happened next.

    The connected framework supported questions such as: Which sources produced completed applications? How did progression differ by source? Which stages warranted closer review? It enabled analysis without assuming that more traffic meant more completed applications.

  4. 04Confirmed capability

    Understand the measurement

    Explain the gaps as well as the solution.

    We explained why the prior setup did not represent the interactive experience or preserve the original source. That understanding helped the team interpret the resulting data in the context of how the application worked.

The applicant journey
  1. 01Arrive

    Capture the referring source and medium associated with the visit.

  2. 02Enter

    Preserve acquisition context across the relevant subdomains as the applicant enters the application.

  3. 03Progress

    Record completion of defined milestones within the interactive application, without requiring a URL change.

  4. 04Submit

    Measure submission as the completion outcome and connect it with the preceding source and application activity for review.

05 / Results

A journey the analytics team could investigate.

The delivered result was connected measurement: a basis for evaluating sources and examining incomplete application journeys. It established visibility, not a measured increase in conversions, revenue, marketing return, or staff efficiency.

  • Application visibility

    Defined stages became visible within a single-URL experience.

    Custom events recorded application-stage completion.
  • Source to submission

    The team could examine acquisition alongside application outcomes.

    Source and medium connected with milestones and completed submissions.
  • Relationship continuity

    Three additional engagements over the following six months.

    Reported in the supplied engagement account; continued analytics consulting and development, not a marketing-performance measure.

Measure the journey the decision depends on.

A page visit and a completed application answer different questions. Connecting acquisition context with meaningful progress gives a team a stronger foundation for investigation. It does not, by itself, explain why an applicant left or prove that a later change improved performance; those conclusions require further analysis and evidence.

Start here

Can you connect acquisition to the outcome?

When reporting loses the customer journey between entry and completion, the next decision becomes harder. We help define the questions, identify the measurement gaps, and implement the connections needed to investigate them.