Assigned
Status Update
No update yet.
Comments
rl...@google.com
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
rl...@google.com
@pa...@google.com, do you have any updates on this? Customer is complaining a lot about this. Are we going to prioritize this? Or how we are goin to handle?
ch...@google.com
@yn...@google.com is this true? I think our "buy-it-again" model should respect userIds instead of visitorIds if both are present.
rl...@google.com
@yn...@google.com , can you check here as the customer stopped using "buy-it-again" because it should be worth for them just with logged users "userId".
rl...@google.com
@ch...@google.com, is there anyone that can help on this?
CX also asked if they can filter to return recommended products just based on some categories. I.e. they sell refrigerators but would no like to recommend new refrigerators as don't make sense. But in case of diapers it make sense to recommend a recurrence buy.
CX also asked if they can filter to return recommended products just based on some categories. I.e. they sell refrigerators but would no like to recommend new refrigerators as don't make sense. But in case of diapers it make sense to recommend a recurrence buy.
rl...@google.com
@yn...@google.com and @ch...@google.com , do you have any updates on this? tks
rl...@google.com
We need to understand if the model uses userIds as well and not only visitorIds. Customer want to present recommendation based on users logged in that bought something.
ch...@google.com
rl...@google.com
@ynhu, please let us know
Description
Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.
What you would like to accomplish:
Customers to be able to populate their user_ids in the visitor_id field in their events
How this might work:
Customers use user_id instead of visit_id, because if the user uses different devices (cell phone, notebook, tablet), they are afraid of not unifying the suggestions with this change.
Does Google have an explanation why they use visitor_id instead of user_id? "
Can this be considered to support cross-device?