Skip to content

Log File Provision

Service Description v6.0 | 06.03.2026

This service will be discontinued as of February 28, 2026.

Would you like to continuously analyze and optimize your digital offering individually, or evaluate conspicuous features independently in order to optimally improve the content structures of your offering through transparent insight?

You'll receive data privacy-compliant raw log file data with various parameters, such as document referrer, browser type, and INFOnline-typical key figures like code and offer identifier.

In other words: You always have your raw data right in view!

Scope of service

As part of the Log File Provision service, you are provided with raw logfile data that contains information about the measurement pulses that enter the measurement system for your digital offer. The following parameters are made available to you: document referrer, pixel referrer, browser type, resolution, device information, and the INFOnline-typical key figures such as code, offer identifier and comment.

The data is accessed via an HTTP API from which you can download the log files manually or automatically using curl or a comparable HTTP client.

Order

The Log File Provision service is ordered via the INFOnline Order Center. The service can be booked for any registered digital offering.

Provision

  • The raw log data is provided via an HTTP API at https://log.ioam.de/<offer_identifier>.
  • In the setup or confirmation e-mail, the client receives the associated credentials (username and password for HTTP Basic Auth).
  • The username corresponds to the offer identifier (site_id).

The service as well as the mail with all necessary information will be provided within 3 working days.

Note

Only one concurrent data retrieval per offer identifier is possible. If a download is already in progress, HTTP status code 429 (Too Many Requests) is returned.

Data availability

  • The log data is available with a delay of approximately 10 minutes after the end of the requested time range. If a time range is not yet available, HTTP status code 503 is returned with a Retry-After header.
  • The log file data is stored for a maximum of 90 days, after which the data is no longer available.
  • A separate data backup outside this period does not take place.
  • The availability of the log file provision is 99 percent.
  • However, there is no entitlement to subsequent delivery of log file data in the event of technical failures.

Term

The service term applies from the time of setup until the service is terminated or the metering contract for the corresponding digital offer is terminated.

If the log file provision is set up before the 15th of a month, this month is counted as a full month. If the log file provision is set up after the 15th of a month, the term of the service begins on the 1st of the following month.

Cancellation

The notice period is always 4 weeks to the end of the quarter. It is sufficient to send an e-mail with the reason for termination to the following address: service@infonline.de. If you cancel the measurement of the digital offer, the service will automatically expire.

Costs

Invoicing takes place quarterly in advance.

The costs consist of a one-time setup fee of 100€ and an annual fee based on the following assessment basis:

Assessment basis:

New customers = page impressions of the last month of the test phase Existing customers = average page impressions of the 2nd quarter of the previous year

The discount regulation is not applicable to the prices of the Log File Provision service. All prices are exclusive of the statutory value added tax.

Grading according to page impressions Setup fee Base costs/annual Additional service Advanced/annual
up to 10,000,000 PIs 100 € 100 € 25 €
10,000,001 to 100,000,000 PIs 100 € 500 € 125 €
100,000,001 to 500,000,000 PIs 100 € 1,000 € 250 €
500,000,001 to 1,000,000,000 PIs 100 € 1,500 € 500 €
1,000,000,001 to 10,000,000,000 PIs 100 € 2,000 € 750 €
from 10,000,000,001 PIs on request on request on request

Technical information

Log file delivery

The log file data is accessed via an HTTP API at:

1
https://log.ioam.de/<offer_identifier>

Authentication is performed via HTTP Basic Auth. The username must match the offer identifier, the password is provided during setup. Data transfer is encrypted via SSL.

Download options

Full day (without time parameter):

1
2
3
curl -u <offer_identifier>:<password> \
  "https://log.ioam.de/<offer_identifier>?date=2026-03-01" \
  -o events.log.gz

5-minute time window (with time parameter):

1
2
3
curl -u <offer_identifier>:<password> \
  "https://log.ioam.de/<offer_identifier>?date=2026-03-01&time=10:05" \
  -o events.log.gz

The time parameter specifies the end of the 5-minute window. time=10:05 returns data from 10:00 to 10:05 UTC. The value must be a multiple of 5 minutes (e.g. 10:00, 10:05, 10:10, ...).

