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

KMarchewa
KMarchewa
Offline

Badges

Badges
5

Accepted Solutions

Accepted Solutions
0

Likes

Likes
3

Posts

Posts
4

Discussions

Discussions
0

Questions

Questions
4

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by KMarchewa
Customize the badges you want to showcase on your profile
Implementing Customer Attributes with Target - mbox3rdPartyID vs. customerId
Avatar
Validate 1
Level 2
KMarchewa
Level 2

Likes

3 likes

Total Posts

4 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Give Back
Ignite 1
View profile
KMarchewa
- Adobe Target
Hello, We are looking at implementing the customer attributes feature. I have reviewed the documentation both in the Target section as well as the "Experience Cloud Interface Component" docs. I understand you upload customer IDs and associated attributes to the platform and that you must send this ID to the platform on the page level after the user logs in. However, based on Adobe's docs (primarily https://experienceleague.adobe.com/docs/target/using/audiences/visitor-profiles/working-with-custo...

Views

78

Likes

0

Replies

4
Re: Launch Rule Not Consistently Firing on Link Click
Avatar
Validate 1
Level 2
KMarchewa
Level 2

Likes

3 likes

Total Posts

4 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Give Back
Ignite 1
View profile
KMarchewa
- Adobe Target
Thanks for the information. Yes, it appears that the rule is firing correctly. The only extension used is Core (v1.8.3). The action type is a Custom Code that, in part, calls "adobe.target.trackEvent" to fire a custom mbox. It works consistently if I manually disable the link navigation event (that triggers the rule) and it works part of the time without any navigation delay inserted. Thanks again.

Views

136

Like

1

Replies

1
Re: Launch Rule Not Consistently Firing on Link Click
Avatar
Validate 1
Level 2
KMarchewa
Level 2

Likes

3 likes

Total Posts

4 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Give Back
Ignite 1
View profile
KMarchewa
- Adobe Target
Thanks for the response. Unfortunately, I cannot provide a URL or logs. Sorry, I realize this will make troubleshooting difficult. How would I distinguish between the rule firing and action script? Currently, the only way I can determine whether or not it is operating correctly is using the Debugger extension and seeing if the mbox call (the action script) comes through. I assume the issue is caused by the action script failing to load (per the Dev Tools console), but why would it fail to load?T...

Views

145

Like

1

Replies

3
Launch Rule Not Consistently Firing on Link Click
Avatar
Validate 1
Level 2
KMarchewa
Level 2

Likes

3 likes

Total Posts

4 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Give Back
Ignite 1
View profile
KMarchewa
- Adobe Target
Hello,We have a a simple configured in Launch. The "trigger" event is merely Core -> Click with a simple CSS selector. There is no condition and the the "Action" portion is custom JS that fires a target mbox. However, we are having issues with this rule firing consistently. It appears to be a timing issue. When the rule fails to fire, I notice a Warning being logged to the console: "Loading failed for the with source “https://assets.adobedtm.com/xxxx/xxxx-source.min.js”. This message does not appear when the Action fires correctly (with the "firing correctly" being verified using the Adobe debugger extension.) If I manually navigate to the script that the browser warns had failed to load, it loads just fine and I can confirm that it is the custom code I wrote for the "Action" in Launch. Additionally, the source (in Firefox's Dev Tools console) of the aforementioned warning is the initial/source page (the one with the link containing the rule trigger) not the destination page. However, the Warning itself is logged while on the destination page, not the source. I am wondering if this is a common/known issues with Launch and how we might resolve. I realize there is an option to delay navigation in the "Click" event within Launch, but this is something we would like to avoid. Any tips are much appreciated.

Views

153

Like

1

Replies

5
Likes given to
Likes from