When the AI Got Causation Backwards: A 70%-Confidence False Conclusion

Forest Liu · Data Marketing Lead for Multiple Companies#causal-inference#llm-reasoning#ai-accountability

Summary

At 2 AM the anomaly engine flagged impressions down 67% (100 vs a mean of 301) at a score of 67. The LLM's 70%-confidence causal chain blamed 43 negative keywords — in fact a correct optimization. The July 15 human review exposed five limitations, from inverted causation to inflated confidence, and changed how we reason with AI.

Quick answer

AI causal claims built on correlational evidence can invert the true story. Give the model campaign-level business context (business type, audience, brand keywords), let humans label each evidence link as agree or disagree, and scale confidence by evidence strength — a 70% causal hypothesis backed only by correlation should be downgraded to a correlation.

At 2:00 AM our anomaly detection flagged a campaign whose impressions had dropped 67% — 100 impressions versus a historical mean of 301 — and generated an anomaly event with a score of 67. The analyst on call clicked “reason causal chain,” and the LLM did its job. It analyzed 30 preceding candidate events and state snapshots, produced eight evidence links, and delivered a conclusion with 70% confidence: the 43 negative keywords added the day before had over-restricted the campaign's reach.

That conclusion was exactly backwards.

The truth: the negative keywords were the fix, not the bug

The 43 negative keywords — brand-adjacent terms like “webox”, “login”, “food”, and “catering” — were a deliberate, correct optimization. They had been cutting off competitor terms mis-matching our brand keywords, and their removal of that noise was why impressions fell. The AI had taken a correct optimization action and labeled it a mistake.

Five limitations found in the review

That night's human review — which happened the evening of July 15 — surfaced five structural limitations:

  • Inverted causation. The model saw “more negatives + fewer impressions” and concluded over-restriction. It had no business semantics to tell it the negatives were our own brand terms.
  • No business context. The LLM did not know these strings were our own brand names, nor that in B2B lead generation these are purely mis-matched queries no prospect would convert on.
  • Inflated confidence. A 70% causal hypothesis was really a correlation. The evidence supported “impressions and negative count moved together,” not “negatives caused the drop.”
  • Missing the real cause. A fully-loaded RSA push may have been the true driver, but it was too recent to sit inside the preceding-candidates window, so the model could not see it.
  • Unfounded external guesses. Competitor spend and algorithm updates were floated without any data behind them.

What we changed

Three changes came out of this case. First, campaign-level business context is now injected into the prompt: business type, target audience, and the brand keyword list, so the model knows what a term means before it reasons about it. Second, humans can label each evidence link as agree or disagree, and that label is stored with the chain. Third, confidence is now adjusted dynamically by evidence strength — a correlation does not get to wear a causal confidence score.

The value of the closed loop

This case is why we believe in the machine-finds-signal, human-decides loop: the AI detected the anomaly, alerted, reasoned about it, and a human corrected it — in time, before the wrong conclusion could reach a client report. Four lessons we now apply to any AI causal reasoning:

  1. Never trust a causal label without checking whether the evidence actually supports causation.
  2. Give the model the business semantics — brand names, audience, offer — before asking it to reason.
  3. Treat high-confidence causal claims built on correlational evidence as a system bug, not a quirk.
  4. Always keep a human review step between an AI conclusion and any external action.

The machine found the signal; the human kept it honest. That division of labor, with evidence chains and a human review loop, is exactly what our attribution and growth engine at iport is built around.

Note on system details: The iport platform is under active development. Any product features, interfaces, or workflows described in this article reflect the version in use at the time of writing and may differ from the latest release. For the most current capabilities, refer to the official platform documentation.

Frequently asked questions

Why did the LLM blame the negative keywords?

It saw more negatives plus fewer impressions and inferred over-restriction. Without business semantics it could not know that those keywords were the brand's own terms and a correct optimization. That is the classic inverted-causation failure: a correct fix labeled as the bug.

What was wrong with the 70% confidence score?

The evidence only supported that impressions and negative count moved together — a correlation. Labeling a correlation as a causal hypothesis at 70% confidence overstates certainty. Confidence should be adjusted dynamically by evidence strength, and a correlation should never wear a causal score.

How do we keep AI causal reasoning honest in practice?

Keep a human review step between the AI conclusion and any external action, inject business context — brand names, audience, offer — into the prompt, and let reviewers label each evidence link as agree or disagree, storing those labels with the chain so the model can be tuned against them.

Keep reading