Skip to content

Standalone solution: Censor sensor newsletter measurement

You want to collect the full potential of your data via INFOnline Measurement?

We recommend that you additionally integrate the pseudonymous measurement into your newsletter. Please note that participation of your digital offering in IVW reporting or agof studies may require parallel integration of pseudonymous measurement and census measurement in your newsletter.

You can find the integration guide for pseudonymous measurement here.


If you activate pseudonymous measurement via the INFOnline Measurement Manager, it is mandatory to have the standalone script integrated in newsletter.


  • Relay client container (hosted by INFOnline or self-hosted)
  • Registered domain service name as CNAME (hosted by INFOnline), AAA(A) (self-hosted), DNS entry
  • Site ID (provided by INFOnline GmbH)


Similar to pseudonymous measurement, census measurement also provides integration for newsletter measurement. To enable the measurement of HTML newsletters, a functionally restricted HTTP call is used without the use of JavaScript. This measurement variant comes with a number of limitations due to the lack of JavaScript functionality:

  • no collection of URLs or HTTP referrers with privacy-compliant automatic shortening
  • no consideration of DNT
  • limited ability to detect false or automatic retrievals


The HTTP call for HTML newsletters is implemented with a simple <img> tag that is built into the <body> of the HTML newsletter:

<img src="https://<domain service name>/<code>&st=<site>&cn=<country>" alt="iomb_np" width="1" height="1" />

- To ensure correct measurement, the tag must be copied unchanged into the source code of the respective newsletter.
- Only the placeholders framed by <...> may be changed.
- Line breaks, upper and lower case must be kept!

The following placeholders must be adjusted accordingly when including the <img> tag in your newsletter:

Placeholder Type Default Length Pattern Mandatory Description
<site> string - 15 ^[a-zA-Z0-9_]*$ yes site identifier
<domain service name> String - - INFOnline CNAME convention1 yes Domain service name (CNAME or AAA(A) host)2
<country> Enum de - no INFOnline Country (de or at)
<code> String non-mapping_code 256 [^a-zA-Z0-9,_/\-?#.] yes Newsletter code for the IVW Kat 2.0 association
<comment> string - 256 /[ -~]/ no optional comment

1 INFOnline CNAME convention: /^(data-)([a-f0-9]{10})\.([a-zA-Z0-9][a-zA-Z0-9-_]{0,61})(?:\.([a-z]{2,62}))?\.([a-z]{2,62})$/

2 If the notation of dn / domainServiceName does not match the INFOnline CNAME convention mentioned, no measurement takes place

Newsletter code handling.

All codes used in newsletter measurement are prefixed with PUSH_ when entered into the measuring system. The consequences of this special treatment are shown below with an example.

You use the following call in the HTML source code of the newsletter email:

<img src="https://<domain service name>/" alt="iomb_np" width="1" height="1" />
When a user calls up the newsletter email, a measurement pulse with the code foo is sent to the INFOnline census processing system, which automatically prefixes the code with PUSH_ when capturing the measurement pulse. Thus foo becomes PUSH_foo and is consistently passed on to the subsequent systems in the notation shown above:

  • Code allocation in the customer center
  • IDAS evaluation
  • All data deliveries containing arbitrary page codes

Last update: February 11, 2022