{"id":20116,"date":"2024-09-16T14:30:00","date_gmt":"2024-09-16T12:30:00","guid":{"rendered":"https:\/\/www.dase-analytics.com\/blog\/?p=20116\/"},"modified":"2024-09-17T13:01:11","modified_gmt":"2024-09-17T11:01:11","slug":"ako-sa-zbavit-not-set-hodnot-v-google-analytics-4","status":"publish","type":"post","link":"https:\/\/www.dase-analytics.com\/blog\/sk\/ako-sa-zbavit-not-set-hodnot-v-google-analytics-4\/","title":{"rendered":"Ako sa zbavi\u0165 (not set) hodn\u00f4t v Google Analytics 4?"},"content":{"rendered":"

Asi ka\u017ed\u00fd sa u\u017e stretol v GA4 reportoch s nevy\u017eiadanou hodnotou (not set). (not set) sa zobrazuje v reportoch GA4 v momente, ke\u010f syst\u00e9m nem\u00e1 o ur\u010ditej dimenzii dan\u00e9 inform\u00e1cie.<\/strong><\/p>\n

Tieto hodnoty n\u00e1s vedia dobre potr\u00e1pi\u0165, preto\u017ee d\u00e1ta s\u00edce m\u00e1me, ale nie s\u00fa jasn\u00e9 a nevieme s nimi pri analyzovan\u00ed webu pracova\u0165.\u00a0<\/strong><\/p>\n

T\u00e9me ch\u00fdbaj\u00facich d\u00e1t sme sa venovali aj v<\/span> blogu o unassigned n\u00e1v\u0161tevnosti<\/span><\/a>.\u00a0<\/span><\/p>\n

V tomto \u010dl\u00e1nku v\u00e1m pribl\u00ed\u017eime, kedy vieme hodnotu (not set) zadefinova\u0165<\/strong>, kedy vieme jej v\u00fdskyt zn\u00ed\u017ei\u0165<\/strong> a kedy ju budeme musie\u0165 v reportoch len akceptova\u0165<\/strong>.<\/span><\/p>\n

Ke\u010f\u017ee sa s hodnotou (not set) stret\u00e1vame vo viacer\u00fdch reportoch, prejdeme si z\u00e1kladn\u00e9 body, kde m\u00f4\u017ee by\u0165 probl\u00e9m a ich rie\u0161enia.<\/span><\/p>\n

1. Vyhodnocovanie d\u00e1t po 48 hodin\u00e1ch<\/strong><\/h2>\n

Prv\u00fdm tipom, ktor\u00fd nevy\u017eaduje \u017eiadne zmeny v meraniach, je po\u010dka\u0165 aspo\u0148 48 hod\u00edn<\/strong> na spracovanie v\u0161etk\u00fdch d\u00e1t.<\/span><\/p>\n

Ak si v GA4 reporte vyhodnocujete d\u00e1ta, kde je zahrnut\u00e9 obdobie menej ako 48 hod\u00edn, m\u00f4\u017eu sa v\u00e1m v reporte objavi\u0165 (not set) d\u00e1ta, ktor\u00e9 syst\u00e9m po p\u00e1r hodin\u00e1ch prirad\u00ed k spr\u00e1vnej hodnote.<\/span><\/p>\n

2. Manu\u00e1lne UTM tagovanie rekl\u00e1m<\/strong><\/h2>\n

Nespr\u00e1vne otagovan\u00e9 reklamy s\u00fa naj\u010dastej\u0161\u00edm d\u00f4vodom<\/strong>, pre\u010do sa v reportoch nach\u00e1dza (not set). Tejto t\u00e9me sme sa venovali aj v <\/span>\u010dl\u00e1nku o unassigned n\u00e1v\u0161tevnosti<\/span><\/a>.<\/span><\/p>\n

3. Measurement protocol<\/strong><\/h2>\n

Measurement protocol je druh\u00fd naj\u010dastej\u0161\u00ed d\u00f4vod<\/strong>, pre\u010do m\u00e1te v d\u00e1tach (not set).<\/span><\/p>\n

Measurement protokol pom\u00e1ha posiela\u0165 d\u00e1ta z v\u00e1\u0161ho servera (napr. CRM) do GA4. Probl\u00e9m vznik\u00e1, ke\u010f Measurement protocol nezded\u00ed niektor\u00e9 \u00fadaje<\/strong>, ktor\u00e9 u\u017e v k\u00f3de natrackovan\u00e9 s\u00fa a tieto nezdeden\u00e9 parametre ozna\u010d\u00ed (not set).<\/span><\/p>\n

Viacer\u00e9 pr\u00edpady, ktor\u00e9 spom\u00edname ni\u017e\u0161ie, maj\u00fa p\u00f4vod v MP a rie\u0161enie n\u00e1jdete pri ka\u017edom z nich.<\/strong><\/p>\n

4. Vstupn\u00e9 str\u00e1nky s\u00fa (not set)<\/strong><\/h2>\n

S t\u00fdmto probl\u00e9mom sme sa stret\u00e1vali u\u017e pri UA, kedy (not set) pri Landing page znamenalo ch\u00fdbaj\u00faci <\/span>page_view <\/b>event, s parametrom <\/span>page_location<\/span><\/i>.<\/span><\/p>\n

Pr\u00edkladom je situ\u00e1cia, kedy niekto od\u00edde od po\u010d\u00edta\u010da a nech\u00e1 si otvoren\u00e9 okno so str\u00e1nkou. Po 30 min\u00fatach jeho rel\u00e1cia vypr\u0161\u00ed. Pou\u017e\u00edvate\u013e sa vr\u00e1ti k po\u010d\u00edta\u010du, kedy na str\u00e1nke vykon\u00e1 akciu, ktor\u00e1 u\u017e ale pri novej rel\u00e1cii prebehne bez page_view<\/strong> a n\u00e1m sa v reporte zobraz\u00ed landing page ako (not set).<\/span><\/p>\n

Mo\u017en\u00fdm rie\u0161en\u00edm je v tomto pr\u00edpade zmena trvania rel\u00e1cie z 30 min na dlh\u0161ie obdobie<\/strong> (maximum je 7h 55min).<\/span><\/p>\n

Zmenu nastav\u00edte tu:\u00a0<\/strong><\/span><\/p>\n

GA4 –<\/span>> Admin -> Data Streams -> Select web data stream -> Configure tag settings -> Show all -> Adjust session timeout<\/span><\/i><\/p>\n

Nezab\u00fadajte<\/strong>, \u017ee toto rie\u0161enie v\u00e1m ovplyvn\u00ed reportovanie aj in\u00fdch d\u00e1t. S nav\u00fd\u0161en\u00edm d\u013a\u017eky rel\u00e1cie poklesne celkov\u00fd po\u010det rel\u00e1cii a priemern\u00e1 doba rel\u00e1cie sa nav\u00fd\u0161i.<\/span><\/p>\n

5. Zdroj \/ m\u00e9dium je (not set)<\/strong><\/h2>\n

Nezaraden\u00e9 (not set) hodnoty v reporte Akviz\u00edcia n\u00e1v\u0161tevnosti<\/strong> sme si vysvetlili v \u010dl\u00e1nku o Unassigned n\u00e1v\u0161tevnosti.<\/span><\/p>\n

Ak je zdroj \/ m\u00e9dium rel\u00e1cie (not set), m\u00f4\u017ee to by\u0165 sp\u00f4soben\u00e9 Measurement protokolom, ch\u00fdbaj\u00facim session_start<\/strong> eventom, pou\u017e\u00edvan\u00edm audience triggers<\/strong> (publik\u00e1 vytvoren\u00e9 na z\u00e1klade sp\u00fa\u0161\u0165a\u010dov), chybn\u00fdmi UTM parametrami, odpa\u013eovan\u00edm tagov pred konfigura\u010dn\u00fdm tagom, alebo nespr\u00e1vnou implement\u00e1ciou server-side GTM.<\/span><\/p>\n

Rie\u0161enia ako to opravi\u0165 n\u00e1jdete <\/span>v tomto \u010dl\u00e1nku<\/span><\/a>.\u00a0<\/span><\/p>\n

\"Kompletn\u00fd<\/a><\/p>\n

Od j\u00fana tohto roka za\u010dali hodnoty (not set) st\u00fapa\u0165 pri zdrojoch n\u00e1v\u0161tevnosti aj z d\u00f4vodu zmien s Consent modom.<\/strong><\/span><\/p>\n

V r\u00e1mci implement\u00e1cie Consent modu si treba da\u0165 pozor na tieto 3 veci:<\/strong><\/p>\n

    \n
  1. Pokia\u013e pou\u017e\u00edvate ako trigger Consent default s updanutn\u00fdmi preferenciami u\u017e\u00edvate\u013ea, m\u00f4\u017ee v\u00e1m to rozbi\u0165 d\u00e1ta. Uistite sa, \u017ee v\u017edy pou\u017e\u00edvate na odpa\u013eovanie tagov event Consent update.<\/span><\/span><\/li>\n
  2. \u010eal\u0161\u00edm d\u00f4vodom m\u00f4\u017ee by\u0165 nastavenie consentu cez CMS plugin. Ak m\u00e1te nastaven\u00fd consent mode cez plugin a z\u00e1rove\u0148 posielate Consent default cez GTM, va\u0161e rel\u00e1cie m\u00f4\u017eu ma\u0165 nepriraden\u00fd zdroj n\u00e1v\u0161tevnosti.<\/span><\/span><\/li>\n
  3. Niektor\u00e9 implement\u00e1cie m\u00f4\u017eu po udelen\u00ed s\u00fahlasu znovu na\u010d\u00edta\u0165 str\u00e1nku, \u010d\u00edm sa rel\u00e1cie nezaradia pod pr\u00edslu\u0161n\u00fd zdroj. Probl\u00e9m m\u00f4\u017ee nasta\u0165, ke\u010f sa funkcia Consent default zavol\u00e1 viackr\u00e1t s r\u00f4znymi hodnotami consentu.<\/li>\n<\/ol>\n

    6. Kampa\u0148 je (not set)<\/strong><\/h2>\n

    Vy\u0161\u0161ie spomenut\u00e9 tipy pre zdroj \/ m\u00e9dium<\/strong> platia aj pre dimenzie t\u00fdkaj\u00face sa kampan\u00ed.<\/span><\/p>\n

    UTM parametre <\/span>utm_source<\/strong> <\/span><\/i>a <\/span>utm_medium<\/i><\/strong> s\u00fa pre fungovanie reportu zdroja n\u00e1v\u0161tevnosti nevyhnutn\u00e9. Pokia\u013e v UTM zna\u010dkovan\u00ed nepou\u017e\u00edvate <\/span>utm_campaign<\/strong>,<\/span><\/i> dimenzie t\u00fdkaj\u00face sa kampan\u00ed ako First user campaign<\/strong> a Session campaign<\/strong> bud\u00fa obsahova\u0165 (not set).\u00a0<\/span><\/p>\n

    7. Google Ads je (not set)<\/strong><\/h2>\n

    Ak sa v\u00e1m zobrazuje (not set) pri dimenzi\u00e1ch t\u00fdkaj\u00facich sa Google ads,<\/strong> d\u00f4vodov m\u00f4\u017ee by\u0165 op\u00e4\u0165 viacero.\u00a0<\/span><\/p>\n

      \n
    1. Uistite sa, \u017ee m\u00e1te prepojen\u00fd Google ads \u00fa\u010det s GA4.<\/span><\/span><\/li>\n
    2. Skontrolujte si, \u010di m\u00e1te zapnut\u00fd auto-tagging<\/strong>. Pokia\u013e nechcete zna\u010dkova\u0165 URL automaticky, m\u00f4\u017eete pou\u017e\u00edva\u0165 manu\u00e1lne zna\u010dkovanie URL adries. Pri manu\u00e1lnom zna\u010dkovan\u00ed je v\u0161ak vy\u0161\u0161ia \u0161anca na chybn\u00e9 ozna\u010denia a n\u00e1rast (not set) hodn\u00f4t. N\u00e1vod na spr\u00e1vne zna\u010dkovanie som vyp\u00edsala <\/span>v minulom \u010dl\u00e1nku.\u00a0<\/span><\/a><\/li>\n
    3. Pokia\u013e m\u00e1te ku GA4 napojen\u00e9 viacer\u00e9 \u00fa\u010dty Google ads, skontrolujte si, \u010di niektor\u00e9 z nich nemaj\u00fa auto-tagging vypnut\u00fd.\u00a0<\/span><\/li>\n<\/ol>\n

      8. Page location je (not set)<\/strong><\/h2>\n

      Pokia\u013e m\u00e1 v\u00e1\u0161 web URL adresy dlh\u0161ie ako 1000 znakov<\/strong> (vr\u00e1tane https a query parametrov), <\/span>page_location <\/i><\/strong>nebude odtrackovan\u00e1<\/strong>. Rie\u0161en\u00edm v tomto pr\u00edpade je prep\u00edsanie parametra <\/span>page_location <\/span><\/i>v GTM, cez vyl\u00fa\u010denie nechcen\u00fdch URL parametrov.\u00a0<\/span><\/p>\n

      9. Page title je (not set)<\/strong><\/h2>\n

      Pri ch\u00fdbaj\u00facom Page title s\u00fa 2 pr\u00ed\u010diny, \u010do to m\u00f4\u017eu sp\u00f4sobova\u0165:<\/strong><\/span><\/p>\n

      1. Chybaj\u00faci nadpis „title“ <\/strong>v html k\u00f3de str\u00e1nky.<\/strong> Aby ste zistili, ktor\u00fdm konkr\u00e9tnym str\u00e1nkam ch\u00fdba Page title, cho\u010fte do<\/span> R<\/span><\/i>eports > Engagement > Pages and screens<\/span><\/i> Tu si skontrolujte v prvej dimenzii <\/span>Page title and screen class<\/span><\/i> a v druhej dimenzii<\/span> Page Path and Screen class. <\/span><\/i>Potom kontaktujte developera str\u00e1nky, aby nadpisy doplnil.\u00a0<\/span><\/p>\n

      \"Kompletn\u00fd<\/a><\/p>\n

      2. GA4 k\u00f3d sa na\u010d\u00edta sk\u00f4r, ako „<\/strong>title“.<\/strong> Pokia\u013e sa title\u00a0nach\u00e1dza v k\u00f3de ni\u017e\u0161ie, ako trackovac\u00ed k\u00f3d GA4, GA4 nadpis z k\u00f3du nevy\u010d\u00edta a prirad\u00ed k nemu hodnotu (not set).<\/span><\/p>\n

      10. Content group je (not set)<\/strong><\/h2>\n

      Aj pri neozna\u010denej content groupe m\u00f4\u017ee by\u0165 d\u00f4vodov viacero:<\/span><\/p>\n

      1. Parameter content_group<\/i><\/strong> sa do GA4 neodosiela.<\/strong> Tento parameter je potrebn\u00e9 zadefinova\u0165 v GTM.<\/span><\/p>\n

       <\/p>\n

      2. Parameter content_group<\/i><\/strong> odosielate chybne.<\/strong> N\u00e1zov parametru je case-sensitive a pokia\u013e ho pomenujete inak, napr. Content_group, content_category, jeho hodnota sa v GA4 neprirad\u00ed.<\/span><\/p>\n

      \"Kompletn\u00fd<\/a><\/p>\n

      3.<\/strong> Ak spust\u00edte konfigura\u010dn\u00fd tag GA4 pred odoslan\u00edm content_group do dataLayera, odo\u0161lete do GA4 nedefinovan\u00fa hodnotu.<\/span><\/p>\n

      11. Jazyk je (not set)<\/strong><\/h2>\n

      GA4 dop\u013a\u0148a dimenziu jazyk na z\u00e1klade nastaven\u00ed v prehliada\u010di. Pre ch\u00fdbaj\u00face hodnoty m\u00f4\u017eu by\u0165 nasledovn\u00e9 d\u00f4vody:<\/span><\/p>\n

        \n
      1. Ka\u017ed\u00fd event odoslan\u00fd cez Measurement Protocol mus\u00ed obsahova\u0165 parameter <\/span>language<\/span><\/i>.<\/span><\/li>\n
      2. U\u017e\u00edvate\u013e m\u00e1 v prehliada\u010di nastavenia, ktor\u00e9 skr\u00fdvaj\u00fa\/modifikuj\u00fa parameter <\/span>language, <\/span><\/i>a GA4 ich nevie pre\u010d\u00edta\u0165.<\/span><\/li>\n
      3. Pou\u017e\u00edvate server-side GTM a z requestu sa neodo\u0161le parameter <\/span>ul<\/span><\/i> (User Language).\u00a0<\/span><\/li>\n<\/ol>\n

        12. Krajina je (not set)<\/strong><\/h2>\n

        Tento bod sa t\u00fdka v\u0161etk\u00fdch geografick\u00fdch dimenzi\u00ed.<\/strong> D\u00f4vody pre (not set) hodnoty m\u00f4\u017eu by\u0165:<\/span><\/p>\n

          \n
        1. Udalos\u0165 sa posiela cez Measurement Protocol.<\/strong> MP nepodporuje prep\u00edsanie user agenta alebo IP adresy, tak\u017ee udalosti odoslan\u00e9 z MP nemaj\u00fa dostupn\u00e9 \u00fadaje o polohe alebo prehliada\u010di. Mo\u017eno sa to \u010dasom v Googli zmen\u00ed, zatia\u013e s t\u00fdm teda ni\u010d nesprav\u00edme.<\/span><\/li>\n
        2. V GA4 je defaultne nastaven\u00e1 IP anonymiz\u00e1cia<\/strong>, tak\u017ee bli\u017e\u0161ie geografick\u00e9 \u00fadaje ako mesto, alebo regi\u00f3n m\u00f4\u017eu by\u0165 (not set).<\/span><\/li>\n
        3. Server-side GTM prepisuje, alebo vymaz\u00e1va IP adresu.<\/strong><\/li>\n
        4. Niektor\u00ed n\u00e1v\u0161tevn\u00edci webu m\u00f4\u017eu pou\u017e\u00edva\u0165 VPN<\/strong>, proxy adresy a in\u00e9 n\u00e1stroje, ktor\u00e9 v\u00e1m neposkytn\u00fa \u00fadaje o IP adrese.<\/span><\/li>\n<\/ol>\n

          13. Event-scoped a Item-scoped dimenzie s\u00fa (not set)<\/strong><\/h2>\n

          Tieto dimenzie sa t\u00fdkaj\u00fa len konkr\u00e9tneho eventu.<\/strong> Nasleduj\u00face alebo predch\u00e1dzaj\u00face eventy tieto hodnoty nezdedia. Skontrolujte si teda, \u010di tieto dimenzie posielate s ka\u017ed\u00fdm eventom.\u00a0<\/span><\/p>\n

          Ke\u010f implementujete ecommerce tracking, bu\u010fte konzistentn\u00ed. Posielajte rovnak\u00e9 parametre po\u010das celej cesty pou\u017e\u00edvate\u013ea.<\/span><\/p>\n

          Taktie\u017e dajte pozor na to, kedy dan\u00e9 dimenzie registrujete. Ak ich zaregistrujete ako custom dimenzie po odosielan\u00ed eventu do GA4, bude ma\u0165 nepriraden\u00e9 hodnoty. Custom dimenzie nie s\u00fa retroakt\u00edvne, ich hodnoty uvid\u00edte a\u017e po registr\u00e1cii.\u00a0<\/span><\/p>\n

          14. User-scoped dimenzie s\u00fa (not set)<\/strong><\/h2>\n

          Pri user-scoped dimenzi\u00e1ch syst\u00e9m nepracuje tak, ako by mal. Ve\u013eakr\u00e1t m\u00e1me pri nich hodnotu (not set), aj napriek tomu, \u017ee sa dan\u00e1 dimenzia odosiela s ka\u017ed\u00fdm eventom. Je to bug na strane Googlu, ktor\u00fd ,d\u00fafajme, \u010dasom odstr\u00e1nia.<\/strong><\/span><\/p>\n

          Rie\u0161en\u00edm je odosiela\u0165 tieto custom dimenzie ako event-scoped.<\/strong> User property odosielajte s ka\u017ed\u00fdm tagom, nielen konfigura\u010dn\u00fdm. A nezabudnite registrova\u0165 custom dimenzie sk\u00f4r, ako ich za\u010dnete odosiela\u0165.<\/span><\/p>\n

          15. Technologick\u00e9 dimenzie s\u00fa (not set)<\/strong><\/h2>\n

          Pre ch\u00fdbaj\u00face hodnoty m\u00f4\u017eu by\u0165 nasledovn\u00e9 d\u00f4vody:<\/span><\/p>\n

            \n
          1. Pokia\u013e sa event odosiela cez Measurement protocol,<\/strong> MP nepovo\u013euje posiela\u0165 pou\u017e\u00edvate\u013esk\u00e9ho agenta, ktor\u00fd obsahuje inform\u00e1cie o prehliada\u010di, zariaden\u00ed.<\/span><\/li>\n
          2. Server-side GTM m\u00f4\u017ee z d\u00f4vodu ochrany osobn\u00fdch \u00fadajov user agenta prep\u00edsa\u0165<\/strong> a v tom pr\u00edpade bud\u00fa inform\u00e1cie o prehliada\u010di, jeho verzii a i, tie\u017e ch\u00fdba\u0165.<\/span><\/li>\n
          3. Ak niekto pou\u017e\u00edva roz\u0161\u00edrenia v prehliada\u010di<\/strong>, inform\u00e1cie o prehliada\u010di m\u00f4\u017eu by\u0165 skryt\u00e9.\u00a0<\/span><\/li>\n<\/ol>\n

            \"Kompletn\u00fd<\/a><\/p>\n

            Z\u00e1ver<\/strong><\/h2>\n

            Mo\u017enost\u00ed, kedy sa v\u00e1m m\u00f4\u017eu objavi\u0165 (not set) hodnoty vo va\u0161ich GA4 reportoch, je ve\u013ea…<\/span><\/p>\n

            Znamen\u00e1 to, \u017ee syst\u00e9m bu\u010f dan\u00e9 d\u00e1ta nem\u00e1, alebo ich nerozpozn\u00e1. V tomto blogu sme v\u00e1m priniesli viacero rie\u0161en\u00ed, ako (not set) d\u00e1ta odstr\u00e1ni\u0165, av\u0161ak v niektor\u00fdch pr\u00edpadoch je to sp\u00f4soben\u00e9 t\u00fdm, ako GA4 funguje.<\/span><\/p>\n

            Pokia\u013e v\u00e1m aj napriek na\u0161\u00edm n\u00e1vrhom (not set) d\u00e1ta v reportoch st\u00e1le svietia, kontaktujte n\u00e1s a spolu sa na to pozrieme. 🖖<\/strong><\/p>\n

             <\/p>\n","protected":false},"excerpt":{"rendered":"

            Asi ka\u017ed\u00fd sa u\u017e stretol v GA4 reportoch s nevy\u017eiadanou hodnotou (not set). (not set) sa zobrazuje v…<\/p>\n","protected":false},"author":79,"featured_media":20125,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[803,639],"tags":[799,798,994,805,937],"_links":{"self":[{"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/posts\/20116"}],"collection":[{"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/users\/79"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/comments?post=20116"}],"version-history":[{"count":11,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/posts\/20116\/revisions"}],"predecessor-version":[{"id":20139,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/posts\/20116\/revisions\/20139"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/media\/20125"}],"wp:attachment":[{"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/media?parent=20116"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/categories?post=20116"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dase-analytics.com\/blog\/sk\/wp-json\/wp\/v2\/tags?post=20116"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}