Page MenuHomePhabricator

Log which accepted CX Suggestions come from
Closed, ResolvedPublic


Since the CX tool now has multiple types of translation suggestions, we would like to know which accepted CX translations came from an API call to

Event Timeline

ellery raised the priority of this task from to Needs Triage.
ellery updated the task description. (Show Details)
ellery added a project: GapFinder.
ellery subscribed.
ellery renamed this task from Log which CX Suggestions come from to Log which accepted CX Suggestions come from 23 2016, 12:02 AM
ellery set Security to None.

@santhosh can you take care of this task before you execute T119939 ? This way, we will have a clean way to distinguish between campaign suggestions and suggestions from article rec API.

Change 266666 had a related patch set uploaded (by Santhosh):
Suggestions: Capture the list type for the campaign identifier

@leila, T119939: Notify translators about new personalised suggestions being available based on their recently published translation is already scheduled to go out this Thursday- 28th Jan. So we will not catch that train. Let us target the next week deployment train.

In the above patch, I added more generic eventlogging for suggestions. Every type of suggestion has a type id in CX. For personalized suggestions type is 5. So the campaign is going to be 'suggestions-type-5'. If we use this in query, we will get recommendation tool suggestion acceptance. Featured article suggestions if used, will have campaign id as 'suggestions-type-1'

Change 266666 merged by jenkins-bot:
Suggestions: Capture the list type for the campaign identifier

thanks @santhosh. Next week is fine, too. :-)

logEvent ContentTranslationCTA Object {version: 1, cta: "suggestions-type-5", action: "accept", session: "fefefefefefefefefe", contentLanguage: "en"…}