ETF Global vs Refinitiv: 2026 Compared

ETF Global vs Refinitiv: the short answer

The two products are positioned for different buyers, but that positioning has to be described carefully here: neither company's own website was part of the material fetched for this article on 24 September 2026, so no feature list, product line-up or scope claim is asserted for either one from memory. What can be sourced is narrow and is attributed below. If you want scored, opinionated ETF analytics, an ETF specialist is the category to shortlist; if you want a single contract covering several asset classes for an analyst desk, a generalist desktop is the category to shortlist, and the specialist will not close that gap.

ETF constituent data is the list of securities a fund or index holds on a given date, with weights, share or par amounts, and identifiers that let each line item be joined to a security master.

Neither vendor is the cheapest route if constituent files are the only thing you need. That is the gap this article is about: both of these products are sold through a quote rather than a published constituent-file price, and a quant team that wants a nightly CSV of holdings for a few thousand funds may be buying a great deal of infrastructure it will never open. A third shape exists, flat-file constituent delivery over FTP, and neither of the pages currently ranking for this comparison mentions it.

One process note before the detail. Everything stated below about another company comes from pages fetched on 24 September 2026 and is attributed and dated. Where a figure or a feature is not on those pages, this article says so rather than filling the gap.

What each vendor actually is in 2026

This section is deliberately thin, because the honest answer is that neither vendor's own pages were in the material available today. What follows is limited to sources that can be named and dated, which makes it less colourful than the ranking pages and more reliable than them.

On the Refinitiv side there is something concrete to point at. Lipper Alpha Insight, published at lipperalpha.refinitiv.com, carried a Monday Morning Memo on the global ETF industry dated 21 September 2026 reviewing August flows and noting that the global ETF industry saw very strong inflows over the month. That is a fair signal of what the Refinitiv-branded research operation does publicly: fund-flow analytics and industry commentary, produced continuously and available to read.

The generalist comparison pages reinforce a familiar framing from the other direction. Wall Street Prep's comparison of Bloomberg, Capital IQ, FactSet and Refinitiv, read on 24 September 2026, treats Refinitiv Eikon as one of four analyst desktops and organises the whole piece around pricing, banking workflows and desktop features. That is the frame nearly every ranking page uses, and it is the frame that leaves the data engineer's question unanswered.

For ETF Global there is no equivalent dated source in front of me. Its product scope, analytics line-up and delivery options are therefore treated here as unverified rather than described, and any claim you read elsewhere about what it includes should carry a date, because vendor pages in this market change quarterly. The same caution applies to Refinitiv's corporate structure and product naming, which this article does not assert.

A limit worth stating plainly: neither company's publicly readable pages, as read today, publish a per-seat or firm-wide figure for constituent data. No price is asserted here for either vendor. Anyone who tells you otherwise is quoting a number that was true on some unspecified date in the past.

Coverage: how many ETFs and indexes does each cover?

Coverage counts are the least comparable number in this market, because vendors count different things. One counts share classes, another counts funds; one counts indexes it licenses, another counts indexes it can reference by name. Before comparing two headline figures, establish what each one is actually counting.

Four coverage dimensions decide whether a vendor works for a constituent workflow:

• US-listed versus global ETFs. A US-only file is fine for a domestic factor book and useless for a global sleeve.
• Index constituents as distinct from fund holdings. The S&P 500 membership list and the SPY holdings file are different datasets that happen to look similar. A fund holds cash, futures and settlement lines; an index does not.
• Delisted and closed funds. If a fund that terminated in 2016 vanishes from the dataset, every backtest that touches it is survivorship-biased.
• Point-in-time history. Being able to retrieve the constituent list as it stood on a date, not as restated later.

Against those four, the concrete reference point on the AmericanETP side is 3,878 US and global indexes and US-traded ETFs, with archived constituent datafiles going back to July 2009. That archive matters more than the coverage count for anyone building historical factor exposures, because it is the difference between backfilling seventeen years and starting your history on the day you signed.

