AU Class
AU Class
class - AU

Developing Winning Business Models for Your Application

共享此课程
在视频、演示文稿幻灯片和讲义中搜索关键字:

说明

You have identified a key problem in your industry and have the perfect solution. Now you want to turn that idea into a business—but how do you decide on a price, and how do you reach customers? Using examples of apps built on Autodesk Platform Services, in this session we will explore potential business models to consider and help you think through how to price your app. We will also explore how you can use the Autodesk App Store to connect your app to a global market of Autodesk customers.

主要学习内容

  • Explore business model options and considerations for choosing one.
  • Gain tips on how to price your app on value instead of cost.
  • Learn how you can use the Autodesk App Store to connect with customers and build your business.

讲师

  • Erica Beffert
    Erica Beffert is the Senior Group Product Manager for Autodesk Platform Services. Her team works to growth Autodesk's portfolio of valuable APIs to help customers and partners connect data, teams and workflows. Her team also ensures a high quality developer experience through the APS Developer Portal and enables developers to distribute their apps and extensions through the Autodesk App Store. With 10+ years of software product management experience across several industries, Erica enjoys taking an incremental approach to collaboratively solving tough problems. When not at work you may find her learning new construction skills on YouTube to use in her next home renovation project.
  • Julia Brun 的头像
    Julia Brun
    Julia Eremeeva is a Business Development Manager on Developer Advocacy & Support Team. She has worked at Autodesk for 6+years supporting the Developer Partner Ecosystem in North America who actively customize Autodesk desktop products and use Autodesk Platform Services to enable Digital Transformation of their business. Julia also organizes global events for the Autodesk Developer Community such as accelerators, Developer Conferences, APS Tuesdays webinars, and online trainings.
Video Player is loading.
Current Time 0:00
Duration 0:00
Loaded: 0%
Stream Type LIVE
Remaining Time 0:00
 
