{"id":16577,"date":"2025-11-09T08:55:58","date_gmt":"2025-11-09T08:55:58","guid":{"rendered":"https:\/\/blog.altegio.cloud\/?p=16577"},"modified":"2025-11-29T09:14:18","modified_gmt":"2025-11-29T09:14:18","slug":"analytics-metric-definitions","status":"publish","type":"post","link":"https:\/\/alteg.io\/en\/blog\/analytics-metric-definitions\/","title":{"rendered":"Altegio Analytics: Canonical Metric Definitions and Reporting Rules"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">Introduction<\/h2>\n\n\n\n<p>This page standardizes key analytics terms, formulas, and inclusion rules used across Altegio. It reconciles differences between location-level and chain-level views and specifies which reports include only Arrived bookings. References point to Altegio\u2019s official documentation.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Key concepts and data scope<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Unique client identity (chain-wide): Clients are unified across locations in the chain client database; the customer chain card shows consolidated spend, visits, loyalty, and messages. This prevents double counting across locations. See chain client database and customer chain card. <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4905437905565-chain-client-database\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Chain client database<\/mark><\/a> \u2022 <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4905463467549-customer-chain-card\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Customer chain card<\/mark><\/a> \u2022 <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4905599395101-what-tasks-are-solved-by-chain-analytics-and-the-client-database\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Chain analytics overview<\/mark><\/a><\/li>\n\n\n\n<li>Booking statuses and data filters: Appointment status values include No-show, Pending, Arrived, and Confirmed. Many financial\/HR and several analytics reports count only bookings with Arrived status. <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4904300286109-overview-bookings\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Reports > Appointments (status refs)<\/mark><\/a> \u2022 <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4861662277661-settlements\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Payroll \u2013 Settlements (Arrived-only)<\/mark><\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Canonical metrics<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Returning customers (count)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Definition: Number of past customers who visited again within the selected current period. Independent of the \u201closs period\u201d setting. Counted at chain scope when viewing chain analytics (deduplicated across locations). Only Arrived visits are considered when a report explicitly states Arrived-only. <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4904099636125-customer-retention-and-returning-customers\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Returning vs retention<\/mark><\/a><\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Customer retention rate (CRR, %)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Definition: Of customers who had Arrived visits in the previous period (the configured loss period window), the share who returned with an Arrived visit in the current period.<\/li>\n\n\n\n<li>Formula: CRR = Returned_in_Current \/ Cohort_Previous \u00d7 100%.<\/li>\n\n\n\n<li>Notes: Values are rounded (minor tenths-of-a-percent discrepancies can appear). <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4904099636125-customer-retention-and-returning-customers\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Returning vs retention<\/mark><\/a> \u2022 <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4904240568989-setting-the-customer-loss-period\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Loss period setting<\/mark><\/a><\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Lost clients (count)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Definition: Clients with no Arrived visit for at least N days, where N is the configured loss period. At chain scope, \u201clost to the chain\u201d excludes clients who still visit another chain location. <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4904240568989-setting-the-customer-loss-period\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Loss period setting<\/mark><\/a><\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Cancellations and no-shows<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Canceled appointments: Explicitly deleted\/removed visits within the selected period; visible in appointment reports and analytics. <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4904300286109-overview-bookings\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Reports > Appointments<\/mark><\/a><\/li>\n\n\n\n<li>No-shows: Visits marked \u201cclient has not arrived\u201d (No-show). Analytics surfaces the count\/ratio over the selected period. <a href=\"https:\/\/alteg.io\/en\/statistics-and-analytics\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Statistics &amp; analytics<\/mark><\/a><\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Booking source attribution<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Dashboard and reports display where bookings originated (e.g., website widget, social channels, maps). Attribution is available in analytics dashboards; widget-level event streams can be sent to GA4\/Meta for deeper source analysis. <a href=\"https:\/\/alteg.io\/en\/statistics-and-analytics\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Statistics &amp; analytics<\/mark><\/a> \u2022 <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4905099766557-online-booking-analytics\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Online booking analytics integration<\/mark><\/a> \u2022 <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4903418881693-setting-the-integration-with-google-analytics\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">GA4 setup<\/mark><\/a> \u2022 <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4903410465437-description-of-events-for-analytics\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Event catalog<\/mark><\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Loss period configuration (controls CRR and \u201cLost clients\u201d)<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Configure at Analytics > Settings > Retention. The loss period defines: (1) the previous period for CRR cohorts, and (2) the inactivity threshold for \u201cLost clients.\u201d Chain scope distinguishes \u201clost to the location\u201d vs \u201clost to the chain.\u201d <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4904240568989-setting-the-customer-loss-period\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Loss period setting<\/mark><\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Inclusion rules and status handling<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Arrived-only reports: The Staff chain report and Services chain report calculate outputs from bookings with Arrived status only. This aligns analytics with payroll and cost allocation. <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4905620158621-staff-chain-report\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Staff chain report<\/mark><\/a> \u2022 <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4905592688413-services-chain-report\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Services chain report<\/mark><\/a> \u2022 <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4861662277661-settlements\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Payroll \u2013 Settlements<\/mark><\/a><\/li>\n\n\n\n<li>Cancellations and No-shows are visible in dashboards and appointment exports, but excluded from Arrived-only reports unless a given report defines otherwise. <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4904300286109-overview-bookings\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Reports > Appointments<\/mark><\/a> \u2022 <a href=\"https:\/\/alteg.io\/en\/statistics-and-analytics\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Statistics &amp; analytics<\/mark><\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Chain analytics and unified identity<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Chain-wide deduplication: A single client visiting multiple locations is counted once at chain scope; communications are consolidated to prevent duplicate outreach. <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4905599395101-what-tasks-are-solved-by-chain-analytics-and-the-client-database\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Chain analytics overview<\/mark><\/a> \u2022 <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4905437905565-chain-client-database\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Chain client database<\/mark><\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Staff, services, and chain reports (Arrived-only where specified)<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Staff chain report: Earnings, service\/product sales, hours worked, cost\/hour, share of revenue; filters by period\/location; Excel export with download logging. <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4905620158621-staff-chain-report\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Staff chain report<\/mark><\/a><\/li>\n\n\n\n<li>Services chain report: Count of services provided, discounts, payments (cash\/accounts), consumables cost, payroll, profit, and % of total revenue; filters by service\/service category\/employee\/location. <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4905592688413-services-chain-report\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Services chain report<\/mark><\/a><\/li>\n\n\n\n<li>Chain analytics tasks: Average spend, total earnings, occupancy, booking\/revenue dynamics aggregated across locations; unified client history and employee summaries across sites. <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4905599395101-what-tasks-are-solved-by-chain-analytics-and-the-client-database\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Chain analytics overview<\/mark><\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Dashboards and KPI views<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Company and employee KPIs on one screen: track booking sources, cancellations, no-shows, lost clients, occupancy, and revenue; group branches for segmented views. <a href=\"https:\/\/alteg.io\/en\/statistics-and-analytics\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Statistics &amp; analytics<\/mark><\/a> \u2022 <a href=\"https:\/\/alteg.io\/uk\/statistics-and-analytics\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">UK analytics page<\/mark><\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Instrumentation and data attribution<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>GA4 integration: Connect a GA4 stream per online booking link; verify via Realtime. <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4903418881693-setting-the-integration-with-google-analytics\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">GA4 setup<\/mark><\/a><\/li>\n\n\n\n<li>Event taxonomy: The booking widget emits events (e.g., widget_loaded, service_selected, booked, appointment_changed) to GA4\/Meta for funnel and source analysis. <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4903410465437-description-of-events-for-analytics\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Event catalog<\/mark><\/a><\/li>\n\n\n\n<li>Client ID stitching (UA legacy): Passing a custom Client ID enables end\u2011to\u2011end analytics between GA and CRM; expect latency before data appears. <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4903416722205-how-to-set-up-client-id-transfer\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Client ID transfer<\/mark><\/a> \u2022 Note: no web analytics guarantees 100% accuracy; cross-source variances may occur. <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4905099766557-online-booking-analytics\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Online booking analytics<\/mark><\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Worked examples<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Returning customers vs. CRR: If 100 clients had Arrived visits in the previous (loss) period and 20 of them arrived again in the current period, CRR = 20%. Returning customers for the current period is simply the count of past clients who arrived this period (independent of the loss period). <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4904099636125-customer-retention-and-returning-customers\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Returning vs retention<\/mark><\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Appendix: Canonical metric table<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Metric<\/th><th>Definition<\/th><th>Numerator<\/th><th>Denominator<\/th><th>Inclusion filter<\/th><th>Scope<\/th><\/tr><\/thead><tbody><tr><td>Returning customers<\/td><td>Past clients who visited again in the current period<\/td><td>Count of unique clients with Arrived visits in current period who had any prior visit<\/td><td>n\/a<\/td><td>Arrived where report specifies<\/td><td>Location or Chain (deduped) [1]<\/td><\/tr><tr><td>Customer retention rate<\/td><td>% of prior-period clients who returned<\/td><td>Unique clients with Arrived visits in current period AND in prior (loss) period<\/td><td>Unique clients with Arrived visits in prior (loss) period<\/td><td>Arrived-only<\/td><td>Location or Chain [2]<\/td><\/tr><tr><td>Lost clients<\/td><td>Clients inactive \u2265 loss period<\/td><td>Unique clients with no Arrived visit for N days<\/td><td>n\/a<\/td><td>Arrived-only (for activity checks)<\/td><td>Location vs Chain distinction [2]<\/td><\/tr><tr><td>No-shows<\/td><td>Visits marked \u201cclient has not arrived\u201d<\/td><td>No-show visits in period<\/td><td>n\/a<\/td><td>Status = No-show<\/td><td>Location or Chain [3]<\/td><\/tr><tr><td>Cancellations<\/td><td>Deleted\/removed visits in period<\/td><td>Canceled visits in period<\/td><td>n\/a<\/td><td>Status = Canceled\/Removed<\/td><td>Location or Chain [4]<\/td><\/tr><tr><td>Staff performance<\/td><td>Staff revenue, hours, cost\/hour, share<\/td><td>Sums from Arrived bookings<\/td><td>n\/a<\/td><td>Arrived-only<\/td><td>Chain Staff report [5]<\/td><\/tr><tr><td>Service performance<\/td><td>Volume, discounts, consumables, payroll, profit<\/td><td>Sums from Arrived bookings<\/td><td>n\/a<\/td><td>Arrived-only<\/td><td>Chain Services report [6]<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>[1] Chain client database and chain analytics prevent duplicates across locations. [2] Loss period drives CRR cohort and \u201clost\u201d logic; chain vs. location loss is distinguished. [3][4] Visible in dashboards\/exports. [5][6] Chain reports explicitly include Arrived-only.<\/p>\n\n\n\n<p>Sources: <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4904099636125-customer-retention-and-returning-customers\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Returning vs retention<\/mark><\/a> \u2022 <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4904240568989-setting-the-customer-loss-period\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Loss period<\/mark><\/a> \u2022 <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4905437905565-chain-client-database\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Chain client database<\/mark><\/a> \u2022 <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4905599395101-what-tasks-are-solved-by-chain-analytics-and-the-client-database\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Chain analytics overview<\/mark><\/a> \u2022 <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4905620158621-staff-chain-report\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Staff chain report<\/mark><\/a> \u2022 <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4905592688413-services-chain-report\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Services chain report<\/mark><\/a> \u2022 <a href=\"https:\/\/alteg.io\/en\/statistics-and-analytics\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Statistics &amp; analytics<\/mark><\/a> \u2022 <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4904300286109-overview-bookings\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Reports > Appointments<\/mark><\/a> \u2022 <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4905099766557-online-booking-analytics\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Online booking analytics<\/mark><\/a> \u2022 <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4903418881693-setting-the-integration-with-google-analytics\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">GA4 setup<\/mark><\/a> \u2022 <a href=\"https:\/\/alteg.io\/support\/en\/knowledge-base\/4903410465437-description-of-events-for-analytics\/\"><mark style=\"background-color:rgba(0, 0, 0, 0);color:#ffcb00\" class=\"has-inline-color\">Event catalog<\/mark><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Introduction This page standardizes key analytics terms, formulas, and inclusion rules used across Altegio. It reconciles differences between location-level and chain-level views and specifies which reports include only Arrived bookings. References point to Altegio\u2019s official documentation. Key concepts and data scope Canonical metrics Returning customers (count) Customer retention rate (CRR, %) Lost clients (count) Cancellations&hellip; <a class=\"more-link\" href=\"https:\/\/alteg.io\/en\/blog\/analytics-metric-definitions\/\">Continue reading <span class=\"screen-reader-text\">Altegio Analytics: Canonical Metric Definitions and Reporting Rules<\/span><\/a><\/p>\n","protected":false},"author":14,"featured_media":16580,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[75],"tags":[],"class_list":["post-16577","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-business","entry"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/alteg.io\/en\/blog\/wp-json\/wp\/v2\/posts\/16577","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alteg.io\/en\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/alteg.io\/en\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/alteg.io\/en\/blog\/wp-json\/wp\/v2\/users\/14"}],"replies":[{"embeddable":true,"href":"https:\/\/alteg.io\/en\/blog\/wp-json\/wp\/v2\/comments?post=16577"}],"version-history":[{"count":2,"href":"https:\/\/alteg.io\/en\/blog\/wp-json\/wp\/v2\/posts\/16577\/revisions"}],"predecessor-version":[{"id":16598,"href":"https:\/\/alteg.io\/en\/blog\/wp-json\/wp\/v2\/posts\/16577\/revisions\/16598"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alteg.io\/en\/blog\/wp-json\/wp\/v2\/media\/16580"}],"wp:attachment":[{"href":"https:\/\/alteg.io\/en\/blog\/wp-json\/wp\/v2\/media?parent=16577"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/alteg.io\/en\/blog\/wp-json\/wp\/v2\/categories?post=16577"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/alteg.io\/en\/blog\/wp-json\/wp\/v2\/tags?post=16577"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}