GTM AI Index

Index › Vendors › Firebase Cloud Messaging · September 2026 Edition

2 categories · Named, not ranked

Firebase Cloud Messaging

26Judge labels

0First choices

9Negative labels

9 of 12Models named it

2Categories

September 2026 Edition. Every number here is derived from the raw labels under vendor table v2026-09-16.3, every buyer segment counted.

Standing

9 labels, too few to rank

A product needs 10 labels in a category before a share or quadrant is stated. Firebase Cloud Messaging was named 9 times in Mobile & push and 1 other category, where OneSignal led with 34%. The labels and the evidence are below, counted exactly.

By buyer segmentRead the same way at every buyer size.

Small business23 of 68

under the label threshold

Mid-market24 of 75

under the label threshold

Enterprise111 of 111

under the label threshold

In mobile & push · each standing computed within its segment · bars are 0 to 100 · the accent bar is the product's own best reading

Standing by category

Every category where a model named Firebase Cloud Messaging for a mid-market B2B company. Share is first choices across the direct, paraphrase, budget and scale prompts; rank is within every product named in that category.

Category	Function	Share	Rank	Negative rate	Labels	Quadrant
Mobile marketing and push	Marketing	0%	24 of 75	12%	8	under 10 labels · led by OneSignal at 34%
Mobile apps	Marketing	0%	56 of 136	0%	1	under 10 labels · led by Meta Advantage+ App Campaigns at 15%

Movement

This is the first edition on this tier, so no move can be computed for Firebase Cloud Messaging yet. The next is due October 1, 2026. From the next edition this section shows, per buyer segment, whether its share moved by more than the measured noise floor.

By model

How each model treated Firebase Cloud Messaging across every prompt where it was named for a mid-market B2B company. Twelve models, six prompts per category.

Model	Alternative	Mention	Negative	Labels
Claude Haiku 4.5	0	1	0	1
GPT-5.4 mini	0	0	0	0
Gemini 3.5 Flash	0	0	0	0
Perplexity Sonar	2	0	0	2
Grok 4.1 Fast	1	0	0	1
Mistral Small	1	0	0	1
DeepSeek V4 Flash	0	0	0	0
Llama 4 Maverick	0	0	0	0
Qwen 3.7 Flash	0	0	0	0
Kimi K2	0	0	1	1
GLM 4.7 FlashX	1	0	0	1
MiniMax M2.5	1	1	0	2

By framing

Which of the six questions produced the naming. By model says how often; this says asked what. The first-choice count on the right carries the marks of the models that produced it.

FramingLabels by classFirst choices

Direct1 labelNone

Paraphrase1 labelNone

Comparative6 labelsNone

Budget-constrained9 labelsNone

Scale-constrained0 labelsNone

Negative9 labelsNone

First choiceAlternativeMentionNegative26 labels in all, every segment counted; 0 of the 0 first choices count toward share, since the comparative and negative framings do not. The bar is one segment per label class, to scale within the framing.

What the models said for it

Verbatim evidence the judge attached to positive labels.

“Developer-controlled infrastructure when you want flexibility and low lock-in, such as Firebase Cloud Messaging” Perplexity Sonar · Mobile & push · negative prompt · alternative

“cheapest option for push because it is free and unlimited, but it does not include the marketing console” Perplexity Sonar · Mobile & push · budget prompt · alternative

“Firebase: Completely free unlimited delivery (Google-backed), great for basics/analytics” Grok 4.1 Fast · Mobile apps · budget prompt · alternative

“Best Free Option: Firebase Cloud Messaging (FCM) ... Completely free” MiniMax M2.5 · Mobile & push · budget prompt · alternative

And against it

Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.

“Not a Complete Solution: Transport-only; no cross-channel fallback” Kimi K2 · Mobile & push · negative prompt · soft negative

Named alongside

The products named in the same answers as Firebase Cloud Messaging, over the 26 answers that named it. Took the first choice instead counts the answers where the other product was the first choice and Firebase Cloud Messaging was named but was not.

ProductSame answerTook the first choice insteadHead to head

OneSignal23 of 2613Not in the top three

Braze14 of 262Not in the top three

Courier9 of 260Not in the top three

Twilio Programmable Messaging9 of 260Not in the top three

Airship8 of 261Not in the top three

CleverTap7 of 260Not in the top three

Klaviyo7 of 260Not in the top three

MoEngage7 of 260Not in the top three

SlickText6 of 261Not in the top three

Attentive6 of 260Not in the top three

A head-to-head page exists where both products are in a category's top three. The other rows are the same fact without a page behind them, so they link to the product instead.

What carried it into the answer

The sites and pages cited by the answers that named Firebase Cloud Messaging. A fact about retrieval, not a lever on the model.

Citations exist only for the models that return a source list, four of the twelve in this edition, so these counts come from 7 of the 26 answers that named Firebase Cloud Messaging and are not a share of its labels.

Domains cited

courier.com7

engagelab.com6

guideflow.com6

moengage.com5

pushwoosh.com5

businessofapps.com4

g2.com4

omr.com4

pushengage.com4

sashido.io4

Forty-nine of the forty-nine domain citations in answers naming Firebase Cloud Messaging came from somebody else's page.

Pages cited

courier.com/blog/top-push-notification-platforms7

engagelab.com/blog/best-push-notification-service6

guideflow.com/blog/push-notification-software-tools6

guideflow.com/blog/best-mobile-marketing-software5

pushwoosh.com/blog/best-mobile-push-notification-services5

businessofapps.com/marketplace/push-notifications4

pushengage.com/best-push-notification-services4

pushwoosh.com/blog/mobile-push-notification-services4

Pages are listed as the models cited them.

Names read as Firebase Cloud Messaging

What the judge wrote, as written, with how often. The vendor table decides that these count as Firebase Cloud Messaging; a claim can dispute any of them.

Firebase Cloud Messaging (FCM) 5

Is this your product?

Claim this page

Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Firebase Cloud Messaging's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Firebase Cloud Messaging, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.

It does not get any change to labels, shares or verdicts, any preview, or any say over which quotes appear. A verification link goes to your work email; an address at firebase.com is approved on the spot, any other address is reviewed by hand.

Your name and company appear on the claimed page, or the company alone if you ask below. A title and a LinkedIn address appear there too if you give them, and are left off if you do not. Your email address is never published.