What it does
Look-through portfolio analysis
Instead of stopping at the ETF ticker, the app follows supported child ETFs and rolls their holdings up into top holdings, sector exposure, country exposure, and ETF overlap.
About
BehindTheETF saves portfolios on this device, pulls supported fund holdings snapshots, expands ETF sleeves into underlying exposure, and shows where your money is actually concentrated.
Version 1.11.4
What it does
Instead of stopping at the ETF ticker, the app follows supported child ETFs and rolls their holdings up into top holdings, sector exposure, country exposure, and ETF overlap.
What to expect
Results depend on the latest stored holdings and price snapshots. If a fund is stale, unsupported, or missing, the app calls that out so you can refresh or investigate.
Guide
Open the dedicated Guide page for a cleaner walkthrough of portfolio setup, holdings look-through, overlap comparison, and best practices.
FAQ
Some provider snapshots do not include a clean sector or country label for every line item. When that happens, the exposure is still counted, but it is grouped as Unknown instead of being silently dropped.
Each ETF needs a supported official holdings source. If the app cannot match the fund to a supported provider or the provider does not return usable holdings, the app keeps the ETF visible and reports the issue clearly instead of showing fake data.
U.S. provider families currently wired into the app are iShares / BlackRock, Vanguard, VanEck, Roundhill, Schwab Asset Management, and Invesco U.S. Canadian provider families currently wired into the app are BlackRock Canada / iShares Canada, Vanguard Canada, BMO, CIBC, RBC, and TD.
In practice, support is mixed. Some providers are broad pattern-based importers, so many tickers in that issuer family are theoretically supported. Others still rely on a smaller direct list plus some broader discovery logic. That means a provider can be supported overall while a specific ticker still ends up unavailable, unsupported, or not found.
Yes. Holdings snapshots and prices are stored in the database, so later visits can use the latest saved data until you refresh again.
No. It is a practical snapshot workflow. Prices and holdings are refreshed on demand, then reused so the app stays fast and inexpensive to run.