issue with marketing channel attribution after upgrading to shopify checkout extensibility

Question

Howdy Adobe Community,Is anyone experiencing issue with their Marketing channel attribution with shopify checkout extensibility?We are noticing new session start in our marketing channel reporting when user proceeds to the order comfirmation page (checkout_completed). Most of our traffic are being attributed to "Direct" which is impacting our paid media campaign reporting. Digging into the data I can see Visit number =1 and Hit Depth = 1 is showing as order confirmation We have VisitorID / ECID enabled on the site for cross domain tracking and this appears to be persisting when I tested in our staging environment but it appears that a new visitorid is getting regenerated when user completes an order which is distrupting the continuity of session tracking.Any insights or assistance you can provide would be greatly appreciated as I can pin point what is going on.. as checkout extensibility is pretty much a sandbox.Any one experiencing this and how did you go about resolving.. I have reached out to shopify and still waiting on a response.

Jennifer_Dungan · Accepted Answer

When you test your flow, can you check that the use is retaining the same ECID between your main site and your Shopify? While the ECID / Visitor ID service may be turned on, if the Shopify is potentially getting third party cookies, it may not be identifying the users as the same person (so new user, new session, etc).

Now, there is an appendVisitorIDsTo plugin (https://experienceleague.adobe.com/en/docs/id-service/using/id-service-api/methods/appendvisitorid) that you can add to append the visitor information to the Shopify link to pass the information about the user to the other site..

However, I have also seen many complaints here that the other site isn't using them (which I though was supposed to be a part of this plugin... I cannot confirm since I am not using this at this time. Maybe they only installed it on one side of the implementation...)

However, that said, you can create your own logic to force the ECID cookie based on the passed ECID in the URL which should compensate if it doesn't work out of the box.

Sign up

Login with SSO

Login to the community

Login with SSO