Consent passing from Mobile Core SDK to AEP | Adobe Higher Education
Skip to main content
S
stefanm38281801
Level 4
February 14, 2022
Répondu

Consent passing from Mobile Core SDK to AEP

Hi,


I'm trying to figure out how consent is passed from Mobile Core SDK (latest AEPCore version), with the Edge Consent being configured in Data Collection as well.

From the Mobile app, I'm performing an updateConsent call with setting the marketing options on the generic level:

["collect": ["val": "y"], "marketing": ["preferred": "email","any":["val": "y"],"email":["val": "y"],"push":["val": "y"]]]
 
In AEP however, I see these consents specifically being added to the ECID identity:
consents.idSpecific.ECID.xxxxxxxxx.collect.val = y
consents.idSpecific.ECID.xxxxxxxxx.marketing.email.val = y
...
 

So I'm wondering if I'm missing something in the setup?

Anyone experience with this?

Ce sujet a été fermé aux réponses.
Meilleure réponse par mdonke

@stefanm38281801 WebSDK behaves exactly the same. It persists consent to the "ID specific". The actual websdk ingestion call is not directly creating the XDM. 

Data sent looks like this 

 

{"consent":[{"standard":"Adobe","version":"2.0","value":{"collect":{"val":"y"},"metadata":{"time":"2022-02-15T11:57:24.217Z"}}}],"query":{"identity":{"fetch":["ECID"]}},"meta":{"state":{"domain":"my.com","cookiesEnabled":true}}}

I guess that's the same for the mobile SDK.

If this assumption is correct, it would mean Adobe is doing this somewhere on the Edge/Serverside which also means we have no control over it.

My suggestion would be to create a client care ticket (and share their response 😉)

3 commentaires

adobechat
adobechat
Level 5
February 15, 2022

@stefanm38281801 Not sure what the problem is here, from your snippet, it appears that AEP is correctly reading the consent values from Mobile SDK. All consents are mapped to ECID because ECID is like Adobe's own unique ID to identify customers), so looks like its all working as intended here. 

 

Let me know if I did not catch your question correctly.

S
stefanm38281801Auteur
Level 4
February 15, 2022

Hi,

since I have the consent field group added to the profile, I was expecting these values under the main branch, and not on the idSpecific.

Furthermore I also tested with adding an idSpecific branch in the updateConsent call, e.g. on another identifier - not ECID, and that does not seem to get recorded in AEP.

    Gokul_Agiwal
    Community Advisor
    Gokul_AgiwalCommunity Advisor
    Community Advisor
    February 15, 2022

    Hi @stefanm38281801 

    Have you check this guide 

    https://github.com/adobe/xdm/blob/master/docs/reference/mixins/profile/profile-consents.schema.md

    M
    mdonkeRéponse
    Level 4
    February 15, 2022

    @stefanm38281801 WebSDK behaves exactly the same. It persists consent to the "ID specific". The actual websdk ingestion call is not directly creating the XDM. 

    Data sent looks like this 

     

    {"consent":[{"standard":"Adobe","version":"2.0","value":{"collect":{"val":"y"},"metadata":{"time":"2022-02-15T11:57:24.217Z"}}}],"query":{"identity":{"fetch":["ECID"]}},"meta":{"state":{"domain":"my.com","cookiesEnabled":true}}}

    I guess that's the same for the mobile SDK.

    If this assumption is correct, it would mean Adobe is doing this somewhere on the Edge/Serverside which also means we have no control over it.

    My suggestion would be to create a client care ticket (and share their response 😉)

    adobechat
    adobechat
    Level 5
    February 21, 2022

    @stefanm38281801 Have you selected 'Opted-in' as part of your mobile property set up?

    M
    MvvsSa
    November 23, 2023

    Yes though we send a channel level still it is attachine to the idspecific - which is ECID OOTB.

     

    Is there any way we could stitch consents at profile level example - CRM ID which is common across devices so that profile could stitch latest consents every time?

    Conditions d'utilisationAccessibility statement

    Loading footer...