📗
One Consent
  • Next14 CMP
  • Proof of Consent
  • 🤔 Generic FAQ
  • 📱Mobile APPs
    • Installation
    • The CMP
    • Consents
      • Consents to TCF partners
      • Consents to Google ATP
      • Consents to Custom Partners
    • Debugging the CMP
      • CMP Flow
      • CMP deep link
      • CMP preferences
    • IAB TCF Vendors
    • 🤔 Technical FAQ
  • Next14 Proximity SDK Docs
Powered by GitBook
On this page

Was this helpful?

  1. 📱Mobile APPs
  2. Debugging the CMP

CMP deep link

How CMP dialog return the result to the APP

PreviousCMP FlowNextCMP preferences

Last updated 1 year ago

Was this helpful?

CMP Dialog generate a deep-link in the following format:

consent://CO_pO56O_pO56ERACAENBICsAP_AAH_AAAAAHONd_X_fb39j-_59_9t0eY1f9_7_v-0zjgeds-8Nyd_X_L8X42M7vF36pq4KuR4Eu3LBIQFlHOHUTUmw6IkVrTPsak2Mr7NKJ7PEinMbe2dYGHtfn9VTuZKYr97s___z__-__v__75f_r-3_3_vp9X---_e_QOXAJMNS-AizEscCSaNKoUQIQriQ6AUAFFCMLRNYQErgp2VwEfoIGACA1ARgRAgxBRiwCAAAAAJKIgJADwQCIAiAQAAgBUgIQAEaAILACQMAgAFANCwAigCECQgyOCo5TAgIkWignkjAEou9jDCEMosAKBR_QAAA.fZgAAAAAAMAA

The string is a TCF Consent String that can be parsed with a TCF String parser as - for example - the one provided by Ãœber Uns:

https://www.tcfv2.de/consent_string_decoder.php