VG Wort

we have summarized the most important parts of the vg wort integration for the purple experience here please refer to the latest version of the original vg wort integration guide at the time of writing, version 2 26 is current for any content, a vg wort pixel is added to the source code of the website after a grace period for the content to undergo editorial changes, (usually, as recommended by vg wort, 14 days) the content and author information is posted to vg wort systems to ensure legacy content is properly tracked, please make sure to import the original tracking information to purples' systems purple will render the tracking codes, but any content created from legacy systems must be posted to vg wort systems from the legacy system preconditions you'll need to set up and gather some data from vg wort to implement this make sure you have enabled "verlagsinterne zählmarken" vg wort zählmarken domäne vg wort karteinummer in addition to tracking, you will also need to set up services in the purple hub to connect authors to the article tracking system construction of the pixel purple currently does not support base64 encoded pixels for vg wort we generally use "verlagsinterne zählmarke " the pixel mostly consists of three parts “https //domain met vgwort de” the tracking domain a specific one is issued per each customer by vg wort “/na/” which is just a part of the tracking pixel and must not be omitted “vgzm 970 123456789”, the properly formatted, internal key of the publisher for the text in question it's always built from the prefix „vgzm “ , and the vg wort karteinummer of the publisher, followed by a " " and the publisher unique id of the content the id must not contain any characters other than \[a z]\[a z]\[0 9] and periods (dots), hyphens (minus) and underscores as it is otherwise freely configurable, you may decide to add further information to it if the content is paid, another prefix, "pw " is added example free https //domain met vgwort de/na/vgzm 970 123456789 https //domain met vgwort de/na/vgzm 970 123456789 " example paid https //domain met vgwort de/na/pw vgzm 970 123456789 https //domain met vgwort de/na/pw vgzm 970 123456789 " integration in html pixel must be integrated in the body respect special requirements when loading full content lazy and indefinitely respect requirements for meta tags on page purple integration the pixel is created from a bit javascript set in the custom server js vgwpixel (contentid, isplus) => { / contentid $context content id isplus $context content access the pixel must not be set if a paywall is displayed please configure the views json accordingly / // global variables not available from builder preview, as testing on device currently not possible circumventing global variables here let baseurl = "https //met example com"; let publisherid = "4711"; let path = `${baseurl}/na/` if (isplus !== "free") { path += 'pw '; } path += `vgzm ${publisherid} ${contentid}`; let finalurl = path; return finalurl } the integration as \<img> tag is done via views json find an example for such a section below { "content" \[ { "tag" "img", "type" "html", "content" "vgwort", "attributes" { "src" "$functions vgwpixel($context content id, $context content access)", "height" "1", "width" "1", "border" "0" } } ], "type" "section", "condition" { "or" \[ { "comparevalue" "free", "value" "$context content access" }, { "comparevalue" "purchased", "value" "$context content access" } ] } } vg wort reporting as soon as tracking is implemented as stated above, you can enable vg wort reporting from the purple manager the data is transferred, by request of vg wort, with a minimum delay of two weeks vg wort reporting is to be configured per purple manager team furthermore, the actual public live domains must be marked at the "experience" page of the app in the purple manager, as the live article urls are to be provided to vg wort as requested by vg wort the reporting is done every night between 10pm and 3am only during that time, error reports are being sent to email addresses configured in the purple manager errors may contain hints like "the article has less than 1800 characters" or "at least one author is required" the errors can be ignored but if articles are changed after such an error code is received, we try to report the changed article to vg wort again the following night for an article to be successfully sent, at least one taxonomy of type author must be present the values of its properties first name , last name and vgwortauthor are sent to vg wort the property vgwortauthor should contain the vg wort card number (karteinummer) of the author author taxonomy as to be discovered in the content cloud explorer the vgwortauthor field for authors must be added as a custom field in the authors plugin this can be done via authors > author fields > new author field, which opens up the following view author field in the hub here the slug needs to be set to vgwortauthor and then saved afterward, the data must be added for every author in the hub this can be done by opening the authors overview by selecting "authors" in the hub menu, and then editing the authors by clicking on "edit" for the author that is supposed to be edited there, the fields can be set and saved by clicking on "update"