[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-04。"],[],[],null,["# A typical Looker Studio workflow\n\nThis page presents a typical way you might work with Looker Studio. This scenario covers 6 steps:\n\n- **Create** a report\n- **Connect** to your data\n- **Visualize** the data\n- **Transform** the data\n- **Share** your insights\n- **Update** and refine the report\n\nScenario\n--------\n\nAqsa is a data analyst for a travel company. She wants to explore and visualize data on flight arrival and departure delays in order to see if there are valuable insights her company can provide to their customers to improve their travel experience. The data is stored in BigQuery.\n\nCreate\n------\n\nAqsa signs into Looker Studio, then clicks **Create \\\u003e Report** . The Looker Studio report editor opens and the **Add data** panel appears.\n\nConnect\n-------\n\nThe **Add data** panel lets Aqsa create a new [data source](/looker/docs/studio/data-source) or select an existing one. She doesn't yet have a data source for the flight data she wants to visualize, so she clicks the BigQuery [connector](/looker/docs/studio/connector) to create a new data source.\n\nAqsa enters the information needed to connect to the BigQuery table containing the flight data, and then adds the new data source to her report.\n\nThe **Add data** panel closes and a table appears on the editor canvas, with the airline carrier field and the record count for each unique carrier.\n\nVisualize\n---------\n\nAqsa adds more fields to the table by dragging them from the properties panel to the table. She adds an **Arrival Delay** metric, which contains the number of minutes each flight was delayed past its scheduled arrival time.\n\nAqsa knows that tables are great for seeing the details in data, but she wants to get a higher level overview, so she adds a horizontal bar chart and a pie chart to the report. Now she can immediately see which airlines had the most delays of their arriving flights and their relationship to the other airlines' performances.\n\nTransform\n---------\n\nAqsa notices that the arrival delay field is summing the data but it should instead be averaging it. She could fix this by changing the aggregation for the field as it appears in each chart, but it's more efficient to edit the data source.\n\nWhen you want to modify a field that appears in a report, you have the following options:\n\n- **Modify the field In a chart**. When you do this, you're just changing that specific instance of the field. The change only applies to the field in that chart. Other charts that use the field will have the field's default configuration, as set in the data source.\n\n- **Modify the field In the data source**. When you do this, the change will appear the next time you use that field. For example, new charts you create will use the changed field, as will existing chart to which you add another instance of the field. Components that used the field before you made the change won't be affected.\n\nTo edit the data source, at the top of the properties panel, Aqsa clicks the pencil next to the data source name. She locates the `ArrDelay` field and changes its **Default aggregation** to **Average** . Aqsa clicks **DONE** to save her change and return to the report editor.\n\nNow when anyone with access to edit the report uses this field, it will have the desired aggregation by default.\n\nShare and collaborate\n---------------------\n\nAqsa asks her colleague Lauren to help apply their design skills to the report. Aqsa shares the report with Lauren's email address, giving them **Can edit** permission. Lauren sets to work, adding text and images, and crafting the report appearance to match their company's style guidelines. Lauren suggests they add a page that provides more context by embedding the current marketing plan, which is stored as a Google Doc. Together, Aqsa and Lauren create an attractive, compelling report that highlights the insights they've found in the flight data.\n\nWhen the report is finished, Asqa shares it with the senior management team's group email address, giving them **Can view** permission. Because the data source has [Owner's data credentials](/looker/docs/studio/data-credentials), the management team can see the data in the report, even if they don't have direct access to the underlying BigQuery dataset.\n\nUpdate and refine\n-----------------\n\nThe company CEO loves the report, and asks Aqsa if she can add their marketing analytics data to get even deeper insights. Aqsa edits the report and adds data sources for their Google Ads and Google Analytics accounts. She uses community connectors to access data from Facebook and other social media channels as well. Aqsa uses some of Looker Studio's more advanced features, such as [data blending](/looker/docs/studio/how-blends-work-in-looker-studio) and [calculated fields](/looker/docs/studio/about-calculated-fields), to reveal opportunities and challenges she'd never have discovered without being able to see all the available data in one place."]]
Aqsa 是一家旅游公司的一名数据分析师。她希望探索和可视化航班到达和出发延误数据，以便确定公司是否可以为客户提供有价值的数据洞见，从而改善他们的旅行体验。数据存储在 BigQuery 中。
Aqsa 注意到，到达延迟时间字段会对数据进行求和，但实际上应该对数据求平均值。她可以通过更改每个图表中显示的字段的汇总方式来解决此问题，但修改数据源更为高效。
Aqsa 请同事 Lauren 帮助将其设计技能运用到报告中。Aqsa 与 Lauren 的电子邮件地址共享报告，并向其授予可以修改权限。Lauren 开始工作，添加文字和图片，并根据公司样式指南调整报告的外观。Lauren 建议他们添加一个页面，通过嵌入存储为 Google 文档的当前营销方案来提供更多背景信息。Aqsa 和 Lauren 共同制作了一个引人入胜的报告，突出显示了他们从广告系列数据中发现的数据洞见。
