Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Nope, but it's possible the user store that happens after VM2 integration fires could be cause VM2 user being stored with previous values instead of the new values. Testing on frontend will confirm if it's working or not.When unsubscribing from the backend, any special instructions? I noticed a delete from the subscription.. Should we use that?
Please Log in or Create an account to join the conversation.