Closed Bug 1550115 Opened 6 years ago Closed 5 years ago

Addition of Pocket ID to SPOC endpoint requests

Categories

(Firefox :: New Tab Page, task, P1)

task

Tracking

()

RESOLVED FIXED
Firefox 69
Iteration:
69.2 - May 27 - Jun 9
Tracking Status
firefox68 --- wontfix
firefox69 --- fixed

People

(Reporter: thecount, Assigned: thecount)

References

Details

(Keywords: github-merged)

Attachments

(3 files)

With Adzerk, we need to be passing a pocket user id to the spoc request.

Blocks: 1550850
Priority: -- → P2
Priority: P2 → --
Assignee: nobody → sdowne
Attached file GitHub Pull Request

Chatted with Digi today, to double check something. Looks like we'll need to send the id over with a post and not a get. Currently the spoc request is a get, and it passes consumer_key along as a query param. If we move this over to a post, and include the pocket impression_id as a payload item, I'll also want to send consumer_key over as a payload item too.

The payload changes I'll be sending in the spoc request post are:

{
  consumer_key: "abcd",
  impression_id: "abcd",
}

Mathijs, does that make sense to you, and is there something separate you need to track for any potential changes needed to be made on the back end?

Flags: needinfo?(mathijs)

I'll make sure the Proxy Server accepts a Post request. I'll let you know when the OpenAPI spec is ready.

Flags: needinfo?(mathijs)

The priority flag is not set for this bug.
:tspurway, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(tspurway)
Flags: needinfo?(tspurway)
Priority: -- → P1
Iteration: --- → 69.2 - May 27 - Jun 9
No longer blocks: pocket-newtab

To test:

  1. Set browser.newtabpage.activity-stream.discoverystream.config to default
  2. In browser console, open up the network tab and probably clear it.
  3. in about:config, change browser.newtabpage.activity-stream.discoverystream.config to {"api_key_pref":"extensions.pocket.oAuthConsumerKey","collapsible":true,"enabled":true,"show_spocs":true,"hardcoded_layout":true,"personalized":false,"layout_endpoint":"https://getpocket.cdn.mozilla.net/v3/newtab/layout?version=1&consumer_key=$apiKey&layout_variant=basic"}
  4. In the network tab, you should now see a POST to unique-spocs and also check that requests params tab for something along these lines: {"pocket_id":"{123-123-123-123-123}","consumer_key":"123345678"}

This got merged.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Blocks: 1558441
Type: defect → task
Keywords: github-merged
Attached file GitHub Pull Request

Is this something we need to uplift to Beta or can it ride the trains?

Flags: needinfo?(sdowne)
Component: Activity Streams: Newtab → New Tab Page

Assuming that's a no then.

Flags: needinfo?(sdowne)

You are correct we don't need this uplifted, 69 is fine.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: