NUTRINTG Abandoned checkout service - audit and analysis

change Shopify query for abandoned checkouts from the value updated_at_min to the value created_at in abandoned checkout JSON

Basing on updated_at_min value in Shopify API query is a cause for discrepancies between Shopify and SFMC data.

Example:

This checkout was created at 12-04-2022 and updated at 21-05-2022.

It also causes a lot of errors on a journey-service related to PK duplicated values:

Response from SFMC: {"message":"The event data contains duplicate value for an existing primary key. Please correct the event data and trygain.","errorcode": 30000,"documentation":""}

Error is thrown whenever client/app updates a cart in more than 1-hour period of time (so that the service tries to send the same cart data to the same journey)

https://rb-digital.atlassian.net/browse/EP-5992

S

TO do

adjust timezones to Shopify time specific to particular timezone

Shopify stores operate in different time-zones - when Mule calculates period to use, it calculates it related to Mule server time, not Shopify server time. As a result, some carts may appear in the feed after few hours. As of now, it is very difficult to track the delay because of other errors on the service

https://rb-digital.atlassian.net/browse/EP-5707

M

DONE

remove validation for cart_token field in SFMC

There are a lot of errors on a journey service related to cart_token = null. For unknown reasons this field is required by SFMC (I don’t see any use of it on this level, because each checkout has its own ID), so retrieved checkouts with cart_token = null will throw an error on a cdp-sfmc-journey-service:

According to Shopify documentation, cart_token = null for checkouts created using an offsite payment gateway like Mercado Pago in Mexico

If there is no need to usecart_token values in the journey, then probably it would be a good idea to remove this column from SFMC (or at least make it non-obligatory value)

https://rb-digital.atlassian.net/browse/EP-5993

S

TO do

skip searching for customer profile in Epsilon for CDS integrations

Example of error log from MW:

As a result, the service throws an error, because it looks for CDS profile in wrong database (CDP): - it always calls this endpoint:/api/v1/infrastructure/scripts/CustomProfileSearch/ → search id done in CDP (Epsilon) always: pmjn-pveapi.epsilonagilityloyalty.com

Note: a very few abandoned carts for CDS integrations are selectively thrown into the journey for profiles that were created in 2019-2020. According to @Małgorzata Mucha , customer data for Health brands was temporarily migrated to CDP

https://rb-digital.atlassian.net/browse/EP-5994

M

TO do

process abandoned cart only if the user accepted marketing

In BB requirements for abandoned checkout journey we can see the condition that the user has to accept marketing to receive abandoned checkout communication:

I noticed that this criterion is misleading, because to journey flow carts whose users didn't accept marketing. Example:

This user in Shopify has indeed has a flag buyer_accepts_marketing = true for this checkout, but he didn’t agree for marketing communication at all:

Solution: to be compliant the entry criteria should be based on accepts_marketing flag in customer node (our source of truth for marketing communication) instead of buyer_accepts_marketing

https://rb-digital.atlassian.net/browse/EP-5996

S

TO do

limit query for abandoned carts in Shopify to maximum (250 carts)

there is a bug that limits query in Shopify to 2 only → it should be set up to maximum (250), checkouts.json?limit=250

FIXED

M

DONE

replace Shopify API access with custom app (instead of private app)

it is not necessary as soon as Shopify API access for our service via Private app is working correctly, but keep in mind that Shopify deprecated private apps in the begging of 2022 and we don’t know if they are going to maintain private apps in near future

C

TO do

add Hyho to abandoned checkouts data flow

it requires exposed REST endpoint for SC profile fetch as well as a decision if whether this goal is worth the development work required. Might be required for example for: https://rb-digital.atlassian.net/browse/EP-5527

https://rb-digital.atlassian.net/browse/EP-5997

C

TO do