Abandoned cart program with payload (product sku's) | Community
Skip to main content
guillermoL
guillermoL
Level 4
March 18, 2020
Solved

Abandoned cart program with payload (product sku's)

  • March 18, 2020
  • 1 reply
  • 4115 views

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

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Darren_Bowers

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.

1 reply

Darren_Bowers
Darren_BowersAccepted solution
Level 9
March 18, 2020

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.

    guillermoL
    guillermoLAuthor
    Level 4
    March 19, 2020
    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
    Terms & ConditionsAccessibility statement

    Loading footer...