We are uploading the offline data into experience cloud using CRS. The website is on at.js 2.x , we have passed mbox3rdPartyId through adobe.target.trackEvent through Adobe Launch Rule "PQR".
Target is implemented on website through launch only and there is separate rule "ABC" for this.
"PQR" is firing post "ABC" and I can see call is firing in network tab for both.
I can see mbox3rdPartyId also present under Id.
So wanted to check with you if this setup would not cause any issue and I can target the loggedIn users since I have the thirdPartyId in the param.
@LordOfTheRings I see what you are doing here but I dont believe there is enough documentation on how this will work and how reliable it can be long term. The function "trackEvent" is meant for reporting so if Adobe scraps it and uses sendNotification instead you will need to pivot. It's a big "if" but perhaps theres another more effective way?
Have you thought of disabling auto global mbox when user authenticates and instead fire it using getOffers/applyOffers when you do have the mbox3rdPartyId?