If you subscribe to ClinicalKey Student, you may want to track its usage separately from the overall ClinicalKey platform.
Although ClinicalKey is COUNTER compliant, Elsevier includes ClinicalKey Student usage in the standard COUNTER reports by using a custom attribute (clinicalkey:Product). CELUS does not natively support this custom attribute, as doing so could compromise the consistency and reliability of COUNTER data processing.
To address this, we provide a dedicated non-COUNTER platform for ClinicalKey Student, allowing you to upload its usage separately.
To avoid manually editing COUNTER reports (for example, removing non-ClinicalKey Student rows), we recommend asking your Elsevier representative to provide a report containing only ClinicalKey Student usage.
Important: When configuring your reports, make sure your usage is not duplicated by filtering out ClinicalKey and ClinicalKey Student at the same time.