Skip to content

Manual Consent Transmission with the INFOnline Measurement Manager

Note on the use of manual codenotation

The use of the measurement procedure is the responsibility of the provider of digital sites; the latter is also responsible for fulfilling the information obligations stipulated in Art. 13 of the German Data Protection Regulation (DS-GVO) and for obtaining the consent of its users (§25 TDDDG) when using the pseudonymous measurement method. This also applies when using manual consent transmission.

The publisher has the option to pass a manual consent string that overrides any TCF2.X API consent and terminates the TCF consent request. It follows the IO Consent String notation, which is a hexadecimal representation of the consent given for the various vendors.

The notation consists of a 2-byte prefix indicating the source of the consent given. For manual consents, this is always 00. This is followed by 4 bytes for each provider, representing the purposes (including Special Feature Optins) specified for each provider. Currently, providers are limited to 730 (INFOnline).

Important to note

Please only use manual Consent submission if you have enabled pseudonymous measurement via Measurement Manager.

The publisher must send the IO Consent String (ct) parameter via the configure command as payload:

1
2
3
<script type='text/javascript'>
  IOMm('configure', { st: 'foo' dn: 'data-acbd18db4c.example.com', ct: '0000810000', mh:5 });
</script>
Attention

Passing a manual Consent String will overwrite existing TCF2.x Consent Strings

Representation of the IO Consent String notation as a formula:

1
𝐼𝑂𝑐𝑡={[00−𝐹𝐹],[0000−𝐹𝐹𝐹𝐹],[0000−𝐹𝐹𝐹𝐹],…}

The order and number of providers enabled are determined by INFOnline (currently 730). Each processing purpose corresponds to a power (𝑛) to the base 2 (2𝑛). See table below

Purpose (TCF 2.x) Type Power
01 Purpose 20
02 Purpose 21
03 Purpose 22
04 Purpose 23
05 Purpose 24
06 Purpose 25
07 Purpose 26
08 Purpose 27
09 Purpose 28
10 Purpose 29
01 Special Feature Optin 210
02 Special Feature Optin 211

The uses for each vendor are added (according to the conversion table) and then converted to the 4-byte hex field.

Examples

Vendor 730 (INFOnline): Consent for Purpose 1 and Purpose 8

This is how the INFOnline Consent string is calculated:

  • Prefix: We pass the consent string manually, so our 2-byte prefix is always 00.
  • Provider 730 (INFOnline): We use the purposes 1 and 8 and have to add them. According to the conversion table, this is 20 (1) + 27 (128) = 129. In 4 byte hexadecimal notation, this is `0081.

Combined, our manual consent string now looks like this: 0000810000 (prefix + provider 730 + 0000). And this is the format we use to pass it as ct``` parameter to theconfigure`` command.

Always check the quality of your measurement
Last update: August 21, 2026