high impactPRODUCTIONSQL / Data Views

Joining _Open Directly to _Click Can Explode Rows

A subscriber/job report returns far more rows than either source and aggregates start looking absurd.

Context Pack →Open Workspace →
Trust & provenancePRODUCTION
Evidence tierPRODUCTIONOfficial sources0Other sources0Last verifiedNot recorded

Evidence tier describes my hands-on relationship with the content. Official sources describe platform contracts/documentation. Production observations should not automatically be treated as official limits.

Why it bites

Both event views can contain multiple rows at the same subscriber/job grain. Joining raw events together creates many-to-many multiplication.

What to check
  1. What is the grain of _Open input?
  2. What is the grain of _Click input?
  3. Are you joining events before reducing to one row per reporting key?
Make it cheaper next time
  1. Pre-aggregate each event source separately, then join the reduced sets.
  2. State output grain at the top of every reporting query.
sqlopenclickgrain