{"id":1408,"date":"2026-09-12T01:16:39","date_gmt":"2026-09-12T01:16:39","guid":{"rendered":"https:\/\/datalunchconsulting.com\/en\/tableau-versus-looker-studio\/"},"modified":"2026-09-12T01:16:39","modified_gmt":"2026-09-12T01:16:39","slug":"tableau-versus-looker-studio","status":"publish","type":"post","link":"https:\/\/datalunchconsulting.com\/fr\/tableau-versus-looker-studio\/","title":{"rendered":"Tableau versus Looker Studio for Your Team"},"content":{"rendered":"

A weekly executive report that takes three days to prepare is not a reporting process. It is a bottleneck. The right business intelligence platform can shorten that cycle, give teams access to trusted metrics, and make performance conversations more productive. In a Tableau versus Looker Studio decision, the best choice depends less on which tool has more features and more on your data environment, reporting audience, governance needs, and available skills.<\/p>\n

Tableau and Looker Studio both turn data into dashboards, but they were designed for different operating models. Tableau is a powerful analytics platform for teams that need deep visual analysis and controlled, scalable reporting. Looker Studio is a browser-based reporting tool that is especially useful for fast, accessible dashboards built around Google products and marketing data.<\/p>\n

Tableau versus Looker Studio: The Core Difference<\/h2>\n

Tableau is built for exploration. An analyst can connect to multiple data sources, investigate patterns through drag-and-drop analysis, create calculated fields, and develop interactive dashboards with a high degree of design control. It is commonly used for operational reporting, financial analysis, customer analytics, and executive dashboards where users may need to ask follow-up questions of the data.<\/p>\n

Looker Studio is built for distribution and accessibility. It lets users create and share reports in a familiar web-based workspace, with particularly convenient connections to Google Analytics, Google Ads, Google Sheets, BigQuery, and other Google services. A marketing manager who needs a campaign performance dashboard quickly can often create a useful first version in Looker Studio without involving a BI developer.<\/p>\n

The distinction matters because a dashboard is only valuable when people can trust, understand, and act on it. A tool that is quick to deploy but difficult to govern can create conflicting metrics. A tool that supports sophisticated analysis but requires specialized skills may be more capability than a small team needs.<\/p>\n

Where Tableau Creates More Value<\/h2>\n

Tableau is usually the stronger option when visual analysis is central to the work. Its desktop authoring environment gives analysts broad flexibility to shape data, build calculations, create parameters, and design highly interactive views. It supports a wide range of data connections and can work with files, databases, cloud platforms, and enterprise applications.<\/p>\n

This flexibility is valuable when a business question is not fully defined. For example, an operations team may begin by reviewing delivery performance by region, then filter by product category, carrier, customer segment, and time period to locate the cause of delays. Tableau is well suited to that investigative workflow.<\/p>\n

Tableau also tends to be a better fit for organizations that need more structured analytics governance. With Tableau Cloud or Tableau Server, administrators can manage user permissions, publish certified data sources, control refreshes, and give different groups access to appropriate content. These capabilities require planning, but they help organizations move beyond disconnected spreadsheets and individually maintained reports.<\/p>\n

There is a trade-off. Tableau has licensing costs and a steeper learning curve than Looker Studio. Building reliable dashboards requires sound data preparation<\/a>, calculation skills, and an understanding of visual design. Organizations should account for the time needed to train users<\/a>, define metric ownership, and establish publishing standards.<\/p>\n

Where Looker Studio Is the Better Fit<\/h2>\n

Looker Studio is a practical choice for teams that need fast, shareable reporting with minimal barriers to entry. Its web-based interface is approachable for business users, and reports can be shared with stakeholders without requiring everyone to install desktop software. For teams already working in the Google ecosystem, setup can be notably straightforward.<\/p>\n

It is particularly effective for recurring marketing and web analytics reports. A digital marketing team can combine website traffic, paid campaign results, search performance, and spreadsheet-based targets into a single dashboard for weekly review. The ability to create pages for different audiences can also make one report useful for executives, campaign managers, and channel specialists.<\/p>\n

Cost is another major consideration. Looker Studio has a free version, which makes it attractive for startups, nonprofits, small businesses, and individuals building their first reporting practice. Looker Studio Pro adds organizational management features for teams that need more administrative control.<\/p>\n

However, free access does not remove the need for good analytics discipline. Looker Studio can become difficult to manage when many report creators define metrics differently, use personal data connections, or depend on third-party connectors without clear ownership. Data blending and complex transformations can also become limiting compared with a dedicated analytics platform or a well-modeled data warehouse.<\/p>\n

Compare the Factors That Affect Adoption<\/h2>\n

A productive Tableau versus Looker Studio evaluation should start with real business use cases, not a generic feature checklist. Ask what decisions the dashboard must support, who will build it, who will consume it, and where the underlying data resides.<\/p>\n

Data sources and preparation<\/h3>\n

If your organization draws from multiple operational systems, cloud databases, CRM platforms, financial systems, and large datasets, Tableau generally provides greater analytical flexibility. It can connect to many sources and supports sophisticated calculations and data modeling approaches.<\/p>\n

Looker Studio works especially well when data is already available through Google connectors or prepared in platforms such as BigQuery. When data requires extensive cleaning, joining, or business-rule logic, prepare it upstream whenever possible. This approach improves performance and ensures that reports use consistent definitions regardless of the visualization tool.<\/p>\n

Dashboard design and analysis<\/h3>\n

Tableau offers more control over visual design, interactions, and exploratory analysis. It is the better choice when analysts need to answer changing questions, develop advanced visualizations, or create dashboards that guide users through complex performance drivers.<\/p>\n

Looker Studio provides the core charting and filtering most teams need for standard reporting. It is often sufficient when the objective is clear: show monthly revenue, campaign conversion rates, website traffic, budget pacing, or service volume. Its advantage is speed, not unlimited customization.<\/p>\n

Governance and security<\/h3>\n

For a department-level reporting need, sharing settings and controlled templates in Looker Studio may be enough. For enterprise reporting, governance becomes more significant. Leaders need confidence that revenue, customer counts, utilization, and other key metrics mean the same thing across every report.<\/p>\n

Tableau offers more mature options for governed publishing and permission management, particularly in larger deployments. That said, governance is not a software setting alone. Organizations need named metric owners, documented definitions, quality checks, and a process for approving changes.<\/p>\n

Skills and support<\/h3>\n

Looker Studio is easier for many first-time dashboard authors to learn. Its familiar interface can help business users move quickly from spreadsheet reporting to interactive reporting. Tableau requires more deliberate training, but the investment can produce stronger analytics capabilities for analysts and data-focused teams.<\/p>\n

The right approach may be to develop different skill paths. Business users can learn how to interpret dashboards, ask better questions, and maintain approved reports. Analysts can build deeper skills in data preparation, calculations, visual storytelling, and governance. This division creates useful self-service without leaving critical metrics unmanaged.<\/p>\n

Do Not Confuse Looker Studio With Looker<\/h2>\n

Looker Studio and Looker are separate Google products. Looker Studio is primarily a reporting and dashboarding tool. Looker is a broader business intelligence platform centered on governed data modeling and semantic layers, often used in more mature cloud data environments.<\/p>\n

This distinction can affect technology planning. An organization comparing Tableau with Looker Studio is evaluating a different set of capabilities than an organization comparing Tableau with Looker. Confirm the exact product, data architecture, and governance requirements before committing to a platform.<\/p>\n

A Practical Choice for Common Scenarios<\/h2>\n

Choose Tableau when your team needs advanced analysis, highly customized dashboards, broad data connectivity, or a scalable governance model. It is a strong long-term investment for organizations where analytics informs operational, financial, customer, or strategic decisions across departments.<\/p>\n

Choose Looker Studio when you need accessible, cost-conscious dashboards, especially for Google-based marketing and web reporting. It is a sensible option for teams that need to share standardized performance reports quickly and do not require extensive analytical complexity.<\/p>\n

Many organizations can use both. Looker Studio may serve marketing teams that need rapid campaign reporting, while Tableau supports enterprise reporting or deeper analysis across multiple systems. The key is to prevent duplicated metrics and unclear ownership. Define which tool serves which audience, establish a trusted source for core data, and train teams to use dashboards as decision tools rather than static presentation materials.<\/p>\n

A dashboard platform should make the next business conversation more specific: What changed, why did it change, and what action should follow? Start with that standard, then select the tool and training approach<\/a> that helps your people meet it consistently.<\/p>","protected":false},"excerpt":{"rendered":"

Compare Tableau versus Looker Studio for data connections, governance, cost, and dashboard design, then choose the platform that fits your team’s goals.<\/p>","protected":false},"author":1,"featured_media":1409,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-1408","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"yoast_head":"\nTableau versus Looker Studio for Your Team - DataLunch Consulting<\/title>\n<meta name=\"description\" content=\"Compare Tableau versus Looker Studio for data connections, governance, cost, and dashboard design, then choose the platform that fits your team's goals.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/datalunchconsulting.com\/fr\/tableau-versus-looker-studio\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Tableau versus Looker Studio for Your Team - DataLunch Consulting\" \/>\n<meta property=\"og:description\" content=\"Compare Tableau versus Looker Studio for data connections, governance, cost, and dashboard design, then choose the platform that fits your team's goals.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/datalunchconsulting.com\/fr\/tableau-versus-looker-studio\/\" \/>\n<meta property=\"og:site_name\" content=\"DataLunch Consulting\" \/>\n<meta property=\"article:published_time\" content=\"2026-09-12T01:16:39+00:00\" \/>\n<meta name=\"author\" content=\"admin\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u00c9crit par\" \/>\n\t<meta name=\"twitter:data1\" content=\"admin\" \/>\n\t<meta name=\"twitter:label2\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/datalunchconsulting.com\\\/en\\\/tableau-versus-looker-studio\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/datalunchconsulting.com\\\/en\\\/tableau-versus-looker-studio\\\/\"},\"author\":{\"name\":\"admin\",\"@id\":\"https:\\\/\\\/datalunchconsulting.com\\\/#\\\/schema\\\/person\\\/1914fb8a5a2d7d21553ac7797925cd1c\"},\"headline\":\"Tableau versus Looker Studio for Your Team\",\"datePublished\":\"2026-09-12T01:16:39+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/datalunchconsulting.com\\\/en\\\/tableau-versus-looker-studio\\\/\"},\"wordCount\":1411,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/datalunchconsulting.com\\\/en\\\/tableau-versus-looker-studio\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/datalunchconsulting.com\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/tableau-versus-looker-studio-for-your-team-featured.webp\",\"articleSection\":[\"Uncategorized\"],\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/datalunchconsulting.com\\\/en\\\/tableau-versus-looker-studio\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/datalunchconsulting.com\\\/en\\\/tableau-versus-looker-studio\\\/\",\"url\":\"https:\\\/\\\/datalunchconsulting.com\\\/en\\\/tableau-versus-looker-studio\\\/\",\"name\":\"Tableau versus Looker Studio for Your Team - DataLunch Consulting\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/datalunchconsulting.com\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/datalunchconsulting.com\\\/en\\\/tableau-versus-looker-studio\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/datalunchconsulting.com\\\/en\\\/tableau-versus-looker-studio\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/datalunchconsulting.com\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/tableau-versus-looker-studio-for-your-team-featured.webp\",\"datePublished\":\"2026-09-12T01:16:39+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/datalunchconsulting.com\\\/#\\\/schema\\\/person\\\/1914fb8a5a2d7d21553ac7797925cd1c\"},\"description\":\"Compare Tableau versus Looker Studio for data connections, governance, cost, and dashboard design, then choose the platform that fits your team's goals.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/datalunchconsulting.com\\\/en\\\/tableau-versus-looker-studio\\\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/datalunchconsulting.com\\\/en\\\/tableau-versus-looker-studio\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\\\/\\\/datalunchconsulting.com\\\/en\\\/tableau-versus-looker-studio\\\/#primaryimage\",\"url\":\"https:\\\/\\\/datalunchconsulting.com\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/tableau-versus-looker-studio-for-your-team-featured.webp\",\"contentUrl\":\"https:\\\/\\\/datalunchconsulting.com\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/tableau-versus-looker-studio-for-your-team-featured.webp\",\"width\":1536,\"height\":1024,\"caption\":\"Tableau versus Looker Studio for Your Team\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/datalunchconsulting.com\\\/en\\\/tableau-versus-looker-studio\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/datalunchconsulting.com\\\/en\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Tableau versus Looker Studio for Your Team\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/datalunchconsulting.com\\\/#website\",\"url\":\"https:\\\/\\\/datalunchconsulting.com\\\/\",\"name\":\"DataLunch Consulting\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/datalunchconsulting.com\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/datalunchconsulting.com\\\/#\\\/schema\\\/person\\\/1914fb8a5a2d7d21553ac7797925cd1c\",\"name\":\"admin\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/81aa9fadd52f149eb5f166625519254c613eece76139d99186ed7621a64ec9da?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/81aa9fadd52f149eb5f166625519254c613eece76139d99186ed7621a64ec9da?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/81aa9fadd52f149eb5f166625519254c613eece76139d99186ed7621a64ec9da?s=96&d=mm&r=g\",\"caption\":\"admin\"},\"sameAs\":[\"https:\\\/\\\/datalunchconsulting.com\"],\"url\":\"https:\\\/\\\/datalunchconsulting.com\\\/fr\\\/author\\\/admin\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Tableau versus Looker Studio for Your Team - DataLunch Consulting","description":"Compare Tableau versus Looker Studio for data connections, governance, cost, and dashboard design, then choose the platform that fits your team's goals.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/datalunchconsulting.com\/fr\/tableau-versus-looker-studio\/","og_locale":"fr_FR","og_type":"article","og_title":"Tableau versus Looker Studio for Your Team - DataLunch Consulting","og_description":"Compare Tableau versus Looker Studio for data connections, governance, cost, and dashboard design, then choose the platform that fits your team's goals.","og_url":"https:\/\/datalunchconsulting.com\/fr\/tableau-versus-looker-studio\/","og_site_name":"DataLunch Consulting","article_published_time":"2026-09-12T01:16:39+00:00","author":"admin","twitter_card":"summary_large_image","twitter_misc":{"\u00c9crit par":"admin","Dur\u00e9e de lecture estim\u00e9e":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/datalunchconsulting.com\/en\/tableau-versus-looker-studio\/#article","isPartOf":{"@id":"https:\/\/datalunchconsulting.com\/en\/tableau-versus-looker-studio\/"},"author":{"name":"admin","@id":"https:\/\/datalunchconsulting.com\/#\/schema\/person\/1914fb8a5a2d7d21553ac7797925cd1c"},"headline":"Tableau versus Looker Studio for Your Team","datePublished":"2026-09-12T01:16:39+00:00","mainEntityOfPage":{"@id":"https:\/\/datalunchconsulting.com\/en\/tableau-versus-looker-studio\/"},"wordCount":1411,"commentCount":0,"image":{"@id":"https:\/\/datalunchconsulting.com\/en\/tableau-versus-looker-studio\/#primaryimage"},"thumbnailUrl":"https:\/\/datalunchconsulting.com\/wp-content\/uploads\/2026\/09\/tableau-versus-looker-studio-for-your-team-featured.webp","articleSection":["Uncategorized"],"inLanguage":"fr-FR","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/datalunchconsulting.com\/en\/tableau-versus-looker-studio\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/datalunchconsulting.com\/en\/tableau-versus-looker-studio\/","url":"https:\/\/datalunchconsulting.com\/en\/tableau-versus-looker-studio\/","name":"Tableau versus Looker Studio for Your Team - DataLunch Consulting","isPartOf":{"@id":"https:\/\/datalunchconsulting.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/datalunchconsulting.com\/en\/tableau-versus-looker-studio\/#primaryimage"},"image":{"@id":"https:\/\/datalunchconsulting.com\/en\/tableau-versus-looker-studio\/#primaryimage"},"thumbnailUrl":"https:\/\/datalunchconsulting.com\/wp-content\/uploads\/2026\/09\/tableau-versus-looker-studio-for-your-team-featured.webp","datePublished":"2026-09-12T01:16:39+00:00","author":{"@id":"https:\/\/datalunchconsulting.com\/#\/schema\/person\/1914fb8a5a2d7d21553ac7797925cd1c"},"description":"Compare Tableau versus Looker Studio for data connections, governance, cost, and dashboard design, then choose the platform that fits your team's goals.","breadcrumb":{"@id":"https:\/\/datalunchconsulting.com\/en\/tableau-versus-looker-studio\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/datalunchconsulting.com\/en\/tableau-versus-looker-studio\/"]}]},{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/datalunchconsulting.com\/en\/tableau-versus-looker-studio\/#primaryimage","url":"https:\/\/datalunchconsulting.com\/wp-content\/uploads\/2026\/09\/tableau-versus-looker-studio-for-your-team-featured.webp","contentUrl":"https:\/\/datalunchconsulting.com\/wp-content\/uploads\/2026\/09\/tableau-versus-looker-studio-for-your-team-featured.webp","width":1536,"height":1024,"caption":"Tableau versus Looker Studio for Your Team"},{"@type":"BreadcrumbList","@id":"https:\/\/datalunchconsulting.com\/en\/tableau-versus-looker-studio\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/datalunchconsulting.com\/en\/"},{"@type":"ListItem","position":2,"name":"Tableau versus Looker Studio for Your Team"}]},{"@type":"WebSite","@id":"https:\/\/datalunchconsulting.com\/#website","url":"https:\/\/datalunchconsulting.com\/","name":"DataLunch Consulting","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/datalunchconsulting.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Person","@id":"https:\/\/datalunchconsulting.com\/#\/schema\/person\/1914fb8a5a2d7d21553ac7797925cd1c","name":"admin","image":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/secure.gravatar.com\/avatar\/81aa9fadd52f149eb5f166625519254c613eece76139d99186ed7621a64ec9da?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/81aa9fadd52f149eb5f166625519254c613eece76139d99186ed7621a64ec9da?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/81aa9fadd52f149eb5f166625519254c613eece76139d99186ed7621a64ec9da?s=96&d=mm&r=g","caption":"admin"},"sameAs":["https:\/\/datalunchconsulting.com"],"url":"https:\/\/datalunchconsulting.com\/fr\/author\/admin\/"}]}},"_links":{"self":[{"href":"https:\/\/datalunchconsulting.com\/fr\/wp-json\/wp\/v2\/posts\/1408","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/datalunchconsulting.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/datalunchconsulting.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/datalunchconsulting.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/datalunchconsulting.com\/fr\/wp-json\/wp\/v2\/comments?post=1408"}],"version-history":[{"count":0,"href":"https:\/\/datalunchconsulting.com\/fr\/wp-json\/wp\/v2\/posts\/1408\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/datalunchconsulting.com\/fr\/wp-json\/wp\/v2\/media\/1409"}],"wp:attachment":[{"href":"https:\/\/datalunchconsulting.com\/fr\/wp-json\/wp\/v2\/media?parent=1408"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/datalunchconsulting.com\/fr\/wp-json\/wp\/v2\/categories?post=1408"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/datalunchconsulting.com\/fr\/wp-json\/wp\/v2\/tags?post=1408"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}