Revenue Signal Feed Attribution Shifts Observed in RCFX

Posted by: Macenzi Barker Date Posted: August 18, 2026
Back to Case Studies

Issue

A data anomaly alert flagged a 61% decrease in forms from the Search – Organic: AI Search + SEO channel for the week of Aug 10–16, 2026: 26 -> 10

At first glance, this looked like a tracking problem or a genuine drop-off in organic performance -> exactly the kind of signal that normally triggers a deeper investigation into lost leads or broken conversion tracking. Notably, total form volume across all channels was actually up (405 vs. an average of 342), and PPC saw a corresponding increase, which raised the question of whether channels were cannibalizing each other or whether something had changed in how leads were being tracked on the client’s site.

Solution

Initially tested to confirm that all forms were still tracking across various channels to eliminate the possibility of a genuine tracking issue.

Then, I looped in the AE to check for any account-level changes that could explain the shift. Greg identified the root cause quickly: Inheritance Funding had recently launched the Revenue Signal Feed, and the timing lined up almost exactly with the channel shift. Rather than a real decline in SEO/AI Search performance, the drop was a byproduct of how the Revenue Signal Feed drives and attributes leads, effectively reallocating some of what had previously shown up as organic-attributed forms.

Notes for Future Anomaly Alerts:
When a client implements the Revenue Signal Feed, expect to see channel-level attribution shifts -> most commonly a drop in Organic/SEO-attributed forms alongside a rise in PPC (or vice versa). This is not necessarily a tracking issue or a real performance decline.

Before flagging this as a tracking break or escalating to devs:

  1. Check the All Channels total first -> if overall lead volume is flat or up, the individual channel dip is likely an attribution shift, not a real loss.
  2. Cross-reference the anomaly date against the client’s Revenue Signal Feed launch/rollout date.
  3. Loop in the rest of the account team early -> they’ll often know about the implementation before it shows up in the data.

Achievement

  • Correctly diagnosed a cross-channel attribution shift instead of misdiagnosing a data anomaly alert as a tracking failure or genuine SEO decline.
  • Confirmed overall lead volume for the account grew ~18% week-over-week (405 vs. 342 forms average) -> the account is healthy; the “decrease” was a direct outcome of the new integrated feeds, not lost business.
  • Transformed a potential false alarm into a documented pattern the team can recognize faster in future instances.

Snippet/Screenshot/Link