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

pradeep_nextrow
pradeep_nextrow
Offline

Badges

Badges
27

Accepted Solutions

Accepted Solutions
17

Likes Received

Likes Received
40

Posts

Posts
63

Discussions

Discussions
3

Questions

Questions
60

Ideas

Ideas
2

Blog Posts

Blog Posts
1
Top badges earned by pradeep_nextrow
Customize the badges you want to showcase on your profile
Re: OOTB XDM variables are not working as conditions in Processing Rules - Adobe Experience Platform Data Collection 21-01-2022
Thanks! Just did that too and surprised that I cannot use many XDM variables in processing rules. The documentations say I can map the value coming in XDM to eVars and props using processing rules. Is this understanding right.

Views

619

Likes

0

Replies

4
Re: OOTB XDM variables are not working as conditions in Processing Rules - Adobe Experience Platform Data Collection 21-01-2022
@dwright I used real-time reports for validation. Let me shoot a quick video and post it here. I setup a processing rule "If a.x.implementationDetails.version exists, then populate prop5 to some value". Then, monitored the result in Real-time reports. This setup was not populating any numbers. Then if I remove the condition, real-time reports populate data for prop5. I replaced the condition with "web.webpageDetails.name", then similar problem occurred (no data in real-time reports).The primary ...

Views

648

Likes

0

Replies

0
Re: OOTB XDM variables are not working as conditions in Processing Rules - Adobe Experience Platform Data Collection 21-01-2022
Yes, I am using "a.x". In fact the eventtype was working for me as well. But this is not passed in all my alloy.js calls. Since I want the processing rules to fire only for alloy.js calls. So wanted to use "a.x.implementationDetails.version". But the condition is not met. Tried with "a.x.web.webPageDetails.name" that was not met as well.

Views

652

Likes

0

Replies

6
OOTB XDM variables are not working as conditions in Processing Rules - Adobe Experience Platform Data Collection 20-01-2022
Hello Folks! I am facing a weird issue. Have implemented Web SDK to capture AA data. I am using processing rules to populate many eVars and props. But to my surprise none of processing rules were firing and all my custom variables had no data. I found that an overall condition ("implementationDetails.version" which is an OOTB XDM value) for the processing rules, did not meet and hence no rules fired. I tried with "web.webPageDetails.name", same result. I change the processing rule condition to a...

Views

681

Likes

0

Replies

16
Re: Tracking code set up by using WEB SDK or Adobe Launch Server - Adobe Experience Platform Data Collection 20-01-2022
Sorry, @Luca_Lattarini . I missed your follow-up question. Yes, the same approach can be used for GA as well. In GA, all the google related campaigns are reported automatically (using the utm parameters). But not the other campaigns (example FB or other social). Best solution would be, you can define the campaign parameters for all the sources and implement in your landing pages. In web SDK, you can capture this marketing tracking code in the "marketing.trackingCode" variable. In GA you can capt...

Views

113

Like

1

Replies

0
Re: AEP Web SDK Migration - Query on Audience Manager Set Customer ID - Adobe Audience Manager 23-12-2021
@Ankita_Sodhi I have a follow-up query. In AAM, we used to ID sync against a specific data source or integration code. How would we do that in AEP Web SDK?

Views

674

Likes

0

Replies

3
Re: Tracking code set up by using WEB SDK or Adobe Launch Server - Adobe Experience Platform Data Collection 22-12-2021
@Luca_Lattarini Are you talking about the campaign tracking codes? (used to be captured in s.campaign variable in AA). If yes, then this is tracked OOTB using Web SDK. Just capture your campaign tracking code (from query strings) and set it as "marketing.trackingCode" XDM variable in your Web SDK calls (using Adobe Launch Rule and Data Element) and you are done. You need to add the right mixin (Field Group) - "Campaign Marketing Details" to your XDM web events schema for using it in AEP (for AA ...

Views

195

Like

1

Replies

2
Re: Does Adobe Launch Server Side support OAuth2.0 authentication flow towards external system? - Adobe Experience Platform Data Collection 22-12-2021
The authentication in Adobe Launch Server-side (a.k.a Event Forwarding) is called as "Secrets" and OAuth2.0 is supported method. It can be configured in the UI and using API as well. API would be a preferred way for most S2S implementations. You can read more about it here: https://experienceleague.adobe.com/docs/experience-platform/tags/event-forwarding/secrets.html?lang=en

Views

151

Likes

0

Replies

0
Re: How do I trigger analytics for browse abandonment? - Adobe Experience Platform Data Collection 21-12-2021
@yuhuisg - I think @keeTee is using "Triggers" (experiencecloud.adobe.com/triggers.html) and this is not in Launch or AA Segments. Can you please setup like this and check once:I think one of the reason would be your "cart additions" event is not programmed right or prodviews not programmed right in the implementation. But if everything is right, it should fire a trigger. You can also test if your triggers are working by setting up a simple "Action" trigger.PS: I think this question needs to be ...

Views

306

Likes

0

Replies

1
Re: "CORE" namespace in XDM identityMap - Adobe Experience Platform Data Collection 21-12-2021
@jgrubbs "CORE" is the namespace for AAM identifier (I think this is the UUID and that is the reason for the mix up). The konductor (Edge) sets the ECID server side and also ECID lives (I think in an encrypted format) in the konductor core identity cookie. In every request to Edge, you will see a "query" under XDM, where alloy goes and asks for the ECID. You can actually see if this would be resulting in a successful ECID in the response ("Preview" tab of the Chrome debugger). Here you should ge...

Views

228

Like

1

Replies

1