> For the complete documentation index, see [llms.txt](https://fiveelementslabs.gitbook.io/tide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fiveelementslabs.gitbook.io/tide/resources/case-studies/growth-challenges-for-bridges.md).
# Growth Challenges for Bridges
{% hint style="info" %}
The analysis has been performed by leveraging Tide analytics & performance suite
{% endhint %}
The Bridge space is harder than other web3 sectors. To avoid competing in a race-to-the-bottom with ever-decreasing fees, bridges need to implement successful marketing strategies. \
\
**Most Bridges have been running quests**, distributing POAPs, awarding Discord roles, and constantly deploying new campaigns to attract and retain users.
But **what is the ROI of marketing budgets on protocol growth?**
Let’s find out with a couple of cases:\
\
**1)Across Quest on Galxe**
The chart represents the share of transactions coming from users who participated in the *Ape into Arbitrum* Campaign on Galxe. \
It's clear that despite a transaction spike on Across from campaign participants it suddenly drops to the pre-campaign level, **indicating a negligible impact on new users and transactions.**
**2)Polygon Degen (LI.FI) on Galxe**
The chart shows the share of daily active users on LI.FI holding at least a Polygon Degens NFT. During the campaign period, this share spiked but quickly dropped just after it to levels that are lower than the pre-campaign average.
Like in [other cases](https://medium.com/@Tide_web3/data-driven-insights-for-optimizing-web3-marketing-budgets-13a9b4bfe78e) analyzed, **we see a minimal impact of quests on protocol metrics**.
## Final Insights
* First, it is imperative to start measuring what matters: protocol activity, revenues, active users, etc. It is very hard to find actionable data on *web3 performance marketing.* [**Tide team can help**](https://calendly.com/silvio-fiveelements/silvio).
* Regarding acquisition strategies, quests have severe limitations. Experimenting with new channels like referrals is a great idea.
* Retention is paramount to reach sustainability long term. Well-designed, data-driven, and personalized quests should be tested for loyalty on a recurrent basis.
\
**You can read the whole analysis** [**here**](https://medium.com/@Tide_web3/navigating-the-challenges-of-growth-in-the-bridge-space-980a5cff80b1)**.**
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://fiveelementslabs.gitbook.io/tide/resources/case-studies/growth-challenges-for-bridges.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.