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
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Abandoned cart program with payload (product sku's)

guillermoL
Level 4
Level 4

Hi all,

We have a program for cart abandonment running for quite a long time. It's getting the data from AA with an API call, but I'm thinking about changing this as the API call takes too long to run and I suspect there should be easier and more efficient ways to do this.

I would like to do it enriching the program with the sku's of the products abandoned, and also using customer attributes of AA (so users don't need to be logged in to identify them) Any idea apart from using Adobe Triggers? Would you recommend to switch to these?

Thanks so much

Guillermo

 

1 Accepted Solution
Darren_Bowers
Correct answer by
Community Advisor
Community Advisor

Can you elaborate on why AA with API call takes too long to run?

After setting up Launch/Analytics/Triggers/Pipelined for abandoned cart, direct AA/AC calls would be my preference as it is relatively simple to set up.

That said, Triggers does give you quite a bit of flexibility on triggering rules as well as trigger enrichment from Launch/AA. You can also have multiple JS handlers on the AC side to process different triggers, so if you want to add new Triggers, its fairly straightforward to implement new data. Triggers can be very confusing to set up correctly, especially around encryption of PII data if you intend to send that across. It also has a bunch of data concurrency issues with the data it sends across. Also, the setup documentation for Triggers is seriously lacking up to date content so can get confusing.

View solution in original post

3 Replies
Darren_Bowers
Correct answer by
Community Advisor
Community Advisor

Can you elaborate on why AA with API call takes too long to run?

After setting up Launch/Analytics/Triggers/Pipelined for abandoned cart, direct AA/AC calls would be my preference as it is relatively simple to set up.

That said, Triggers does give you quite a bit of flexibility on triggering rules as well as trigger enrichment from Launch/AA. You can also have multiple JS handlers on the AC side to process different triggers, so if you want to add new Triggers, its fairly straightforward to implement new data. Triggers can be very confusing to set up correctly, especially around encryption of PII data if you intend to send that across. It also has a bunch of data concurrency issues with the data it sends across. Also, the setup documentation for Triggers is seriously lacking up to date content so can get confusing.

View solution in original post

guillermoL
Level 4
Level 4
Hi Darren, and thanks for you help. It is my preferred method as well, but not sure why it's not working for us at the moment. In fact the AA API call is failing for sometime now and customer care can't seem to know why. We used to have many timeouts as well in the past. I'm using the Report.Queue method to get cartadditions metric and visattrcustomeridcustomerattributes, timeparting and productId dimensions. All applying the segment for carts abandoned. If you see anything strange here, please let me know! Thanks again
Darren_Bowers
Community Advisor
Community Advisor
Hi @guillermoL - I havent actually done an implementation with AA/AC direct except for POC where it seemed fairly straightforward. If you are having issues with this method and decide on Triggers, it is not a small effort to implement Triggers. There are a lot of moving parts to set up and not much in the way of clear current documentation. However, once it is set up, it seems to be fairly reliable. cheers