The special case time=00:00 returns the time window 23:55–00:00 of the previous day.

If the date parameter is omitted, yesterday's date is used by default.

Parameters

Parameter Required Format Description
offer_identifier Yes (URL path) [a-zA-Z0-9_-]+ Offer identifier (must match Basic Auth username)
date No YYYY-MM-DD Date of the data. Default: yesterday. Maximum 90 days in the past.
time No HH:MM 5-minute time window. Specifies the end of the window. Must be a multiple of 5. If omitted, the full day is returned.

Response

  • Content-Type: application/gzip
  • Content-Disposition: attachment; filename="<offer_identifier>_YYYYMMDD_HHMM.log.gz"
  • Body: gzip-compressed, pipe-delimited log lines (14 fields per line)

HTTP status codes

Code Meaning Description
200 Success Gzip data stream
400 Bad Request Invalid date, time not a multiple of 5, or date older than 90 days
401 Unauthorized Missing or incorrect credentials
403 Forbidden Username does not match offer identifier
429 Too Many Requests Another download for this offer identifier is already in progress
503 Service Unavailable Data is still being processed (includes Retry-After header in seconds)

Health check

An unauthenticated health check endpoint is available at https://log.ioam.de/health.

Log file data

Data fields in log lines

Each log line contains 14 pipe-delimited (|) fields. Pipe characters within field values are automatically removed.

Example: Excerpt from a downloaded log file

1
1380279169.342900|193.46.63.0| |de.ioam.de|OK N4 N9|000605e97501e61fd50f475930001|ap=0&cb=0007&cn=de&co=a%20comment&cp=sus&cs=z26cu9&ct=0000810141&dc=web&id=qpc1so&it=mm&la=1380273421&lo=DE%2FNordrhein-Westfalen&lt=1380279168058&mo=1&mv=1.8.0&pt=CP&sc=yes&st=infonlin&ur=www.infonline.de&vr=5.4.0&vs=1.0.0&xy=1920x1080x24|i00=00145b9eb35278f965242b3dc0001%3B5242b4a4%3B53c79048|Mozilla/5.0 (Windows NT 6.1; WOW64; rv:23.0) Gecko/20100101 Firefox/23.0|https://www.infonline.de/de/service-support/|015|web|OK|OK

Explanation of data fields

No. Field Description Example
1 Timestamp Timestamp of the measurement pulse (Unix timestamp in seconds with microseconds) 1380279169.342900
2 Client IP IP address of the client 193.46.63.0
3 X-Forwarded-For Content of the HTTP header "X-Forwarded-For", usually empty
4 Domain Hostname of the requested measurement system de.ioam.de
5 Status code Status code of the measurement pulse (possible values: "OK", "N1", "N3"–"N14", may contain multiple values) OK N4 N9
6 Cookie ID ID consisting of: box number (hex) + random number + timestamp (hex) + cookie serial number 000605e97501e61fd50f475930001
7 Parameters Parameters collected by sensor/library (URL-encoded, sorted alphabetically, separated by &) cb=0007&cn=de&cp=sus&...
8 Cookie string Value of cookie i00 of the domain "ioam.de" i00=00145b9eb35278f965242b3dc0001%3B...
9 User agent User agent string of the browser used Mozilla/5.0 ...
10 Referrer Page URL called by the user (HTTP referrer) https://www.infonline.de/
11 Cube no. Number of the measurement server that received the request 015
12 Dimension Type of measurement (currently "web", "mew", "app", "hyb" possible) web
13 Status Validation result (currently always "OK") OK
14 Bot detection Result of automatic bot detection: "OK" = human traffic, "ERR" = bot traffic OK
Note

Compared to the previous log file provision, the data format has the following changes:

  • Parameters (field 7): Parameters are now output sorted alphabetically by key. The order may therefore differ from the previous output.
  • Bot detection (field 14): Instead of the user agent whitelist check, automatic bot detection is now performed. "OK" means human traffic, "ERR" means bot traffic.

Explanation of parameters (field 7)

The following parameters may be present in field 7. Not all parameters are always available — availability depends on the integration type and web sensor version.