Verdict on coverage: no coverage count for either ETF Global or Refinitiv can be sourced from the material available today, so this criterion has to be settled in a quote. Ask both for a machine-readable list of the funds and indexes they cover, including terminated funds, rather than a headline number in a deck, and see ETF Constituent Lists: 2026 Data Guide for how to sanity-check the answers.

Delivery: terminal, API or flat CSV feed?

Delivery is the criterion that decides this comparison for engineering teams, and it is the one the ranking pages skip entirely. A desktop terminal, a request-response API and a scheduled flat file are three different products, and only one of them loads into a nightly pipeline without a human in the loop.

The terminal is built for a person: search, screen, chart, export. It is excellent for an analyst forming a view and structurally wrong for a job that needs 3,000 holdings files at 6pm every session. Export limits, entitlement checks and session-bound authentication are all reasonable for a desktop and all friction for a scheduler.

An API sits in between. It is the right shape for on-demand lookups, for an application that needs one fund's holdings when a user opens a page, and for teams that want to avoid managing file storage. It is the wrong shape for a full daily refresh of every fund you track, where you end up writing pagination, retry and rate-limit logic to reassemble a file the vendor could have handed you whole. That trade-off is worked through in detail in ETF Holdings Data API vs CSV Feeds.

Flat CSV over FTP is the least fashionable and most operationally boring option, which is the point. The file either arrived or it did not, the diff against yesterday is a one-line command, and reprocessing a month of history is a loop over a directory rather than 30 days of API calls. AmericanETP delivers constituent files this way, with FTP access available, and publishes a downloads area and a constituent change report for teams that care about membership deltas rather than full snapshots. The practical mechanics of a scheduled pull are covered in Daily ETF Holdings Download: 2026 Guide.

Verdict on delivery: if your users are humans reading screens, an analyst desktop is the right category and a CSV feed will disappoint them. If your user is a cron job, buy files, and confirm in writing which of the three shapes each vendor will actually deliver before you sign.

Update frequency and timing: when do holdings actually land?

"Daily" is a marketing word. The number that determines whether you can act on a file is the cutoff time and the timezone it is quoted in, and every vendor in this market says daily while meaning something different by it.

Consider what a same-evening rebalance actually requires: the file has to land after the US close, carry that session's holdings, and arrive early enough for your pipeline to validate it, diff it and generate orders before the desk goes home. A file that is stamped "daily" but lands at 4am the following morning is a T+1 file with a T+0 label. AmericanETP publishes a twice-daily schedule, with a primary update at 6pm EST and a secondary update around noon EST, which is a specific enough claim to test on day one of a trial.

Ask both ETF Global and Refinitiv these questions during an evaluation and get the answers in writing, because they are rarely on a public page:

Verdict on timing: neither vendor's public pages read today publish a constituent-file cutoff time, so this criterion cannot be decided from the web. It can be decided in ten sessions of a trial, and it should be, because it is not recoverable after signature.

Identifiers and joinability: FIGI, CUSIP, ISIN, tickers

Identifier coverage determines integration cost more reliably than content breadth does. A dataset with fewer fields that joins cleanly to your security master is cheaper to run than a richer dataset that ships tickers only and leaves you to build a mapping layer.

The failure mode is specific. Tickers are not unique across venues, they are recycled after delistings, and they change on corporate actions. A holdings file keyed only on ticker forces you to resolve each line against an exchange and a date, and every unmatched line becomes a manual exception. Multiply that by a few thousand funds a night and the mapping tax is a headcount cost, not a technical inconvenience.

Bloomberg's FIGI is an open identifier, which makes it useful as a spine precisely because it is not licensed per lookup. AmericanETP includes Bloomberg FIGIs in the holdings files of its constituent lists, and publishes Bloomberg extensions for teams working inside that ecosystem. CUSIP and ISIN remain the settlement-side keys most operations teams reconcile against, so a file that carries more than one of these gives you a fallback when the primary key misses.

