Manual TCF processing iOS¶
Manual processing uses the setCustomConsent method. It takes a string in the INFOnline Consent String Notation, not the CMP's TC string.
When the consent must be set
setCustomConsentonly takes effect while the session is running. Call it directly after starting the session, before the first event.- The value only applies to the running session. Set it again after every session start.
- The IOLib discards events without valid consent before sending (see Effect on measurement).
For measurement in Austria (ÖWA), use the session type IOLSessionTypeOEWA or .OEWA instead of SZM in all calls.
Objective-C¶
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 | |
Swift¶
1 2 3 4 5 6 7 8 9 10 11 12 13 | |
Priority of automatic processing¶
The IOLib prioritises automatic processing over manual processing. If automatic processing produces a valid IO consent string, that string is transmitted and the manual one is ignored. As of version 2.7.0 you can force manual processing.
Checking¶
The consent method returns the IO consent string currently used for transmission.
Objective-C:
[IOLSession defaultSessionFor:IOLSessionTypeSZM].consent;
Swift:
IOLSession.defaultSession(for: .SZM).consent()
Whether the IOLib discards events for missing consent is only shown in debug mode with IOLDebugLevelTrace.