Gigya made the login worth keeping

A login button is a peculiar place to build a company. It occupies a few square inches of a screen. People click it because they want to be somewhere else. The better it works, the less anybody thinks about it. Gigya discovered that this small, forgettable transaction could lead to a much larger business. But getting there required the company to change direction twice.

The first business was already selling

Founded in 2006 by Rooly Eliezerov, Eyal Magen and Eran Kutner, Gigya initially helped content travel around the social web. Its Wildfire technology distributed widgets: little pieces of interactive content people could put on profiles and blogs. In 2008, DoubleClick incorporated Wildfire sharing into its advertising platform. Gigya helped advertisers get their creations into a user’s social circle.

Then the neighborhood changed. In a retrospective interview, future CEO Patrick Salyer recalled that the company was meeting revenue targets when Facebook’s rise made its earlier assumptions look fragile. Around 2009, Gigya turned toward selling social infrastructure to enterprises. The change replaced advertising economics with software subscriptions. A healthy sales report had concealed an unhealthy dependence on where the internet was going.

The customer who quietly leaves

The second warning came from inside the business. By early 2014, Salyer was confronting weak retention. Social features could sell, but too many customers treated them as optional. Gigya built on social login to pursue customer identity management, and concentrated on large enterprises. The move included closing a 40-person Phoenix office serving smaller businesses. Changing the product meant changing who could sell it, too.

“With the high churn rate, the math just didn’t work out.”

Patrick Salyer, recalling the second pivot

The useful distinction is between attracting attention and accepting responsibility. A social feature promises engagement. A registration system must remember who somebody is, connect accounts and keep working when that person returns. Once the customer relationship runs through that system, replacing it becomes a consequential project. That helps explain why identity offered Gigya a more durable position.

What the button was really doing

Gigya’s registration-as-a-service combined conventional account creation with social login. Someone could arrive with an existing identity rather than start from scratch. The software could link that identity to an existing site account and put information from different providers into consistent fields. Developers received APIs and tools for registration, authentication and profile management instead of assembling every component themselves.

The paying customers were businesses running consumer-facing properties. Historical customer lists included Fox, Forbes and Verizon; investor Mayfield also names Nestle and GSK. These companies had different products, but a shared administrative headache: recognizing customers across digital experiences without creating another disconnected collection of accounts. Gigya sold the infrastructure underneath those relationships, rather than a consumer destination of its own.

Its expertise sat at the junction of identity engineering and customer data. Authentication answers who can enter. Profiles and preferences help determine what happens afterward. Consent records establish what the business has permission to do. For a company operating several brands or channels, bringing those jobs together could reduce duplication and make personalization more accountable.

A large number needs a small footnote

Gigya occupied the customer identity and access management market, usually shortened to CIAM. Forrester’s 2017 evaluation placed it alongside Janrain, ForgeRock, Auth0, LoginRadius, Microsoft, Ping Identity and Salesforce. Its pitch connected consumer sign-in with usable customer information and permission. That combination gave marketing teams a reason to care about infrastructure that might otherwise have remained an engineering procurement decision.

The alternative was not always another vendor. An enterprise could maintain its own registration and authentication stack. Buying a platform shifts some maintenance to a specialist, while introducing integration work and dependence on that supplier. The trade makes more sense when account complexity, multiple properties and customer-data governance have become substantial jobs. A simple site with little need for persistent customer relationships has a different calculation.

The company’s workplace story had its own complications. Gigya received a Glassdoor Employees’ Choice Award for 2015 in the small and medium business category. Salyer described a culture built around relationships and community. Set beside the office closure, the award illustrates why a company’s reputation and its strategic choices need to be examined together: an appealing workplace could still face a painful reorganization.

The price of becoming necessary

Capital helped fund the transition. Gigya raised $25 million in 2013 and another $35 million in a 2014 round led by Intel Capital. Contemporary accounts put total funding above $100 million. The $35 million figure sometimes attached to Gigya is therefore a round, not its entire fundraising history. Those investments bought room to develop the product and expand the business.

For a present-day buyer, the relevant offer comes from SAP. Its Singapore pricing page lists Customer Identity and Access Management for B2C Core at SGD 424 a month per block of 10,000 active users, observed in October 2026. Enhanced security and broader consent capabilities are separate options. That is a current regional listing for a successor service, with implementation work to budget for separately.

The buyer was already next door

SAP’s acquisition announcement arrived in September 2017. Gigya had partnered with SAP Hybris since 2013, giving the proposed combination a working history. SAP wanted to connect Gigya’s consent-based identity platform with Hybris Profile’s data matching and enrichment. Public reports put the purchase at $350 million; SAP did not disclose the terms. A co-founder’s later SAP account dates completion to November.

Today, SAP places Gigya’s capabilities within its customer data portfolio. Even the old name persists in console addresses. The lesson for another founder is practical: investigate what customers can remove without much consequence. Then examine the adjacent work they must keep doing. Gigya’s opportunity lay a little beyond the button, where a passing visitor became a relationship somebody had to manage.