1x
  • Chapters
  • descriptions off, selected
  • subtitles off, selected
      Transcript

      ERICA BEFFERT: Hello, and welcome to "Developing winning business models for your application." My name is Erica Beffert, and I'm the senior group product manager for Autodesk Platform Services. With me today is Julia Brun. Julia, do you want to introduce yourself?

      JULIA BRUN: Sure. Thank you, Erica. My name is Julia, and I work as a business development manager on developer advocacy team at Autodesk. Our team's mission is to make companies like yours successful with Autodesk developer technologies and also help you create your own value-driven solutions on top of Autodesk technologies. Erica, back to you.

      ERICA BEFFERT: Thank you. Before we go any further, I need to make you aware of our safe harbor statement. This presentation may contain forward-looking statements about our outlook, product capabilities and strategies.

      These statements reflect our best judgment based on currently-known factors. Actual events or results may differ materially. Please do not make any purchase decisions based on the contents of today's presentation.

      This class is focused on providing a framework for choosing the business model that is right for your company, your customers, and your product. Whether you are an independent software vendor and already develop and sell your own intellectual property, partner with customers to build custom solutions, or currently only build apps and integrations to use within your company, there's always an opportunity to think about what business model best suits your current business and what might you want to adopt in the future. Today's conversation will be divided into four parts, understanding your goals and constraints, choosing a business model, pricing your app, and reaching customers through the App Store.

      So let's first talk a little bit about the goals and constraints that can help decide which business model makes most sense for you. Company. Before you decide on a business model, it's important to understand what you want to achieve as a business. What is your revenue mix? What do you want it to be?

      Autodesk partners often derive revenue from varying ratios of agency and reseller payments, revenue from services or custom software, and revenue from products or selling intellectual property. What is your goal? Do you want to make money from selling a software product or selling services and custom software?

      Your customer goals and constraints. What are your customers' goals? What motivates them and what are they trying to achieve? And how are you helping them achieve that? What do they value and what would they be willing to pay for?

      This is critical, especially if you're considering a customized solution. What other products do they use and what business models might they already be familiar with from using these products? These don't necessarily need to be competitive products, but could just be other types of products that they may use in their day-to-day business activities.

      Competition. What are the alternatives to your product in the market? What types of business models are those products offering? And what are your customers think about them? It's also important to remember that the status quo or doing nothing or continuing to do what you're doing today is also a competitor and has a business model.

      Finally, product. What type of software do you have? Is it a desktop plugin or is it a cloud service? If it's cloud, is it single-tenant or multi-tenant? These types of things are going to impact the business model that will be easiest for you and your customer to understand.

      Do you intend to customize your software? Or do you want to have a product that's basically the same thing with a few configurations to differentiate it? What do your customers want? More importantly, what are they willing to pay for?

      After you've spent some time considering these goals and constraints, it's time to look at your business model options. This is not an exhaustive list of all the possible business models. We have selected a few with one strong preference, but what is best for your company is going to depend on some of the factors we've mentioned and also maybe some other ones that are unique to your situation.

      So the first is subscription. Under the subscription model, your customer pays you a fixed monthly or annual fee to use your product. Your subscription price can be per company, per user, or some other unit of value, such as project. And you may offer subscription tiers if you have companies that are using your product in different amounts. Under this situation, you treat your Autodesk Platform Services costs as a cost of doing business.

      Some of the advantages or some of the reasons why you should choose a subscription over a different type of business model include that your customer requires a non-variable price. They don't want to see the amount that they're paying you go up and down every month. It's especially useful to have a subscription if you have a cloud or cloud-connected app. And if your product is going to be configured rather than customized, subscription is really the way to go.

      Also, if you see usage patterns that vary in predictable ways across your customer base, this will help make it easier for you to implement tiering. On the other hand, subscription may not be the right choice for you if your each client requires a lot of customization. This may also be because, for example, you're offering something that is new to the market and patterns haven't yet emerged about how customers want to use your software. Also, if usage varies widely between your customers and it's not in predictable ways that would allow you to create tiers, subscription might not be your best choice.

      So option-- the second type of business model that you can choose is hybrid subscription and consumption. Under this model, your customer is paying you for the subscription for your product, and they're also paying you that variable consumption rate that is oftentimes based on your APS costs. And then you are passing along or you're paying those APS costs on to Autodesk.

      Option two is that you are directly charging the customer or the customer is directly paying with APS. Under this situation, your customer pays you the fixed monthly subscription fee or annual, and your customer pays Autodesk directly for their APS usage.

      So why are some-- what are some reasons why you might want to choose this option? Or why it might be the best option for you? So first of all, if you have an app that you have created, maybe you've put it in the App Store to use to generate marketing leads, and you're not charging anything for this app, then going with the hybrid approach and having the customer pay directly for their APS usage while they pay a $0 subscription to you may be a better option.

      Or you simply want your customers to have more visibility into the costs of running your app. On the other hand, if your customers require a predictable, fixed-recurring cost, then passing those consumption charges on to them may not be the best situation. Also, having the charge broken up between the fixed subscription costs and the variable consumption cost to the same customer is a little bit more complicated and might be harder for you to explain to your customers. Finally, if you don't want to have to build and manage a system to track how much your customers are using your application, then, again, going with a standard, fixed-subscription rate may be a better option.

      So custom solutions. For those of you that are building custom solutions, either because that simply is your business model or, like I had mentioned earlier, you're bringing out something new in the market where you want to work with a couple of customers first before you attempt to productize it, then you should probably go with a custom solution and the custom pricing. And the way that this typically works is you are building a custom solution for each of your customers.

      Either you're starting from scratch or you have some sort of base configuration and then you're going to customize the code on top of that. And your customer pays you an initial development fee plus an ongoing maintenance fee to handle the fact that you are effectively creating them a bespoke code. This can be an advantage if your customer's requirements are genuinely unique, you don't see any patterns, and you haven't yet seen a path to productize the solution.

      And most importantly, your target customers are willing and able to pay for custom software. It's very common for customers to want custom software. It's less common for them to be able or willing to pay for it. It's not necessarily-- I would stay away from the custom solution model if you are looking to scale quickly. If each of your customers has a different code base and you're maintaining it separately for them, you're not going to be able to onboard customers very quickly, because there's a high support cost due to separate code bases and unique workflows.

      OK. So after you've looked through those types of things, you have a better understanding of what your company goals are and what your product goals are and sort of looked at some of your options. How do you go about pricing your app? So I think the take-home message for this will be it's important to understand your costs, but you should price your app based on the value that it is giving to your customers.

      But let's talk about pricing. There are many costs that go into developing and running a software product. And APS usage costs are just one of them, but they're the one that we get questions about, so they're the one that we'll walk you through a little bit on how to estimate those costs both before you build and then after you build your software. But ultimately, what those costs are going to be are going to depend on many things, depend on which APIs you're using.

      And it's going to depend on your customer usage pattern. So deciding how much you're going to charge for app isn't a one-time exercise. And here are the steps that you can generally go through to help you understand. So first of all, during the phase when your team is developing the application, they're doing maybe a proof of concept. And you're starting to get a better understanding of what APIs are going to use.

      You can go ahead and begin to start estimating what your costs would be. This is really a hypothesis that you have based on the APIs that you're using. And you can use the APS token estimator tool, which I've put a QR code to in the slide, which will walk you through some of the most common use cases and help you think about how you can estimate in advance what your costs might be. Second, take advantage of your beta phase, not just to get that product market fit with the offering of your product, but also to better understand how customers are using your application and what the costs might be associated with that usage.

      A couple of tips here is that think about trying to select beta partners for your program that reflect the diversity of your expected user base so that you can see different types of usage patterns during the beta. And that will help you better estimate your costs. Also, look at those that usage and see if it clusters into any tiers or whether it was going to make sense for you to just offer one flat subscription offering.

      Finally, as good as your hypothesis might have been and as good as your observations may have been during the beta, it's always important to observe and adjust after that introduction to the market. So we recommend consider listing your initial price as introductory to set the expectations that prices may change the first, say, three to six months after you go into the market, and continue to track and evaluate usage after launch.

      OK. So you've got a handle on what your costs might be. Now, how do you go about actually pricing on the value that you're bringing to customers? And the questions that you should ask yourself and your company as you're going about pricing it are also the types of questions that, when you have good answers to them, are going to help you have that conversation with your customer and sell them on the value of your application.

      As we talked about at the very beginning, it's really important to understand what your customer's goals are and what they value. Where are they looking to make money? Where do they see their business going? And how does your application or the service that you're providing help them to achieve those outcomes? It's also important to understand how are they achieving those outcomes today.

      What is their status quo? And how much does that cost them? This might be if, for example, your application is going to help them automate a business process. How many people are involved in that business process today? How many hours?

      What are they paying them? Help anchor the value of your product in the value or the expense of the solution today. And also be thinking about what if they don't solve this problem. What is the cost to their business of doing nothing? And I think once you walk through those different examples, a lot of times you may understand that you are undervaluing your application when you think about the value that it's bringing to your customer.

      All right. So that's a little bit about some of the business models that are available and how to go about pricing your app. I'm now going to hand things over to Julia, who's going to talk to you about how you can reach more customers by listing your app on the Autodesk App Store. Thank you.

      JULIA BRUN: Now we are moving to a part where we will show you how you can reach customers, sell your solutions, and do all of that successfully. We're going to talk about Autodesk App Store. For those who are new to the Autodesk App Store, it is a marketplace and a web service provided by Autodesk. You can search for hundreds of applications, whether that's plugins for Autodesk Revit, Maya, Inventor, and more, or its integrations and cloud applications powered by Autodesk Platform Services.

      App Store is a platform where you can find and download a solution that fits your needs. Autodesk App Store is also a place where you can publish your own solutions and share your app with thousands of Autodesk customers across the world. The apps found on App Store are created by third-party developers as well as Autodesk. We at Autodesk place a very high emphasis on maintaining the quality of the app content, as well as delivering top-class user experience that makes it easy to discover and get apps. We also prioritize creating a space where developers, maybe like you, can distribute their apps successfully. And the goal here is to enable developers to find new customers, build, and extend their business.

      To number lovers out here, let's learn more about the App Store statistics. Autodesk App Store was started in 2012 with AutoCAD as the main product and with only 170 apps total available to customers. Fast forward to today, in 2024, we have more than 4,000 applications.

      And each year, there are hundreds of new apps that get added to the App Store. For example, this year, from 2023 to 2024, we added 507 new applications. And it wouldn't have been possible without third-party developer contribution.

      OK. I have a few more numbers for you. The App Store developer community is 1,000 publishers. And there are also four million-- almost four million total visitors per year.

      You might be wondering, where are those visitors located? Well, they are distributed across 170 countries. So you can see that you have access to multiple different regions and markets.

      On this slide, we will talk about how to get started as a publisher and walk through the steps of the publication process. Let's set expectations. Publishing on the App Store can take anywhere between one to four weeks, depending on a few things. One, understanding of a publishing process. Two, the completeness and accuracy of the app data submitted.

      This is really important, because that can either save you weeks or extend the process by multiple months. So let's break down the steps. You start with an onboarding process that includes creating an account for a publisher, setting up payment account information if you plan to publish paid apps, and lastly, submitting app-related information. Next, the app submission moves to the admin review stage. App Store admins will reach out to developers with requests for more information or update recommendations.

      Your successful app listing is the team's number one priority and number one goal. Once the app is published, there are a separate set of activities that publisher gets involved in. That includes app management, meaning updating the app yearly with the latest version of Autodesk products and releasing new versions, app monitoring, which includes customer engagement and app performance through dashboards, and then customer support in case of incoming requests from customers. You can also set up troubleshooting and ticketing system for those questions.

      Now let's move to the fun part. In the next few slides, we will talk about the most valuable tips and tricks for creating an effective and engaging app listing. Based on our App Store team's research, more than 65% of all App Store users land on the App Details page.

      But what's more important, and now pay attention, on average, a user spends only three minutes on the App Details page. So what does it mean? It means that you only have three minutes to capture users' attention. Good news is that we have a few tips and tricks for you to help you make the most out of those three minutes.

      If you are considering publishing an app or already have an app listing, take a piece of paper and a pen. We looked at top 10 apps on the store and we identified a few things those app listings had in common. Based on that information, we created a simple checklist that can help you uplevel your App Store presence. So let's go through that.

      Does your application have a compelling app description, which is a clear, concise, and engaging app description highlighting key features and benefits of your application? Does your application have visual assets? That might include eye-catching app icons and screenshots, images showcasing the app's user interface and functionality, and so on. Does your application have app reviews and ratings? This is important.

      Do you make sure you encourage positive user reviews and ratings and also address user feedback to improve the app quality? Now, does your application have regular updates? That means providing consistent app updates with improvements showing your commitment to user satisfaction. And lastly, did you do competitor analysis? Did you study successful apps in your niche? Did you identify strengths and weaknesses to differentiate?

      If you have four or five yes responses, then congratulations. Your app is off to a great start. However, if you responded yes to less than three points, we strongly, strongly recommend reimagining your app listing. That's the time to do that.

      This slide summarizes best practices based on our research of successful app publishers. It has lots of good tips, so please pause this recording and take a screenshot. And then we'll move on.

      Now, you might be wondering if and how Autodesk helps publishers to be successful on the App Store. We have a few co-marketing activities that you can take advantage of. First, we can feature your app on the App Store. We can also place a marketing banner you create at the top of the App Store for maximum visibility. Next, there is an opportunity to be featured on our social media platforms.

      To do that, participate in ongoing customer research, usability interviews, et cetera, and contribute to shaping up our product. And then event collaboration. Feel free to collaborate with us at events to promote your app. And in some cases, you may be invited to events with our support, often at no cost to you. We are eager to partner with you and support your app's success, so feel free to reach out.

      So far, you heard Autodesk talking. Let's now listen to a story of an App Store publisher. I will tell you the experience of Plex-Earth. Plex-Earth is the maker of Plex-Earth app, Plex-Earth Lite, and Plex-Earth for Autodesk Forma published on Autodesk App Store. Plex-Earth gives engineers the complete 3D geographical view of their project area with imagery and data from leading satellite providers.

      They shared with us three key benefits and opportunities that helped them be successful on the marketplace. First, focusing on customer needs and recurring revenue. They prioritize customer needs and focus on their core competencies. They also meet customer needs at various levels, from drafters and CAD users to high-level decision makers. And they ensure predictable revenue streams through subscription-based pricing.

      The second pillar or benefit is increasing credibility and building awareness. Autodesk App Store enabled them to reach thousands of potential customers and expand their reach. And here's a fun fact for you. Formula One, F1, a high-profile organization, discovered Plex-Earth through the App Store. And finally, the third pillar is lead generation opportunities.

      Their Lite or free to Pro model created an effective structure for lead generation. They generated a lot of leads through content marketing rather than a dedicated sales team. And last year, Plex-Earth apps had more than 7,000 downloads. And that connected them with some of their best customers.

      Before you go, I do have two more slides for you. Please don't be shy and reach out to us. If you need to talk to someone about partnership opportunities and get business support in your application, send us an email at aps.business@autodesk.com. If you have any questions around your application submission and need to contact our App Store team, please reach out to appsubmissions@autodesk.com.

      Last but not least, we also have two events coming up after Autodesk University. First, we have an online training for software developers in the basics of Autodesk Platform Services. If you or someone on your team is just getting started with APS, then this training is exactly what they need. It's free, and it covers four different topics. You can attend one or all four days.

      Second event. If you would like to get support on your powered application and prepare it for publishing on the App Store, then you should sign up for our accelerator in Atlanta in December. The attendance is also free of charge, but we do need an application from you describing your APS project. APS Accelerators are a week-long, technical support event where you bring your software development project and get technical support from APS engineers. And we do organize some fun activities outside of those coding hours.

      With that, thank you very much for being a part of this session. I hope you enjoyed it, and I look forward to seeing you at one of our future events. Take care.

      ______
      icon-svg-close-thick

      Cookie 首选项

      您的隐私对我们非常重要,为您提供出色的体验是我们的责任。为了帮助自定义信息和构建应用程序,我们会收集有关您如何使用此站点的数据。

      我们是否可以收集并使用您的数据?

      详细了解我们使用的第三方服务以及我们的隐私声明

      绝对必要 – 我们的网站正常运行并为您提供服务所必需的

      通过这些 Cookie,我们可以记录您的偏好或登录信息,响应您的请求或完成购物车中物品或服务的订购。

      改善您的体验 – 使我们能够为您展示与您相关的内容

      通过这些 Cookie,我们可以提供增强的功能和个性化服务。可能由我们或第三方提供商进行设置,我们会利用其服务为您提供定制的信息和体验。如果您不允许使用这些 Cookie,可能会无法使用某些或全部服务。

      定制您的广告 – 允许我们为您提供针对性的广告

      这些 Cookie 会根据您的活动和兴趣收集有关您的数据,以便向您显示相关广告并跟踪其效果。通过收集这些数据,我们可以更有针对性地向您显示与您的兴趣相关的广告。如果您不允许使用这些 Cookie,您看到的广告将缺乏针对性。

      icon-svg-close-thick

      第三方服务

      详细了解每个类别中我们所用的第三方服务,以及我们如何使用所收集的与您的网络活动相关的数据。

      icon-svg-hide-thick

      icon-svg-show-thick

      绝对必要 – 我们的网站正常运行并为您提供服务所必需的

      Qualtrics
      我们通过 Qualtrics 借助调查或联机表单获得您的反馈。您可能会被随机选定参与某项调查,或者您可以主动向我们提供反馈。填写调查之前,我们将收集数据以更好地了解您所执行的操作。这有助于我们解决您可能遇到的问题。. Qualtrics 隐私政策
      Akamai mPulse
      我们通过 Akamai mPulse 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Akamai mPulse 隐私政策
      Digital River
      我们通过 Digital River 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Digital River 隐私政策
      Dynatrace
      我们通过 Dynatrace 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Dynatrace 隐私政策
      Khoros
      我们通过 Khoros 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Khoros 隐私政策
      Launch Darkly
      我们通过 Launch Darkly 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Launch Darkly 隐私政策
      New Relic
      我们通过 New Relic 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. New Relic 隐私政策
      Salesforce Live Agent
      我们通过 Salesforce Live Agent 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Salesforce Live Agent 隐私政策
      Wistia
      我们通过 Wistia 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Wistia 隐私政策
      Tealium
      我们通过 Tealium 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Tealium 隐私政策
      Upsellit
      我们通过 Upsellit 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Upsellit 隐私政策
      CJ Affiliates
      我们通过 CJ Affiliates 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. CJ Affiliates 隐私政策
      Commission Factory
      我们通过 Commission Factory 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Commission Factory 隐私政策
      Google Analytics (Strictly Necessary)
      我们通过 Google Analytics (Strictly Necessary) 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Google Analytics (Strictly Necessary) 隐私政策
      Typepad Stats
      我们通过 Typepad Stats 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Typepad Stats 隐私政策
      Geo Targetly
      我们使用 Geo Targetly 将网站访问者引导至最合适的网页并/或根据他们的位置提供量身定制的内容。 Geo Targetly 使用网站访问者的 IP 地址确定访问者设备的大致位置。 这有助于确保访问者以其(最有可能的)本地语言浏览内容。Geo Targetly 隐私政策
      SpeedCurve
      我们使用 SpeedCurve 来监控和衡量您的网站体验的性能,具体因素为网页加载时间以及后续元素(如图像、脚本和文本)的响应能力。SpeedCurve 隐私政策
      Qualified
      Qualified is the Autodesk Live Chat agent platform. This platform provides services to allow our customers to communicate in real-time with Autodesk support. We may collect unique ID for specific browser sessions during a chat. Qualified Privacy Policy

      icon-svg-hide-thick

      icon-svg-show-thick

      改善您的体验 – 使我们能够为您展示与您相关的内容

      Google Optimize
      我们通过 Google Optimize 测试站点上的新功能并自定义您对这些功能的体验。为此,我们将收集与您在站点中的活动相关的数据。此数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID 等。根据功能测试,您可能会体验不同版本的站点;或者,根据访问者属性,您可能会查看个性化内容。. Google Optimize 隐私政策
      ClickTale
      我们通过 ClickTale 更好地了解您可能会在站点的哪些方面遇到困难。我们通过会话记录来帮助了解您与站点的交互方式,包括页面上的各种元素。将隐藏可能会识别个人身份的信息,而不会收集此信息。. ClickTale 隐私政策
      OneSignal
      我们通过 OneSignal 在 OneSignal 提供支持的站点上投放数字广告。根据 OneSignal 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 OneSignal 收集的与您相关的数据相整合。我们利用发送给 OneSignal 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. OneSignal 隐私政策
      Optimizely
      我们通过 Optimizely 测试站点上的新功能并自定义您对这些功能的体验。为此,我们将收集与您在站点中的活动相关的数据。此数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID 等。根据功能测试,您可能会体验不同版本的站点;或者,根据访问者属性,您可能会查看个性化内容。. Optimizely 隐私政策
      Amplitude
      我们通过 Amplitude 测试站点上的新功能并自定义您对这些功能的体验。为此,我们将收集与您在站点中的活动相关的数据。此数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID 等。根据功能测试,您可能会体验不同版本的站点;或者,根据访问者属性,您可能会查看个性化内容。. Amplitude 隐私政策
      Snowplow
      我们通过 Snowplow 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Snowplow 隐私政策
      UserVoice
      我们通过 UserVoice 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. UserVoice 隐私政策
      Clearbit
      Clearbit 允许实时数据扩充,为客户提供个性化且相关的体验。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。Clearbit 隐私政策
      YouTube
      YouTube 是一个视频共享平台,允许用户在我们的网站上查看和共享嵌入视频。YouTube 提供关于视频性能的观看指标。 YouTube 隐私政策

      icon-svg-hide-thick

      icon-svg-show-thick

      定制您的广告 – 允许我们为您提供针对性的广告

      Adobe Analytics
      我们通过 Adobe Analytics 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Adobe Analytics 隐私政策
      Google Analytics (Web Analytics)
      我们通过 Google Analytics (Web Analytics) 收集与您在我们站点中的活动相关的数据。这可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。我们使用此数据来衡量我们站点的性能并评估联机体验的难易程度,以便我们改进相关功能。此外,我们还将使用高级分析方法来优化电子邮件体验、客户支持体验和销售体验。. Google Analytics (Web Analytics) 隐私政策
      AdWords
      我们通过 AdWords 在 AdWords 提供支持的站点上投放数字广告。根据 AdWords 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 AdWords 收集的与您相关的数据相整合。我们利用发送给 AdWords 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. AdWords 隐私政策
      Marketo
      我们通过 Marketo 更及时地向您发送相关电子邮件内容。为此,我们收集与以下各项相关的数据:您的网络活动,您对我们所发送电子邮件的响应。收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、电子邮件打开率、单击的链接等。我们可能会将此数据与从其他信息源收集的数据相整合,以根据高级分析处理方法向您提供改进的销售体验或客户服务体验以及更相关的内容。. Marketo 隐私政策
      Doubleclick
      我们通过 Doubleclick 在 Doubleclick 提供支持的站点上投放数字广告。根据 Doubleclick 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Doubleclick 收集的与您相关的数据相整合。我们利用发送给 Doubleclick 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Doubleclick 隐私政策
      HubSpot
      我们通过 HubSpot 更及时地向您发送相关电子邮件内容。为此,我们收集与以下各项相关的数据:您的网络活动,您对我们所发送电子邮件的响应。收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、电子邮件打开率、单击的链接等。. HubSpot 隐私政策
      Twitter
      我们通过 Twitter 在 Twitter 提供支持的站点上投放数字广告。根据 Twitter 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Twitter 收集的与您相关的数据相整合。我们利用发送给 Twitter 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Twitter 隐私政策
      Facebook
      我们通过 Facebook 在 Facebook 提供支持的站点上投放数字广告。根据 Facebook 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Facebook 收集的与您相关的数据相整合。我们利用发送给 Facebook 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Facebook 隐私政策
      LinkedIn
      我们通过 LinkedIn 在 LinkedIn 提供支持的站点上投放数字广告。根据 LinkedIn 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 LinkedIn 收集的与您相关的数据相整合。我们利用发送给 LinkedIn 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. LinkedIn 隐私政策
      Yahoo! Japan
      我们通过 Yahoo! Japan 在 Yahoo! Japan 提供支持的站点上投放数字广告。根据 Yahoo! Japan 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Yahoo! Japan 收集的与您相关的数据相整合。我们利用发送给 Yahoo! Japan 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Yahoo! Japan 隐私政策
      Naver
      我们通过 Naver 在 Naver 提供支持的站点上投放数字广告。根据 Naver 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Naver 收集的与您相关的数据相整合。我们利用发送给 Naver 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Naver 隐私政策
      Quantcast
      我们通过 Quantcast 在 Quantcast 提供支持的站点上投放数字广告。根据 Quantcast 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Quantcast 收集的与您相关的数据相整合。我们利用发送给 Quantcast 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Quantcast 隐私政策
      Call Tracking
      我们通过 Call Tracking 为推广活动提供专属的电话号码。从而,使您可以更快地联系我们的支持人员并帮助我们更精确地评估我们的表现。我们可能会通过提供的电话号码收集与您在站点中的活动相关的数据。. Call Tracking 隐私政策
      Wunderkind
      我们通过 Wunderkind 在 Wunderkind 提供支持的站点上投放数字广告。根据 Wunderkind 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Wunderkind 收集的与您相关的数据相整合。我们利用发送给 Wunderkind 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Wunderkind 隐私政策
      ADC Media
      我们通过 ADC Media 在 ADC Media 提供支持的站点上投放数字广告。根据 ADC Media 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 ADC Media 收集的与您相关的数据相整合。我们利用发送给 ADC Media 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. ADC Media 隐私政策
      AgrantSEM
      我们通过 AgrantSEM 在 AgrantSEM 提供支持的站点上投放数字广告。根据 AgrantSEM 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 AgrantSEM 收集的与您相关的数据相整合。我们利用发送给 AgrantSEM 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. AgrantSEM 隐私政策
      Bidtellect
      我们通过 Bidtellect 在 Bidtellect 提供支持的站点上投放数字广告。根据 Bidtellect 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Bidtellect 收集的与您相关的数据相整合。我们利用发送给 Bidtellect 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Bidtellect 隐私政策
      Bing
      我们通过 Bing 在 Bing 提供支持的站点上投放数字广告。根据 Bing 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Bing 收集的与您相关的数据相整合。我们利用发送给 Bing 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Bing 隐私政策
      G2Crowd
      我们通过 G2Crowd 在 G2Crowd 提供支持的站点上投放数字广告。根据 G2Crowd 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 G2Crowd 收集的与您相关的数据相整合。我们利用发送给 G2Crowd 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. G2Crowd 隐私政策
      NMPI Display
      我们通过 NMPI Display 在 NMPI Display 提供支持的站点上投放数字广告。根据 NMPI Display 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 NMPI Display 收集的与您相关的数据相整合。我们利用发送给 NMPI Display 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. NMPI Display 隐私政策
      VK
      我们通过 VK 在 VK 提供支持的站点上投放数字广告。根据 VK 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 VK 收集的与您相关的数据相整合。我们利用发送给 VK 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. VK 隐私政策
      Adobe Target
      我们通过 Adobe Target 测试站点上的新功能并自定义您对这些功能的体验。为此,我们将收集与您在站点中的活动相关的数据。此数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID、您的 Autodesk ID 等。根据功能测试,您可能会体验不同版本的站点;或者,根据访问者属性,您可能会查看个性化内容。. Adobe Target 隐私政策
      Google Analytics (Advertising)
      我们通过 Google Analytics (Advertising) 在 Google Analytics (Advertising) 提供支持的站点上投放数字广告。根据 Google Analytics (Advertising) 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Google Analytics (Advertising) 收集的与您相关的数据相整合。我们利用发送给 Google Analytics (Advertising) 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Google Analytics (Advertising) 隐私政策
      Trendkite
      我们通过 Trendkite 在 Trendkite 提供支持的站点上投放数字广告。根据 Trendkite 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Trendkite 收集的与您相关的数据相整合。我们利用发送给 Trendkite 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Trendkite 隐私政策
      Hotjar
      我们通过 Hotjar 在 Hotjar 提供支持的站点上投放数字广告。根据 Hotjar 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Hotjar 收集的与您相关的数据相整合。我们利用发送给 Hotjar 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Hotjar 隐私政策
      6 Sense
      我们通过 6 Sense 在 6 Sense 提供支持的站点上投放数字广告。根据 6 Sense 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 6 Sense 收集的与您相关的数据相整合。我们利用发送给 6 Sense 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. 6 Sense 隐私政策
      Terminus
      我们通过 Terminus 在 Terminus 提供支持的站点上投放数字广告。根据 Terminus 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 Terminus 收集的与您相关的数据相整合。我们利用发送给 Terminus 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. Terminus 隐私政策
      StackAdapt
      我们通过 StackAdapt 在 StackAdapt 提供支持的站点上投放数字广告。根据 StackAdapt 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 StackAdapt 收集的与您相关的数据相整合。我们利用发送给 StackAdapt 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. StackAdapt 隐私政策
      The Trade Desk
      我们通过 The Trade Desk 在 The Trade Desk 提供支持的站点上投放数字广告。根据 The Trade Desk 数据以及我们收集的与您在站点中的活动相关的数据,有针对性地提供广告。我们收集的数据可能包含您访问的页面、您启动的试用版、您播放的视频、您购买的东西、您的 IP 地址或设备 ID。可能会将此信息与 The Trade Desk 收集的与您相关的数据相整合。我们利用发送给 The Trade Desk 的数据为您提供更具个性化的数字广告体验并向您展现相关性更强的广告。. The Trade Desk 隐私政策
      RollWorks
      We use RollWorks to deploy digital advertising on sites supported by RollWorks. Ads are based on both RollWorks data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that RollWorks has collected from you. We use the data that we provide to RollWorks to better customize your digital advertising experience and present you with more relevant ads. RollWorks Privacy Policy

      是否确定要简化联机体验?

      我们希望您能够从我们这里获得良好体验。对于上一屏幕中的类别,如果选择“是”,我们将收集并使用您的数据以自定义您的体验并为您构建更好的应用程序。您可以访问我们的“隐私声明”,根据需要更改您的设置。

      个性化您的体验,选择由您来做。

      我们重视隐私权。我们收集的数据可以帮助我们了解您对我们产品的使用情况、您可能感兴趣的信息以及我们可以在哪些方面做出改善以使您与 Autodesk 的沟通更为顺畅。

      我们是否可以收集并使用您的数据,从而为您打造个性化的体验?

      通过管理您在此站点的隐私设置来了解个性化体验的好处,或访问我们的隐私声明详细了解您的可用选项。