since ‎20-07-2017
‎20-10-2020
StewSchilling
MVP
Re: Access Processing Rules via API StewSchilling - Adobe Analytics
Wow. This is really distressing. The introduction of AEP Web SDK makes this a really hot issue since we will have to send everything via XDM key value pairs which become context variables on the beacon that gets sent to the AA collection server. Processing rules suddenly become super-important for the purpose of mapping from these (xdm) context variables into AA events, props, and evars. I have to assume that if the functionality was once in the 1.4 API but now gone from the 1.4 and 2.x API's th...
86
Views
0
Likes
0
Comments
Re: Accessing non standard "Additional Parameters" in Launch Direct Call Rule StewSchilling - Adobe Experience Platform Launch
Here is a work-around. The idea here is to automatically map every key in the event.detail object to a data element so that you can reference each key in the UI. This is done using a Core > Custom Code Condition with the following javascript:In any action (or any subsequent condition) you can then reference the key using %palyload:foo-bar%The period character is not allowed in data element names, so it had to be replaced...Brackets are allowed, so you _could_ change this code to use payload[foo-...
1843
Views
2
Likes
0
Answers
Re: Accessing non standard "Additional Parameters" in Launch Direct Call Rule StewSchilling - Adobe Experience Platform Launch
If it were possible to get at this data from Core > Custom Code data elements would that solve the problem? You'd have to create a data element for each context variable.
1840
Views
0
Likes
0
Answers
Re: Accessing non standard "Additional Parameters" in Launch Direct Call Rule StewSchilling - Adobe Experience Platform Launch
I don't think that bracket notation is supported at all within a %% expression in the UI. I think that you are stuck unless you transform the object before passing it (or get away from the practice of using dot notation in key names). To be honest, my first reaction when you said that you had object keys like "foo.bar" was bewilderment.In my mind, I had to ask, "why would anyone do such a thing?"
1792
Views
0
Likes
0
Answers
Re: Accessing non standard "Additional Parameters" in Launch Direct Call Rule StewSchilling - Adobe Experience Platform Launch
Did you try %event.detail.foo.bar% ?
1821
Views
0
Likes
0
Answers
Re: Clearvars() on SPA StewSchilling - Adobe Experience Platform Launch
On the client side, the main object provided by the Adobe Analytics JS library (AppMeasurement.js) is _typically_ "s". People refer to this as the "s Object" or just as "s". It may also be referred to as the "tracker" object. Technically, it may have a different name and it may or may not be exposed at global scope. Anyway, I'm going to just call it "s". "s" is created when the Adobe Analytics library loads (and when a call to s_gi is made. BTW, s_gi is the function that gets an instance of the ...
3858
Views
5
Likes
1
Answers
Re: To Lower Case Values StewSchilling - Adobe Analytics
SHIRINL26​ This should do the trick:
2452
Views
5
Likes
0
Answers
Re: Angulartics2 with Launch Provider StewSchilling - Adobe Experience Platform Launch
The way I'd approach this using Data Layer Manager is :1) Create an AA PostTrackCallback that clears vars after each beacon. (Forget about using the AA extension's Clear Vars action). 2) Have the angular app push an event when a view change is starting. Use that event to trigger a rule that resets the data layer 3) Option1 - Trigger rules from each of the events that you care about which set AA variables but do not send a beacon. Trigger a rule from the last of these events that sets AA variable...
3413
Views
2
Likes
0
Answers
Re: Angulartics2 with Launch Provider StewSchilling - Adobe Experience Platform Launch
Can I assist you with the Data Layer Manager? 
3421
Views
0
Likes
0
Answers
Re: Adobe Launch - steps to use AA Product String Builder Search Discovery StewSchilling - Adobe Experience Platform Launch
Your root object should be a data element that returns the whole `window.digitalData` object.the product collection path should be (the string) "transaction.item".Anything that you want to set on the AA beacon outside of the product string should be set using the AA set variables action. In your case this would include setting the "purchase" event, setting "s.purchaseID", "s.transactionID", etc.Any product string (merch syntax) evars or product string custom events are set using the AA Product S...
3130
Views
4
Likes
0
Answers
Re: Adobe Launch - steps to use AA Product String Builder Search Discovery StewSchilling - Adobe Experience Platform Launch
There are a few challenges here. 1) AA Product String Build needs the product collection to be an array.2) AA Product String Builder needs the quantity to be specified within each item of the product collection.You have this: But you need this: Assuming that you will not be able to change the actual data layer, I suggest doing a transformation in the data element that provides the Root Data Object. Just create a Core > Custom Code data element as follows: Then configure the rule action as : Your...
3017
Views
1
Like
0
Answers
Allow custom metadata to be persisted on Launch Resources via API StewSchilling - Adobe Experience Platform Launch
As a Launch API user, I would love to have place to attach my own metadata to a Launch resource when creating/updating it. As an example, I might want to create a data element by posting to the standard endpoint, POST /properties/:property_id/data_elementsIn addition to the normal, required parameters, I'd like to have a place to store my own metadata (perhaps a stringified JSON object up to some sane size limit). This would allow for any number of expanded uses. Thanks for the consideration. -S...
1583
Views
2
Likes
1
Comments
Re: Add GUI element to add values to Analytics events StewSchilling - Adobe Experience Platform Launch
Nicely done! 
16777
Views
0
Likes
0
Comments
Re: Adobe Analytics Product String extension not working StewSchilling - Adobe Experience Platform Launch
Glad I could help. If you are reworking a data layer, you might also benefit from the Data Layer Manager extension that we created (Lots of exciting new features coming on this one). Feel free to reach out directly if you need help with either extension.-Stew
1771
Views
0
Likes
0
Answers
Re: Adobe Analytics Product String extension not working StewSchilling - Adobe Experience Platform Launch
My best advice is to check out the "AA Product String Builder" extension from Search Discovery. I took the liberty of putting an example together for you using the existing window.pageData object on your live site. Here's the recipe: 1) Start with (at a minimum) these extensions.2) Create a Data Element that points to your Data Layer object. I pointed to window.pageData in this example.Here's the object that I'm pointing to: 3) Create a "Cart Viewed" rule. I used a direct-call event for this, bu...
2696
Views
1
Like
2
Answers
Re: Adobe Launch Extension Creation. StewSchilling - Adobe Experience Platform Launch
My first advice is to get on the Launch Developers SlackBeyond that, be sure that your Adobe.io Integration has the Extension Developer role. Based on the error that you are reporting, you have some form of authorization (indicated by the first message). I think that you might not have the authority to upload.
2983
Views
0
Likes
0
Answers
Re: Add GUI element to add values to Analytics events StewSchilling - Adobe Experience Platform Launch
I would agree that it is desirable to omit an event that has no value. With the exception of the built-in events (prodView, scOpen, scView, scAdd, etc), I'm pretty sure that setting to 0 is the same as not setting (even with counter events). It was not this way historically, but I'm pretty sure that it works that way now. As a tidbit, you can now increment counter events by more than one. I've also seen people using negative event values although I don't I'm ready for that leap yet!
16777
Views
0
Likes
0
Comments
Re: Add GUI element to add values to Analytics events StewSchilling - Adobe Experience Platform Launch
It looks like this idea has been implemented. Awesome! jantzen.belliston-Adobe Can you update the status of it? gflareHave you tested this to see if it solved the set/no set issue?
16777
Views
0
Likes
0
Comments
Re: AA Beacon has two network requests- 302 followed by 200 StewSchilling - Adobe Analytics
Thank you! I would assume that this does not happen when using ECID service. Right?
3172
Views
0
Likes
1
Answers
AA Beacon has two network requests- 302 followed by 200 StewSchilling - Adobe Analytics
Can anyone explain what is happening here? I see this occasionally. It tends to be at the beginning of a session. I originally thought that I had some issue in my code that was causing two beacons to be sent. I finally caught it in the network tab this AM. I now think that this is normal behavior, but I don't fully understand the "Why" of it. Any help?
3642
Views
0
Likes
3
Answers and Comments
Re: Angulartics2 with Launch Provider StewSchilling - Adobe Experience Platform Launch
"The key here is to construct and attach the data layer before Angulartics fires pageTrack or eventTrack event." This is one of the things that we set out to solve with the Data Layer Manager - By using a native JS Array at window scope, any application can push a data layer event regardless of whether Launch or the DLM has initialized. When DLM initializes, it inspects the array and processes any previously pushed events. In the case of the Angulartics pageTrack and eventTrack events, if they s...
3433
Views
1
Like
0
Answers
Re: Unknown launch/dtm libraries under head tag StewSchilling - Adobe Experience Platform Launch
AppMeasurement.min.js is the Adobe Analytics library (loaded by the AA extension). Others that may show in the head will most likely be snippets loaded by other extensions or (page top) Library Load rules. If you have custom code actions on your rules, the code that you enter for those custom code snippets will be loaded when needed. If needed on demand (e.g. by a rule triggered on a click event), those snippets will show up on the bottom of the DOM. One thing to note - If you are using the asyn...
2052
Views
0
Likes
0
Answers
Re: Unknown launch/dtm libraries under head tag StewSchilling - Adobe Experience Platform Launch
These are secondary files that are pulled in by Launch as it initializes. If you are looking in the Elements tab of the Chrome dev tools, you are seeing the live DOM. As changes are made in the application, you see those changes reflected here. If you want to see the HTML of the page as it was delivered (before any DOM manipulations, use View Page Source
2014
Views
0
Likes
0
Answers
Re: Launch APIs - list audit events StewSchilling - Adobe Experience Platform Launch
You bet. Just to be clear, try it with this endpoint. https://mc-api-activation-reactor.adobe.io/audit_eventsHere is what your curl command should look like (note: I have modified the bearer token and clientID, so this exact command will not actually work).
2152
Views
0
Likes
0
Answers
Re: Launch APIs - list audit events StewSchilling - Adobe Experience Platform Launch
Does your API endpoint include "-integration"If so, try taking that out.
2192
Views
0
Likes
0
Answers
Group Data Elements by Expected Type of Returned Value StewSchilling - Adobe Experience Platform Launch
In the creation of the Data Layer Manager, SDI Tooklit, and AA Product String extensions, I have created or worked with various new data elements that are expected to have return types other than simple string values.One example is the Malformed URL Error data element of the SDI Toolkit which can return an Array of Strings.Another is the Data Layer Manager's Contextual Data Element which can return a JSON object, an Array of JSON objects, boolean, number, or string depending on how it is configu...
1590
Views
3
Likes
0
Comments
Re: Launch APIs - list audit events StewSchilling - Adobe Experience Platform Launch
Hi Matt, There are two things missing in your API request. [TOKEN] and [KEY].Essentially, in order to make API requests, you need to create an Integration (service account) in Adobe I/O.That account has an API Key (aka client ID) which you would use where it says [KEY].You will also need to generate a "bearer token" via JWT exchange and put that value in [TOKEN].There is an instructional doc here: Launch Documentation I hope this gets you going!-Stew
2167
Views
0
Likes
0
Answers
Re: Angulartics2 with Launch Provider StewSchilling - Adobe Experience Platform Launch
Please take a look at the Data Layer Manager and AA Product String Builder extensions from Search Discovery. The Data Layer Manager provides a standard way for applications to trigger Launch rules and to access the information in the data layer. It also cleanly handles the issues around asynchronous Launch load by de-queuing any events pushed prior to the Launch init.I have an update coming very soon that will provide:1) A new event type (Data Layer Push)2) A new data element type (Context Aware...
3422
Views
3
Likes
0
Answers
Re: Increasing Rendered Rules Per Page StewSchilling - Adobe Experience Platform Launch
Not presently, but you can add your vote to this idea on the same topic: Allow for more than 10 rules/DEs listed at one time -Stew
1778
Views
0
Likes
0
Answers
Re: Link DTM embed code to Launch StewSchilling - Adobe Experience Platform Launch
The linked embed code will load one of two things: 1) The DTM Production library -or-2) The Launch Production libraryWHICHEVER ONE WAS MOST RECENTLY PUBLISHED.This means that there is no impact on your production tracking until you push the Launch build into production.It also means that if you should need to revert back to DTM, you can just force a publish there. Does that help? -Stew
2164
Views
0
Likes
0
Answers