Adobe Launch - steps to use AA Product String Builder Search Discovery

I'd be happy to do that.  This extension is HIGHLY configurable and can serve many needs.

Please tell me about your need.  If you can point you the site that you are using it on, that too would be very helpful.

Thanks,

-Stew

Currently, I am trying on localhost website using sandbox account.

I would like to understand the extension from start to end such as the configuration of extension and use of the extension in the tags.

For example:

I want to fire a tag on click of Add to Cart button, I will set the trigger using event - "addToCart" as per below datalayer set:

digitalData.eventData = {

ecommerce: {

product: {

sku: '123456',

name: 'White Polo Shirt',

category: 'Polo',

subcategory:'White',

quantity: 2,

}

}

};digitalData.event = 'addToCart';

})

Please help me to set the configuration based on above datalayer.

Thank you.

It is working now. Awesome!!

Thank you so much.

I have some questions related to above solution:

1)What if i change to digitalData instead of AppEventData. (showing error for me when changed).

2) what is "%event.detail.__meta.computedState%"? How it works

Data Layer Settings

Root Data Object : %event.detail.__meta.computedState%

You can use any name you like for the data layer object.  If you change, you must update the Data Layer Manager configuration so that it knows what variable to attach to.   This solution requires a data layer that is structured as a Javascript Array.  I choose not to use `digitalData` since most people seeing this name will assume that the structure follows the W3C CEDDL spec (which is not an Array).   A compromise might be to name it `digitalDataArray` which would help those who expect the data layer to start with `digitalD` then the autocomplete in the console will surface `digitalDataArray` which would let them know that something might be different than expected.

In DTM and Launch, within an event-based rule, you can get the event context by using `%event%` where ever you might otherwise use a data element.  In this case, we have the Data Layer Manager which will dispatch a Custom Event when any JSON object that contains an `event` attribute.  In Launch and DTM you can reference the detail (payload) of a Custome Event triggered rule by using `%event.detail%`.    The magic is that the Data Layer Manager adds __meta.computedState to each pushed event object.  This provides a view of the pushed event and all prior pushed events.

If you inspect AppEventData after pushing a few different events, you'll find that each event will have __meta.computedState.  Also, you'll find a top-level getter at AppEventData.computedState which shows the combination of all event objects on the array.

I'm not totally happy with this cryptic reference. I'm waiting for an enhancement (Add support for referencing event from data element library module. by Aaronius · Pull Request #83 · Adobe-Marketing-Clo… to be pushed to production that will allow us to add a special data element type which will be provided by the Data Layer Manager extension (Data Layer Computed State).  This data element will return the __meta.computedState if the context is that of a Data Layer Manager event.  It will return the top-level computedState if referenced from a context outside of a data Layer event.   I expect that we'll be able to add this in the next few weeks.

Hi Stewart,

I'm wondering if you could help me with my setup.

My transaction event is supposed to fire on a direct call.

While using this AA string builder, which variables should I populate via AA "Set Variables" Vs "SDI string builder"

In my current workspace report, I can see that the Evars are populating for purchase category/product. However, the events [currency] are showing as 0 while ecommerce variables such as product/category are empty.

In my rule for Purchase event:

Adobe Analytics - Set variables has a few evars + events only

AA string builder has my root object as: %Transaction: Root Object% [where it is a JS var called digitalData.transaction]

Product collection path is set to: .transaction.item [because the object is available in digitalData.transaction.item]

Category is setup as .transaction.item.category as Collection Item Path

Quantity as 1 as Static Text

Unit price as .transaction.item.basePrice as Collection Item Path

Question: In the AA string builder, should I again set custom events if they are already set in the AA "Set variables" action?

I'm attaching a screenshot of the transaction object.

Thanks for reading and your help.

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 question,

In the AA string builder, should I again set custom events if they are already set in the AA "Set variables" action?

No, you should ont set an event in one place - either the AA extension or the AA Product String Extension.  The only events that need to be set in the AA Product String Extension are those events that are to be set within the product string itself.

Thanks, Stewart

Here's my revised dataLayer object as an array. Should my root object be digitalData.transaction?

Also, for eVars, should I set them as AA set variables Action?

and would the product collection path be .transaction.item or just transaction.item?

Thanks a lot for your help

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 String Builder's set variables action.