활동이 없어 이 대화는 잠겼습니다. 새 게시물을 작성해 주세요.
활동이 없어 이 대화는 잠겼습니다. 새 게시물을 작성해 주세요.
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
해결되었습니다! 솔루션으로 이동.
조회 수
답글
좋아요 수
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.
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.
조회 수
답글
좋아요 수
조회 수
답글
좋아요 수
조회 수
Likes
답글
조회 수
Likes
답글
조회 수
Likes
답글