The second join-key set is fund-level rather than security-level: the fundamentals file, which carries an ETF description, leverage indicator and constituent counts. Constituent counts are the cheapest validation you will ever implement, because a holdings file whose row count disagrees with the stated constituent count is wrong before you look at a single weight. Leverage flags matter for anyone screening or classifying funds programmatically, as does sector classification, covered in ETF List by Sector: 2026 Classification Guide.

Verdict on identifiers: if you need one identifier spine spanning several asset classes, ask each vendor to demonstrate it on your own instrument list rather than assuming it from brand reputation, because that is the claim most worth testing and the one least visible on a public page. If you only need fund holdings to join to an existing equity master, an open identifier in the file is enough, and you should not pay for a reference-data platform to get it.

Cost structure and licensing: what you are really buying

The price is rarely the expensive part of an enterprise data contract. The licence is. Seat counts, redistribution rights, derived-data clauses and internal-use-only restrictions decide whether the data you bought can appear in a client report, a public tearsheet or a product you sell.

Four clauses to read before anything else:

• Internal use only. Common, and fatal if you intended to show the data to clients.
• Derived data. Whether a factor score computed from the holdings is yours or remains the vendor's.
• Redistribution. Whether a fintech can surface the data inside its own application, and on what terms.
• Seat definition. Whether a headless service account counts as a user, which is where per-seat pricing and automated pipelines collide.

Neither ETF Global's nor Refinitiv's publicly readable pages, as read on 24 September 2026, publish a firm-wide figure for constituent data, so a quote is the only route to a number for either. Wall Street Prep's comparison article does include a pricing section for each platform it covers, but the material available here does not contain the figures, and quoting a price for a named company from memory is exactly the error this article refuses to make. For the shape of that question, see ETF Global Pricing: 2026 Cost Guide and Refinitiv Review 2026.

The one figure this article can state is AmericanETP's own, confirmed by a customer: $1,500 per year or $150 per month for an individual, and $2,500 per year or $250 per month firm-wide. Whatever else that is, it is a published number against which any quote can be benchmarked, and firm-wide means firm-wide rather than a seat count that grows with your engineering team.

Verdict on cost: if you are already buying multi-asset content under an existing contract, adding ETF constituents to it is worth pricing before you open a new vendor relationship. If constituent files are the entire requirement, a flat subscription is the lower-friction purchase and the licence is shorter to read.

Verdict by use case: quant fund, RIA, exchange, fintech

There is no single winner here, because the two products are not competing for the same budget line. The verdict depends entirely on whether you are buying opinions about ETFs, a research desktop, or raw membership files, and on which of those each vendor will confirm in writing.

Quant fund. You need point-in-time membership, survivorship-safe history and files that arrive on a schedule. Ask each vendor whether those three things are in scope before discussing anything else, because analytics and breadth you do not use still appear on the invoice. Compare against AmericanETP vs ETF Global 2026 before deciding.

RIA. If your workflow is client reporting and manager due diligence, a research desktop plus published fund-flow commentary of the kind Lipper Alpha Insight puts out may do more work per dollar than a constituent feed. An RIA that only needs look-through holdings for a handful of model portfolios is over-buying with either vendor.

Securities exchange or index provider. Breadth and reference-data depth matter, and so does redistribution licensing, which is usually where the serious conversation with a large generalist happens. See FactSet vs Refinitiv: 2026 Comparison for how the generalists stack against each other.

Fintech building on a feed. Your constraint is redistribution rights and predictable delivery, not desktop features. A flat-file subscription with a firm-wide licence is the shape that fits, which is the argument made in AmericanETP vs Refinitiv (LSEG) 2026 and in ETF Global vs FactSet: 2026 Compared.

How to run a fair 30-day evaluation of both

