Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

stefanm38281801
stefanm38281801
Online

Badges

Badges
21

Accepted Solutions

Accepted Solutions
2

Likes Received

Likes Received
44

Posts

Posts
58

Discussions

Discussions
17

Questions

Questions
41

Ideas

Ideas
9

Blog Posts

Blog Posts
0
Top badges earned by stefanm38281801
Customize the badges you want to showcase on your profile
Re: Data element "default value" in Mobile Core Modify Data rule is not interpreted - Adobe Experience Platform Data Collection 26-09-2022
Hi Charles, doesn't make any difference. default value is not picked up. Stefan

Views

6

Likes

0

Replies

0
Re: Profile merging on ECID - what about sharing devices? - Adobe Experience Platform 19-09-2022
Switching off ECID as an identity has other consequences according to Adobe technical staff, since ECID is used as the main identifier for most of the OOTB Adobe solutions. You might impact their proper working.

Views

48

Likes

0

Replies

0
Profile merging on ECID - what about sharing devices? - Adobe Experience Platform 14-09-2022
Hi, bringing this topic back in attention. Mobile SDK (and Web SDK) are highly relying on the ECID as the primary identity. As long as a device (or multiple devices) are used by the same user, there's no real issue. Problems start to raise when a device - a desktop PC, a tablet - is shared along users, each using their own credentials for login. From the "user" point of view, the user login can be seen as "personal" (i.e. unique for a user). But if the ECID for the device remains, the profiles w...

Views

103

Like

1

Replies

3
Data element "default value" in Mobile Core Modify Data rule is not interpreted - Adobe Experience Platform Data Collection 12-09-2022
Hi, I'm capturing a CollectPii call from the (AEP) Mobile SDK in Experience Platform Data Collection. In the rule I use a Modify Data action to transform the context data from the call into an XDM for AEP. In the input context some fields may be missing, so I did set up default values for those data elements that might be missing. However in the generated XDM schema, the default values are not taken into account:e.g. snippet from the modify data JSON:"xdm": { "person": { "name": { "lastName": "{...

Views

68

Likes

0

Replies

2
Re: Consent passing from Mobile Core SDK to AEP - Adobe Experience Platform 15-02-2022
Even if I post something like this: ["collect": ["val": "y"],"marketing": ["preferred": "email","any":["val": "y"],"email":["val": "y"],"push":["val": "y"]],"idSpecific":["Email":["my_email@mycompany.com":["marketing":["email":["val":"y"]]]]]] I can see in Griffon, on the streaming validation that the idSpecific value on Email is not passed to AEP.

Views

391

Likes

0

Replies

0
Re: Consent passing from Mobile Core SDK to AEP - Adobe Experience Platform 15-02-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.

Views

407

Likes

0

Replies

1
Consent passing from Mobile Core SDK to AEP - Adobe Experience Platform 14-02-2022
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.idSpecif...

Views

458

Likes

0

Replies

6
Re: Delivery weight arbitration in prepared deliveries - Adobe Campaign 06-05-2021
Hi Cedric, that's just the point of the test. I cannot set the Prepare state in the form, because the delivery logs are created and the arbitration pressure rule will be finalized. The delivery will not count for re-evaluation anymore (in order to achieve re-evaluation the delivery should be in target ready state: this behavior is nicely explained in this very useful webinar on pressure rules: https://helpx.adobe.com/customer-care-office-hours/campaign/campaign-optimization-using-pressure-rules....

Views

546

Likes

0

Replies

0
Re: Delivery weight arbitration in prepared deliveries - Adobe Campaign 05-05-2021
Hi Cedric, in the template used for the preparation, the Approval mode was set to "Automatic", but it seems that in the actual generated email the Approval mode was reset to Manual.So now I do enforce in the delivery script also the automatic mode, and just started a new test...delivery.scheduling.validationMode = "auto"this results in the actual delivery that the mode is correctly set. Although the interface is still asking for the confirm...Just rerunning the test, and wait till tomorrow for t...

Views

579

Likes

0

Replies

0
Delivery weight arbitration in prepared deliveries - Adobe Campaign 05-05-2021
Hi,I'm testing delivery weight arbitration in a Campaign workflow with prepared deliveries: Contact date and weight are set in the "script" part of the delivery:delivery.scheduling.contactDate = "2021-05-05 09:00:00"delivery.scheduling.extracted = "2021-05-05 07:00:00"delivery.forecast.weight = "20" // each of the 3 deliveries get a different weight (20, 30 and 40). Contact date and extraction date are +12h and the deliveries are left on "Estimate Target" in order to have the re-evaluation being...

Views

621

Likes

0

Replies

6