Expand my Community achievements bar.

Help shape the future of AI assistance by participating in this quick card sorting activity. Your input will help create a more effective system that better serves your needs and those of your colleagues.
SOLVED

Help with Product String Launch Extension

Avatar

Level 5

Hi Masters!

I'm trying to figure out how the Product String Launch Extension works.

I'm tagging a checkout page, and I would like to set the product ids (array) using this extension. The documentation is not very clear (Use bracket notation to denote any object in the variable that is an array ( i.e. myDataLayer.thisIsAnArray[n].productID))

To store the product ids, I tried with a Data Element and with a custom JS with _satellite.setVar(). But it doesn't work. Is there any example out there?

For example, my specific questions about the documentation example (myDataLayer.thisIsAnArray[n].productID):

  • Is myDataLayer a Launch Data Element?
  • Should I include the '%' symbols in the configuration field, inside the Product String Launch Extension, like any other field in Launch?
  • If I set a Data Element, let's say 'CheckoutPage_SKUs' with an array of product ids, should it work if I set '%CheckoutPage_SKUs%'? Or '%CheckoutPage_SKUs[]%'? Or '%CheckoutPage_SKUs%[]'. (These doesn't work for me)

Any help would be appreciated!

Kind regards,

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

The best advice that I can give is to use the AA Product String Builder extension from Search Discovery instead. 

It has inline documentation and can build any product string from simple to complex.

Screen Shot 2018-11-29 at 8.01.07 AM.png

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

The best advice that I can give is to use the AA Product String Builder extension from Search Discovery instead. 

It has inline documentation and can build any product string from simple to complex.

Screen Shot 2018-11-29 at 8.01.07 AM.png

Avatar

Level 5

Thank you very much stewarts16448458!

At first sight, it has a lot more documentation than the original extension (which it's not difficult). It seems a good piece of code. I'll give it a try.

Kind regards,