ProLitteris

we have summarized the most important parts of the prolitteris integration for the purple experience here please refer to the latest version of the original prolitteris integration guide, which you receive as a member from prolitteris an older version of the document can be found on https //prolitteris ch/hilfe dokumente online meldesystem/ for any content, a prolitteris pixel is to be added to the source code of the website after a grace period for the content to undergo editorial changes (usually 14 days), the content and author information are posted to prolitteris systems to ensure legacy content is properly tracked, please make sure to import the original tracking information to purple systems purple will render the tracking codes, but any content created from legacy systems must be posted to prolitteris systems from the legacy system preconditions you'll need to set up and gather some data from prolitteris to implement this make sure you have enabled "verlagsinterne zählmarken" prolitteris zähldomäne prolitteris mitgliedsnummer 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 the pixel is created by a script, "ptag min js", which must be loaded from prolitteris the pixel mostly consists of three parts “https //domain owen prolitteris ch” the tracking domain a specific one is issued per each customer by prolitteris “na” the indicator for publicly available contents use “pw” for protected contents “vzm 12345 79c9e1ac 96f1 11e5 85a6 000c29f1f6c4”, the properly formatted zählmarke for the text in question we generally use "verlagsinterne zählmarken " it's always built from the prefix „vzm “ , and the prolitteris mitgliedsnummer of the publisher, followed by a " " and the unique id of the content integration in html pixel must be integrated in the body respect special requirements when loading full content lazily and indefinitely respect requirements for meta tags on page prolitteris reporting as soon as tracking is implemented as stated above, you can enable prolitteris reporting from the purple manager the data is transferred with a minimum delay of two weeks prolitteris 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 to avoid unnecessarily reporting test contents reporting is done every night, starting at 11pm and finishing 5 hours later during that time, error reports are being sent to email addresses configured in the purple manager errors may contain hints like "text is too short (min length 1,000 characters)" or "no participants given " 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 prolitteris again the following night storing author fields 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 prolitterisauthor are sent to vg wort the property prolitterisauthor should contain the prolitteris mitgliedsnummer of the author and can be omitted if no such value is known first name and last name are mandatory the prolitterisauthor 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 a new dialog here the slug needs to be set to prolitterisauthor 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 who is supposed to be edited there, the fields can be set and saved by clicking on "update"