Parameter Description
Public (set by client via SZM tag or in app)
cp= Page code (can also be specified via fp= [Flash], np= [newsletters], xp= [non-counting test])
st= Offer identifier / app identifier for app measurement
Public / Optional (optionally set by customer)
co= Comment field
sc= MCVD (Multistage Client & Visit Detection) activation, Web/MEW only
ie= Customer-provided fingerprint for the client
mc= Transfer value for MCLIENT method
mo= Response mode (no value/1 = blank.gif, 2 = empty script)
cn= Market (country) for which the digital content is primarily measured (default "de"). From web sensor version 5.0.0.
Private (collected by measurement script or library)
cb= Cube number: number of the measurement server that delivered "iam.js"
cs= Checksum over all transmitted parameters
ev= Event for apps, video and audio measurement
i2= ID of the 1st-party cookie
i3= Information about the 1st-party cookie
id= Browser fingerprint (Jenkins hash of plugin information)
lo= Location as country and state
lt= Local time on client
pt= Pixel type
r2= Unshortened document referrer
rf= Document referrer
ur= Pixel referrer (accessed website of the offer)
u2= Unshortened pixel referrer (only with certain browsers)
vr= Version of the script "iam.js"
xy= Resolution and color depth of client screen
ct= INFOnline consent notation (TCF2.x)
tb= Tab detection status
ap= Google AMP integration flag (0/1). From web sensor version 5.0.0.
fb= Facebook Instant Article integration flag (0/1). From web sensor version 5.0.0.
dc= Distribution channel (web, hyb, ctv). From web sensor version 5.0.0.
it= Integration type (mm = Measurement Manager, sa = Standalone). From web sensor version 5.0.0.
nt= Navigation type based on Performance Navigation API (0–4). From web sensor version 5.0.0.
vs= Data schema version of the measurement request. From web sensor version 5.0.0.
uahint= User-Agent Client Hints
mv= Measurement Manager version. From web sensor version 5.1.0.
i5= Origin identifier, hashed UUIDv4. From web sensor version 5.5.0.
Private (added by measurement system)
la= Last occurrence of the cookie
mt= Time of event registration on the IO measurement server
u3= Hash of unshortened pixel referrer
Private / Apps (collected by measurement library only)
ae= [Native app measurement] complex JSON data type (see below)
bo= [Hybrid app measurement] Unix timestamp of DeviceID registration
er= [Hybrid app measurement] Transmitted error
fs= [Hybrid app measurement] Original offer identifier of the web page
ls= [Hybrid app measurement] LSO identifier
mi= [Hybrid app measurement] complex JSON data type (see below)

Explanation of status codes (field 5)

Status code Meaning Effect
OK No Error (If no error occurred, notifications (Nx) are possible) normal
N1 No uuid found, inside ae or mi normal
N3 uuid found, ie set normal
N4 i00-Cookie not set normal
N5 Renew cookie, because of lower serial normal
N6 mi found, ie set (hybrid measurement) normal
N7 ls found, ie set (iPhone hack) normal
N8 no id found, using hash normal
N9 no id found, using hash plus JavaScript fingerprint normal
N10 LSO not accessible normal
N11 aid.io fault normal
N12 Marking for IPv6 (preparation for IPv6) normal
N13 Code type was missing in call, set to CP with default empty code (JS functionality) normal
N14 Cookie broken, was set again normal

JSON data fields in app log files

In app measurement, additional data is transmitted by the library in JSON format:

  • ae (native apps): Events in the native part of an app
  • mi (hybrid apps): Events in the hybrid part of an app (e.g. content from web page)

This JSON data is included in the parameters field (field 7) as a URL-encoded JSON string.

JSON data structure:

JSON data structure Description
application [ae] App version details
client [ae, mi] Client details (OS, OS version, country, language, carrier, etc.)
client/screen [ae, mi] Information about the screen resolution of the client
client/uuids [ae, mi] UUIDs of the client (e.g. "advertisingIdentifier" for iOS or "androidId" for Android)
events [ae] OS event that triggered the measurement pulse
library [ae, mi] Information about the version of the measurement library
protocolVersion [ae] Version of the JSON object
stats [ae] Event handling error

Last update: March 6, 2026