Colocalization analysis is a Bayesian statistical method that determines whether two association signals—such as a genetic variant's effect on a molecular trait and its effect on a complex disease—are driven by the same causal variant at a shared genomic locus. It moves beyond simple overlap of significant hits to quantify the posterior probability of a single shared causal variant, distinguishing true pleiotropy from mere genomic proximity caused by linkage disequilibrium.
Glossary
Colocalization Analysis

What is Colocalization Analysis?
A statistical method to assess whether two potentially related traits share the same causal genetic variant at a given genomic locus, supporting a shared causal mechanism.
The method integrates GWAS summary statistics and expression quantitative trait loci (eQTL) data to compute five mutually exclusive hypotheses, with the key metric being the posterior probability of a shared causal variant (PP.H4). A high PP.H4 provides strong evidence that a molecular phenotype and a disease outcome are causally linked, making it a critical tool for prioritizing drug targets and validating findings from Mendelian randomization studies.
Key Characteristics of Colocalization Analysis
Colocalization analysis tests whether two traits share the same causal variant at a genomic locus. It moves beyond simple overlap of association signals to quantify the probability of a shared causal mechanism.
Posterior Probability of Colocalization
The core output is a posterior probability (PP) that a single variant is causal for both traits. This is calculated under a Bayesian framework that evaluates five mutually exclusive hypotheses:
- H0: No causal variant for either trait
- H1: Causal variant for trait 1 only
- H2: Causal variant for trait 2 only
- H3: Two distinct causal variants, one for each trait
- H4: A single shared causal variant for both traits A high PP.H4 (typically >0.75) supports a shared causal mechanism.
Bayesian Statistical Framework
Colocalization uses a Bayesian model averaging approach to integrate uncertainty across all variants in a locus. Unlike simple overlap tests, it accounts for linkage disequilibrium (LD) patterns and the possibility of distinct causal variants in high LD. The method computes Bayes factors comparing each hypothesis, then derives posterior probabilities using prior probabilities that reflect the expected sparsity of causal variants in the genome.
Input Data Requirements
The analysis requires GWAS summary statistics for both traits at a defined genomic locus. Essential inputs include:
- Variant IDs (rsIDs or chr:pos)
- Effect sizes (beta or log odds ratio) and standard errors
- Allele frequencies or sample sizes
- LD matrix from a matched reference panel (e.g., 1000 Genomes) Precise alignment of effect alleles across datasets is critical to avoid sign errors.
Distinction from Mendelian Randomization
While both methods use genetic variants to infer causality, they address different questions. Mendelian randomization (MR) estimates the magnitude of a causal effect of an exposure on an outcome using variants as instruments. Colocalization asks a more fundamental question: do two traits share the same causal variant? Colocalization is often used to validate MR instruments by confirming the variant acts through the intended exposure.
Locus Definition and Sensitivity
Results are sensitive to the genomic window definition. A window that is too narrow may miss the true causal variant; too wide may include multiple independent signals. Standard practice uses a lead variant ± 200-500 kb or a defined number of LD blocks. Sensitivity analyses varying window size are recommended. The prior probability of colocalization also influences results and should be calibrated to the expected biology.
Frequently Asked Questions
Clear, technically precise answers to the most common questions about colocalization analysis, a critical statistical method for determining whether two traits share a causal genetic variant at a given genomic locus.
Colocalization analysis is a statistical method that assesses whether two potentially related traits share the same causal genetic variant at a specific genomic locus, supporting the hypothesis of a shared causal mechanism. It works by integrating GWAS summary statistics from two independent studies—typically an exposure trait (e.g., gene expression) and an outcome trait (e.g., disease risk)—and evaluating whether the observed association patterns are consistent with a single underlying causal variant. The method calculates posterior probabilities for five mutually exclusive hypotheses: (H0) no association with either trait, (H1) association with trait 1 only, (H2) association with trait 2 only, (H3) both traits associated but with distinct causal variants, and (H4) both traits associated and sharing a single causal variant. A high posterior probability for H4 (typically >0.75 or >0.80) provides strong evidence for colocalization, distinguishing true shared causal variants from coincidental overlap due to linkage disequilibrium.
Colocalization vs. Related Methods
Distinguishing colocalization analysis from other statistical genetics and causal inference methods used to prioritize causal variants and therapeutic targets.
| Feature | Colocalization Analysis | Mendelian Randomization | Fine-Mapping |
|---|---|---|---|
Primary Objective | Assess whether two traits share the same causal variant at a locus | Estimate the causal effect of an exposure on an outcome | Identify the most likely causal variant(s) within a credible set |
Input Data Required | GWAS summary statistics for two traits | GWAS summary statistics for exposure and outcome (two-sample MR) | GWAS summary statistics for a single trait plus LD reference panel |
Causal Inference | |||
Requires Instrumental Variables | |||
Accounts for LD Structure | |||
Output Metric | Posterior probability of shared causal variant (e.g., H4) | Causal effect estimate (beta coefficient) with confidence intervals | Posterior inclusion probability (PIP) per variant |
Pleiotropy Assessment | Distinguishes shared causality from distinct causal variants in LD | Sensitive to horizontal pleiotropy; requires MR-Egger or MR-PRESSO for robustness | Not directly assessed; assumes a single causal variant per locus |
Key Statistical Framework | Bayesian model comparison (e.g., COLOC, eCAVIAR) | Instrumental variable regression (e.g., IVW, MR-Egger) | Bayesian variable selection (e.g., SuSiE, FINEMAP) |
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Master the statistical and genetic epidemiology concepts essential for interpreting colocalization studies and distinguishing shared causal variants from mere genomic proximity.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us