Last updated March 2026
If you work in digital analytics or martech long enough in Utah County, you start to see the same names show up again and again: Omniture, Adobe, Domo, ObservePoint. What looks like a list of separate companies is really a connected story about how platforms evolve, how partners emerge, and how cooperation and competition often happen at the same time.
Let’s use the relationship between Adobe and ObservePoint as a simple case study in “coopetition” and game theory. The goal is not to predict their exact strategies, but to give marketers a clearer way to think about platform decisions, integrations, and why your favorite tools sometimes get embraced and other times get quietly replaced.
The Utah analytics lineage: Omniture → Adobe, Domo, ObservePoint
Omniture was one of the foundational companies in the web analytics space, and its acquisition by Adobe helped anchor a major analytics and marketing technology presence in Utah County. After the acquisition, talent and leadership from Omniture spread into new ventures, including Domo and ObservePoint.
Adobe became the home for enterprise analytics and experience tools like Adobe Analytics, Adobe Launch, and Customer Journey Analytics. ObservePoint, built by leaders with deep Omniture roots, focused on a complementary problem: making sure data collection actually works. That means automated tag auditing, data quality checks, and ongoing monitoring so that the numbers inside Adobe Analytics are trustworthy.
On paper, this looks like a classic complementary relationship. Adobe helps brands collect, analyze, and activate data. ObservePoint helps brands make sure that data is accurate. But under the surface, there is always a strategic question. This isn’t a story of conflict—platforms and partners often create enormous value together even while navigating natural tensions.
Should a platform like Adobe:
1. Stay open and lean on partners like ObservePoint
2. Or build more of those capabilities internally over time
Cooperation and competition in a simple game
We can describe this tension with a very simple two player game.
Player one is ObservePoint. Its main decision in this context is how much to invest in deep integration with Adobe. That includes building robust APIs, advanced auditing for Adobe tags, and tight workflows around Adobe Analytics and Customer Journey Analytics.
Player two is Adobe. Its main decision is how open to be as a platform partner. Adobe can keep APIs open, promote partners, and design its roadmap around an ecosystem. Or it can build more internal data quality and tag auditing features that compete with partners over time.
Here is a simple way to think about their choices.
| Adobe stays open to partners | Adobe builds more internal tools | |
| ObservePoint invests deeply in Adobe integrations | (high value for both) | (great for Adobe, risky for ObservePoint) |
| ObservePoint keeps integrations more minimal | (good but not great for both) | (lower value for both) |
When both sides lean into partnership, marketers get strong integration, better data quality, and a healthier ecosystem. When Adobe internalizes too much or ObservePoint under invests in integration, the value to marketers is lower, even if it feels safer in the short term to each company.
What this means for marketers
It is easy to assume platform decisions happen in a vacuum, but they rarely do. Companies like Adobe and ObservePoint are constantly weighing:
1. How much value a partner adds to the platform
2. How difficult that functionality would be to build in house
3. How much customers associate the benefit with the platform versus the partner
4. How much revenue and retention is at stake if the partnership grows or shrinks
For marketers and analytics leaders, this has a few practical implications.
First, deep integrations are not just technical conveniences. They are signals that incentives are aligned. When a platform and a partner make it easier to work together, they are often saying that they see long term mutual value in the relationship.
Second, you can often feel when the relationship is shifting. Fewer joint webinars, less co marketing, slower integration updates, or a sudden new native feature that looks a lot like a partner product are all signs that the game behind the scenes has changed.
Third, it is smart to design your measurement stack with these dynamics in mind. If a critical capability is provided only by a partner that feels strategically fragile, you should at least be aware of that risk and have a plan B over a multi year horizon.
Game theory without the jargon
In formal game theory language, platforms and partners are often stuck between what is called a Nash equilibrium and a socially optimal outcome.
The Nash equilibrium is the combination of strategies where neither side has an incentive to unilaterally change its decision. It is stable, but not always ideal for customers.
The socially optimal outcome is the combination of strategies that create the most total value for everyone involved, including the end customer. It is often more collaborative and more integrated, but it can be fragile if the incentives are not well aligned.
In the Adobe and ObservePoint story, the socially optimal outcome is the world where Adobe stays open and supportive of partners, and ObservePoint invests deeply in making Adobe data more accurate, actionable, and reliable. That is also the world where marketers get the strongest combined solution.
The strategic question is whether the incentives on both sides are strong enough to keep them there.
How platforms can keep cooperation sustainable
For cooperation to last in a relationship like Adobe and ObservePoint, both sides need to see more upside from partnering than from going their own way.
That usually means things like:
1. Clear revenue impact that can be tied back to the partnership
2. Integration depth that would be expensive to rebuild internally
3. Joint marketing and sales motions that benefit both companies
4. A customer story that is stronger together than either product alone
The more these conditions hold, the more the ecosystem behaves like a collaborative, high value game rather than a short term competition.
Why this matters for your own stack
You do not need to be Adobe or ObservePoint to apply this thinking. Any time you are building a marketing or analytics stack, you can ask a few simple questions.
1. Which tools are true platforms, and which are plug in partners
2. Where are incentives strongly aligned, and where are they more fragile
3. If one partner disappeared or got acquired, what breaks in your stack
4. Where can you lean into deep integrations that are likely to be supported for years
Thinking this way will not predict every roadmap change or acquisition, but it will help you design a more resilient measurement strategy and avoid being surprised when platform relationships evolve.
For me, the Adobe and ObservePoint story is a great example of how local Utah County companies can shape global martech while still reflecting very human, understandable trade-offs. Underneath all the platform terminology and economics, it is really just about two companies deciding when to cooperate, when to compete, and how much they believe they can win together.
