Status Update
Comments
pa...@google.com <pa...@google.com> #2
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.
lo...@gmail.com <lo...@gmail.com> #3
Supported pages for model deployment:
Detail page. See detail-page-view event
Add-to-cart page. See add-to-cart event
Shopping cart page. See shopping-cart-page-view event
Purchase-complete page. See purchase-complete event
rl...@google.com <rl...@google.com> #4
pa...@google.com <pa...@google.com> #5
it can be used but the goal is then to recommend items you might want to buy together with item you are looking at
if you want to show items related to the item being viewed than pdp with ctr or cvr is better.
assigning to our PM to make the final call. but i would strongly advise customer try pdp - results will be better
rl...@google.com <rl...@google.com> #6
rl...@google.com <rl...@google.com> #7
@pa...@google.com , let me know witch model are you referring pls.
pa...@google.com <pa...@google.com> #8
sorry to calrify, pdp = item view model. we call it pdp internally cause that is the page its expected to be shown on
fbt is not well suited for the case the customer is testing on
rl...@google.com <rl...@google.com> #9
@sh...@google.com , pls let us know.
rl...@google.com <rl...@google.com> #10
vi...@google.com <vi...@google.com> #11
Since we still with no answer about this issue, the customer developed an internal solution that is currently performing better them our Recommendations.
Now the customer is moving out from our solution and we are with revenue impact
Raising this case to P1
Thanks
sh...@google.com <sh...@google.com> #12
FBT is mostly used in the check out/cart placement. For PDP they should be using OYML. Most importantly, PDP is personalized while FBT is not
rl...@google.com <rl...@google.com> #13
Notice that many other TVs are being recommended to buy together. There is also an air fryer being recommended.
PDP 0f TV 50 inches:
Whats being recommended with FBT model:
li...@google.com <li...@google.com> #14
Anyone can share the project number?
rl...@google.com <rl...@google.com> #15
PN: 1086652394397
li...@google.com <li...@google.com> #16
Hi, this project has 2 FBT models: frequently_frequently_1697420189287
and frequently_frequently_1698697500946
. Which is for this bug? Thanks!
rl...@google.com <rl...@google.com> #17
Consider for the bug this one: frequently_frequently_1697420189287
rl...@google.com <rl...@google.com> #18
PDP acessed - Sylvanian families primeira casa
FBT returning pliers as a recommendation
rl...@google.com <rl...@google.com> #19
rl...@google.com <rl...@google.com> #20
rl...@google.com <rl...@google.com> #21
Amazon uses the FBT in the PDP as well but their behavior is as expected as you can see from the following print screen. As you can see all recommended products by FBT make sense.
rl...@google.com <rl...@google.com> #22
hi @li...@google.com , how are you? Please let me know if you have any comments on this bug? were you able to identify improvements?
Thanks
li...@google.com <li...@google.com>
di...@google.com <di...@google.com>
di...@google.com <di...@google.com> #23
Hi rlombardi@, investigated further and found the root cause for this issue.
The FBT model essentially looks at the user events containing items that are viewed or bought together in the same session. This is the reason behind the recommendations displayed in the two issues that the customer pointed out.
So in the case of the Sylvanian families primeira casa toy item, we found one event where a user actually purchased the pliers along with it:
And similarly for the case of the TV, there were actually user evens where other TVs were bought together:
rl...@google.com <rl...@google.com> #24
Hi @di...@google.com , I understand that we are basing in products bought together. But we don't believe that this is happening frequently. So for example in the first case it was probably the only one the case that the person bought the toy together with the pliers. Also if we think about people buying TV it's uncommon frequently buying more than one TV in the same session. So We need to be based on purchases that are really see some frequency of buying together.
li...@google.com <li...@google.com> #25
Hi @rlombardi, yes. This weird purchase behaviors does not happen frequently. We had an internal discussion for improving the FBT quality on this point, and will have new results soon later. Thanks!
rl...@google.com <rl...@google.com> #26
Hi
li...@google.com <li...@google.com> #27
Hi
rl...@google.com <rl...@google.com> #28
Hi
li...@google.com <li...@google.com> #29
Hi @rl...@google.com, For this product, Google FBT's recommendation is this panel?
rl...@google.com <rl...@google.com> #30
for me it's not showing this carrousel. But this should be the Google FBT.
rl...@google.com <rl...@google.com> #31
@li...@google.com , please let me know if we made progress? Thanks
rl...@google.com <rl...@google.com> #32
@shraygulati, the next A/B test is programmed to start 27th January. We need to have FBT model ready until there.
rl...@google.com <rl...@google.com> #33
@li...@google.com , pls let us know if there is any evolution on the FBT model. Thanks
li...@google.com <li...@google.com> #34
Thanks for the confirm. Will update this bug once we can confirm the model improvement.
cy...@google.com <cy...@google.com> #35
@li...@google.com @di...@google.com Do you have any update on this? The customer'll start the next A/B test on 27th January
li...@google.com <li...@google.com> #36
Yes, we did internal testing for the customer's FBT model and saw the improvements for the problematic queries. Will apply the improvement on the production model. @di...@google.com can comment the current status as well.
cy...@google.com <cy...@google.com> #37
@li...@google.com @di...@google.com The customer will start the A/B next Monday (27th January). Is the model ready to start the test?
li...@google.com <li...@google.com> #38
Hi, we know the next Monday for the A/B testing. We are still tune the FBT model and will give the updates by the end of this week.
di...@google.com <di...@google.com> #39
Hi
Description
Frequently Bought Together model is being used by the customer in PDP pages and is returning results not correlated to the product being considered by the client to be purchased. The customer is complaining about the results.
What you expected to happen:
To recommend products related to the one that the customer is considering to buy or purchased.
Steps to reproduce:
access
see screenshot: