TCF v2.x / GDPR Compliance

​

How it Works

1. CMP Implementation: You must first implement a TCF v2.x compliant CMP (like OneTrust, TrustArc, Didomi, Sourcepoint, etc.) in your React Native app. This CMP is responsible for displaying the consent UI to users and storing their preferences locally.
2. SDK Detection: When the Zeotap React Native SDK initializes with the correct configuration (see below), it automatically detects the presence of TCF data stored by the CMP in AsyncStorage or other local storage.
3. Consent Retrieval: The SDK reads the stored TCF consent data including:
   • The user’s current consent status (encoded in the TC String).
   • Purpose consents and legitimate interests.
   • Vendor consents (if check_zeotap_vendor_consent is enabled).
4. Decision Making: Based on the retrieved TC String and the SDK’s configuration, the SDK determines whether it has consent for specific actions:
   • Purpose Consent: Checks if consent has been granted for the specific IAB TCF Purposes required for tracking (purposes_for_tracking).
5. Action Execution:
   • If the necessary consents are present, the SDK will proceed with tracking events (setEventProperties, setUserProperties, etc.).
   • If the necessary consents are not present, the SDK will block those specific actions and won’t queue any events until consent is obtained.

​

Configuration

// SDK Initialization for TCF v2.x Integration
import { initialiseZeoCollect } from 'zeo-collect';

const options = {
    android_write_key: "YOUR_ANDROID_WRITE_KEY",
    ios_write_key: "YOUR_IOS_WRITE_KEY",
    // --- Core TCF Configuration ---
    use_consent: true,           // REQUIRED: Enables consent management features
    check_for_cmp: true,         // REQUIRED: Tells the SDK to look for TCF data
    
    // --- Optional TCF Fine-tuning ---
    // Define which TCF Purposes are required for tracking
    // Defaults may vary, but explicitly setting is recommended
    purposes_for_tracking: [1, 3, 4], // Purpose 1 (Store/Access Info), 3 (Ad Selection), 4 (Content Selection)
    
    // Optional: Check for Zeotap vendor consent in addition to purpose consent
    check_zeotap_vendor_consent: true
};

initialiseZeoCollect(options);

​

Common TCF Purpose IDs

• Purpose 1: Store and/or access information on a device
• Purpose 2: Select basic ads
• Purpose 3: Create a personalised ads profile
• Purpose 4: Select personalised ads
• Purpose 5: Create a personalised content profile
• Purpose 6: Select personalised content
• Purpose 7: Measure ad performance
• Purpose 8: Measure content performance
• Purpose 9: Apply market research to generate audience insights
• Purpose 10: Develop and improve products

​

Interaction with setConsent API

• The track parameter within the setConsent object is ignored as tracking consent is determined by the TCF data.
• However, any Brand Consents included in the setConsent call (e.g., { "myBrandConsent": true }) will still be processed, stored, and sent with subsequent events under the z_p query parameter. This allows you to manage non-TCF consents alongside TCF integration.

import { setConsent } from 'zeo-collect';

// Example: Even with TCF enabled, this call will still store 'brandConsent'
// but the 'track: true' will be ignored in favor of the TCF signal
setConsent({
    track: true, // This value is IGNORED when check_for_cmp is true
    brandConsent: true // This custom/brand consent IS processed
});

​

CMP Integration Considerations

​

Timing

• Initialize your CMP before initializing the Zeotap SDK
• Ensure TCF data is available when the SDK starts
• The SDK may queue events until valid consent is determined

​

Data Storage

• TCF data is typically stored in AsyncStorage by the CMP
• The SDK looks for standard TCF keys like IABTCF_TCString, IABTCF_PurposeConsents, etc.
• Ensure your CMP correctly writes TCF data to these standard locations

​

Consent Updates

• When users update their consent preferences through your CMP, the SDK will automatically detect the changes
• No additional API calls are needed for basic tracking consent
• Use setConsent() only for brand-specific consents

​

Best Practices

1. CMP First: Always initialize and configure your CMP before the Zeotap SDK
2. Purpose Selection: Carefully choose which TCF purposes are required for your use case
3. Vendor Consent: Consider enabling check_zeotap_vendor_consent for stricter compliance
4. Testing: Test with different consent scenarios (all accepted, all rejected, mixed)
5. Documentation: Document which purposes your app requires and why

​

Troubleshooting

• Verify TCF data is being written to AsyncStorage by your CMP
• Check that use_consent: true and check_for_cmp: true are set
• Ensure purpose IDs in purposes_for_tracking match your CMP configuration

• Check if required purposes have consent in the TCF data
• Verify Zeotap vendor consent if check_zeotap_vendor_consent is enabled
• Review SDK logs for consent-related messages

​

Related Documentation

• Consent Configuration Options: Detailed configuration options for consent management
• Set Consent API: API reference for managing user consent
• Choosing a Consent Strategy: Guide to choosing the right consent approach
• Custom Consent Management: Alternative approach using manual consent