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

dwright
dwright
Offline

Badges

Badges
27

Accepted Solutions

Accepted Solutions
33

Likes Received

Likes Received
46

Posts

Posts
117

Discussions

Discussions
32

Questions

Questions
85

Ideas

Ideas
6

Blog Posts

Blog Posts
1
Top badges earned by dwright
Customize the badges you want to showcase on your profile
Re: Flicker Management on Adobe Target with AEP Web SDK - Adobe Experience Platform 11-03-2022
Just wanted to say that the approach to flicker management is the same with Web SDK, but the prehiding snippet itself is different, so that would need to be updated as part of your migration from at.js to Web SDK. It's discussed in this Web SDK tutorial: https://experienceleague.adobe.com/docs/platform-learn/implement-web-sdk/applications-setup/setup-target.html

Views

204

Like

1

Replies

0
Tutorial Discussion: Implement Adobe Experience Cloud in mobile apps - Adobe Experience Platform Data Collection 09-03-2022
Use this thread to ask any questions related to the Implement Adobe Experience Cloud in mobile apps tutorial on Experience League. Experts are monitoring this thread to ensure your questions are answered.

Views

11.6K

Likes

0

Replies

7
Re: Adobe Target Display call only firing on first page view with Adobe Web SDK - Adobe Experience Platform 04-02-2022
Hi @kristinae599482 ,So the main thing is you need to "remember" that they have been to the page the first time they go there. Using a profile script (or profile parameter) is Target's main way of "remembering" something happened. You could use a data element in tags/Launch to do this, but you would need to persist it using the "Storage Duration" setting of the data element to something like "visitor" so it is persisted across multiple pages. My recommendation is to use a profile script in Targe...

Views

271

Likes

3

Replies

0
Re: Adobe Target Display call only firing on first page view with Adobe Web SDK - Adobe Experience Platform 03-02-2022
Hi @kristinae599482 ,Is your goal to do something like this?Visitor loads a page.If this is the first time they load the page, they do not qualify for the test. You want Target to remember they have seen the page.If this is the second or more time they have loaded the page, they now qualify for the test and should get a test experience.Am I understanding your scenario correctly? Are you using a profile script to "remember they have seen the page"? Daniel

Views

283

Like

1

Replies

2
Re: 'Google Ads' BETA Source Connector in AEP - Adobe Experience Platform 27-01-2022
@PratheepArunRaj , I haven't used this source connector personally, but it does seem odd that the tables are not available and you can't proceed. I see the connector is in BETA, so perhaps all of the kinks haven't been worked out yet. I would suggest that you open a support ticket so that client care and engineering can help look into what you are experiencing in your account.

Views

371

Like

1

Replies

0
Re: XDM Field Groups for "Media Interaction Details" not consistent in documentaiton - Adobe Experience Platform 26-01-2022
@pradeep_nextrow , I see your point about the fields in the docs not aligning with the fields in the media object. Here is my advice:If this is just a docs question, a good way to report it is to use the "Log an issue" icon in the right sidebar of the page to open a github issue which will go right to the docs team.If data is not landing in your account as per the docs, please open a support ticket so customer care and triage this with engineering and fix it.That being said, I notified a few peo...

Views

249

Likes

0

Replies

0
Re: OOTB XDM variables are not working as conditions in Processing Rules - Adobe Experience Platform Data Collection 26-01-2022
@pradeep_nextrow , what I heard is that the implementationDetails.version is automated mapped to Code Version. I've asked for that to be added to our documentation of the auto-mapped variables. Also, the auto-mapped variables (with the exception of ECID and product details) are not available in processing rules to manage payload sizes. If you feel like implementationDetails.version (or any of these other auto-mapped variables) should be available in processing rules, please be sure to put that i...

Views

572

Likes

0

Replies

0
Re: OOTB XDM variables are not working as conditions in Processing Rules - Adobe Experience Platform Data Collection 21-01-2022
@pradeep_nextrow and @yuhuisg ,Triple-confirmed! I see implementationDetails in my interact call, but not in the call sent from Edge to Analytics. I'm asking around, but can you open a client care ticket for this @pradeep_nextrow ?

Views

608

Likes

0

Replies

1
Re: OOTB XDM variables are not working as conditions in Processing Rules - Adobe Experience Platform Data Collection 21-01-2022
That seems odd. "implementationDetails.name" is just the version of the alloy.js library, so that should always be present. How did you conclude that the condition "did not meet"? What debugging process were you using to come to that conclusion? Do you see that XDM value passed in the page call?

Views

666

Like

1

Replies

3
Re: Repeating Page Views were send in SPA with the Data Element "Page Path" Change by Adobe Launch - Adobe Experience Platform 21-01-2022
Hi @DebbyNPL , it sounds like you are getting calls from both the "app load" and the "view change" when your intention is to only make calls on the "view change". Does your data element change twice on the first load of the app? Or is there another rule which is firing on on the page load (via "Library loaded - Page Bottom", "DOM Loaded", or "Window Loaded")?

Views

267

Likes

2

Replies

1