Desired outcome
Increase revenue by resolving issues that appear when a user attempts to complete an action.
Key performance indicators
Bottom of the Funnel Analysis measures the following KPIs:
KPI | Description | Goal |
---|---|---|
Bottom of the Funnel Success Rate/Conversion Rate | The rate of conversion once a user has gone far enough to demonstrate intent to complete an action to actual completion. Examples of this are rate of:
| Increase the rate of conversion by addressing errors and latency at the bottom of the funnel |
Revenue at Risk due to Latency | Value of a conversion * number of pages or interactions in the bottom of the funnel that are slower than the industry threshold. | Focus on reducing this value by improving page KPIs |
Revenue at Risk due to Errors | Value of a conversion * number of backend errors in the bottom of the funnel interactions | Tune this value to make it meaningful by filtering out errors that aren't visible to the end user. Once this is meaningful, focus on reducing it. Create an alert to notify you if it suddenly trends upward. |
Prerequisites
Required knowledge
- Familiarity with synthetic monitoring
- Familiarity with browser monitoring
- Familiarity with basic Browser UI views
- Familiarity with SPA data in Browser UI
Required installation and configuration
- Browser Pro installed in relevant pages
- SPA enabled for single page applications
- Insights retention for Browser events is at least 2x an average sprint.
Establish current state
Identify where the Bottom of the Funnel starts
The Bottom of the Funnel is focused on the final steps of a user journey where a user has gone far enough to show intent to complete the journey.
Some examples:
Ecommerce user journey
The user journey is simplified so you can focus on where the bottom of the funnel begins - at checkout. Most users entering the checkout phase plan to purchase something. Reducing errors and latency from this point onward is more likely to improve conversions than focusing on any other part of the funnel.
Car insurance purchase user journey
In the example above, you have the user’s interest in car insurance as they enter information, but you do not know their intent until they see the quote and continue to proceed.
Distinguish between Pages and Actions
The final steps of a user’s journey is likely to be a mix of full page loads and AJAX calls.
You will need to know all pages and Ajax requests for the next step. If you are not sure which requests are running from the page in question, you can run:
SELECT count(*) FROM AjaxRequest WHERE pageUrl like ‘%FILTER%’ FACET groupedRequestUrl SINCE 1 DAY AGO
Create a scripted Synthetics Check for the Bottom of the Funnel
Make sure you have a scripted monitor for each path through the bottom of the funnel. The goal is to make sure your bottom of the funnel services are working around the clock.
For example, you may have a checkout flow that calls a different payment API depending on the customer’s payment preferences.
Import the Bottom of the Funnel Dashboard
Follow the instructions documented in the public GitHub README.
Capture Current Performance
- Follow the GitHub repository README instructions.
- Use the dashboard from the previous step to understand the bottom of the funnel performance.
- Create a plan to improve KPIs that don’t meet target values as well as reduce revenue at risk.
Improvement process
Plan your work
Whether you have a dedicated initiative to improve performance or classifying as ongoing maintenance, you need to track your progress at the end of every sprint. For detailed information, see:
Advanced topics
Should I apply segmentation?
Segmentation (breaking out performance into cohorts, such as region and device type) is a good idea if:
- Your organization has initiatives tied to addressing a target audience from a particular cohort that you can segment by using either custom attributes or data that is already available in New Relic.
- You are already familiar with Bottom of the Funnel Analysis and there is a significant enough difference in performance among different cohorts to warrant tracking and/or developer focus.
Conclusion
Best practices going forward
- Revisit performance metrics at the end of each sprint.
- Any time the user journey changes, revisit if the steps at the Bottom of the Funnel are the same. Incorporate changes in developer sprints as needed.
- Openly share metrics with the lines of the business you support as well as other internal stakeholders.
- Revisit your Customer Experience SLOs. Do you need to define more ambitious SLOs for the end of the funnel?
- Create alerts for business critical drops in Quality Foundation KPIs.
Value realization
At the end of this process you should:
- Know your user conversion rate and have addressed errors or performance issues that negatively impact it.
- Increased revenue for your company.
- Created, or be on the path to create, a common language with business owners so you are working together; opening new avenues for recognition and sponsorship for new projects.
その他のヘルプ
さらに支援が必要な場合は、これらのサポートと学習リソースを確認してください:
- Explorers Hubでは、コミュニティからのサポートを受けたり、ディスカッションに参加したりすることができます。
- 当社サイトで答えを見つけて、サポートポータルの使用方法を確認してください。
- Linux、Windows、およびmacOS向けトラブルシューティングツールであるNew Relic Diagnosticsを実行してください。
- New Relicの とandドキュメント をご確認ください。