Verify a custom layout can reliably display spocs from the same campaign
Categories
(Firefox :: New Tab Page, defect, P2)
Tracking
()
People
(Reporter: mmiermans, Unassigned)
References
Details
Spocs were not being displayed consistently in the Firefox Newtab. Specifically:
-
Conventional spocs were sometimes shown instead of Apollo spocs, despite that the layout was pointing to a spoc feed with only Apollo spocs. This suggests to me a cache mismatch or that the code is falling back to a different spoc endpoint.
-
Organic recs were sometimes shown instead of Apollo spocs. Multiple people saw this, but it wasn't clear why. Maybe it was a simple case of impression capping. We weren't able to reproduce consistently. Might be worth doing some more QA around this use-case.
|
||
Comment 1•6 years ago
•
|
||
I havn't seen this be reproducible.
The campaign was a hack and making it work required a weird setup and I'm not convinced we managed to get the setup quite right and cache on the client for this is also complex, which I also think wasn't properly cleared or consistently cleared for some of the people that saw this.
I we can get solid steps to reproduce not related to a campaign we decided not to run, we should refile with those updates..
|
Reporter | |
Comment 2•6 years ago
•
|
||
All true.
I had an action item to create a bug with steps to take before we could relaunch Apollo. Given what I saw, I would like more testing to be done before I would be confident that we're able to deliver this experience reliably.
Agreed that reproducible steps would be required for a fix. I don't have time to dig into this now, so that would be part of this bug.
|
|
Reporter | |
Comment 3•6 years ago
|
||
If we can't reproduce this ourselves, maybe we should do an experiment in nightly to verify that users are getting the correct experience.
|
||
Comment 4•6 years ago
|
||
The goal of this bug to remain open, and work to test on it, was so that we're sure we can launch a sponsored collection campaign like Apollo, before having to wait until the beautiful version is launched in Fx 70 (Oct 22).
Tawanda/Wolasi, can you confirm that it's still important for us to get this working to support an experiment like this before Oct 22?
|
||
Comment 5•6 years ago
|
||
Yes, I think this is still important to get this working. It would be awkward for the brand behind a sponsored collection to see an ad for another brand in that collection.
|
|
||
Comment 6•6 years ago
|
||
Per our Cross-functional meeting today - this functionality will not be needed for 68 Sponsored Collection Experiments. We will not be able to run the Sponsored Collection experiment until 70 when we have the real component working and hooked into our new adserver. (We can't run this in 69 since this hack is based upon how we currently serve up SPOCs, and our new adserver will launch in 69).
Description
•