A trial that consists of logging in and looking around tells you nothing. Run the same five tests against both vendors, record the results, and let the numbers decide rather than the demo.

1. Pick five funds deliberately. One mega-cap US equity fund, one leveraged product, one global or emerging-market fund, one fixed-income ETF, and one fund that terminated before 2020. The last two are where vendors diverge.
2. Diff constituent counts against the issuer. Pull the issuer's own published holdings file for the same date and compare row counts and total weight. Explain every discrepancy before you accept the dataset.
3. Time the file for ten consecutive sessions. Record arrival timestamp, data date and row count each session. Ten data points separate a real cutoff from a marketing claim.
4. Attempt one full historical backfill. Ask for a specific date in 2012 and see what comes back, and in what format. Archives that exist in a sales deck sometimes do not exist in a directory.
5. Read the redistribution and derived-data clauses before signing. If the answer to "can this appear in our client-facing product" is not in the contract, it is not a yes.

Run the same protocol against a flat-file provider in parallel, so you have a control. ETF Global Alternatives: 2026 Options and Best ETF Global Alternatives 2026 list the candidates worth including in that third column.

FAQ

Is there a free alternative to Bloomberg?

There is no free equivalent, but there are free sources for parts of what a terminal provides. SEC filings, including N-PORT and N-CEN, give fund holdings on a regulatory schedule, and issuers publish daily holdings files for most US-listed ETFs on their own sites. The gap is not content, it is normalisation, timeliness and coverage in one place: free sources arrive in different formats, with different identifier conventions, at different times. For most institutional workflows the realistic answer is a low-cost specialist feed rather than a free substitute.

What is the difference between ETF holdings data and index constituent data?

ETF holdings data describes what a fund actually owns on a date, including cash, futures, currency hedges and settlement lines. Index constituent data describes the membership and weights of a benchmark, which is a construction rule rather than a portfolio. The two differ in practice because funds sample, optimise and hold residual cash, so an S&P 500 tracker's holdings file rarely matches the index membership line for line. Teams measuring tracking error need both, keyed to the same date.

Which global index ETF is the best?

This article does not recommend funds, and the question has no vendor-neutral answer, because best depends on the benchmark you want, your tax domicile and your cost tolerance. The data-side version of the question is answerable: compare funds on the benchmark they track, their published holdings overlap with that benchmark, and their constituent count against the index count. Those comparisons need a constituent dataset covering both the fund and the index it tracks.

What is Warren Buffett's favorite ETF?

This question circulates widely in commentary rather than in any dataset that can be verified from the sources available for this article, so no attribution is offered here. What is checkable is Berkshire Hathaway's 13F filings with the SEC, which disclose reportable US equity positions quarterly and are public. If the underlying interest is fund exposure rather than celebrity, the useful exercise is to take any large fund's constituent file and measure its overlap with the positions you already hold.

What is the 7% rule in ETF investing?

There is no standard definition of a 7% rule in ETF investing, and the phrase is used inconsistently across retail commentary, sometimes for a stop-loss threshold and sometimes for an assumed long-run return. Because it is not a defined industry convention, no vendor dataset implements it. Anything presented as a fixed rule with a number attached should be traced to a named source before it is relied on.

Can I download daily ETF holdings as CSV instead of using an API?

Yes. Flat CSV delivery, typically over FTP or a scheduled download, is the standard shape for teams loading holdings into a database rather than querying them interactively. AmericanETP delivers constituent lists as CSV files with Bloomberg FIGIs included in the holdings, on a twice-daily schedule with a primary 6pm EST update and a secondary update around noon EST, with archived files back to July 2009. The trade-off against an API is covered in ETF Holdings Data API vs CSV Feeds.

---

If the requirement is constituent files on a schedule rather than a desktop seat, compare the file itself: see what AmericanETP delivers, or get in touch with the five-fund test above and check the output against your own security master.