I think that works as long as @Isaac and @bmansurov can integrate it into the tool.

Change 575974 had a related patch set uploaded (by KartikMistry; owner: KartikMistry):
[operations/mediawiki-config@master] Add URL campaign for Wiki for WikiGap

https://gerrit.wikimedia.org/r/575974

In T246335#5926942, @Astinson wrote:

I think that works as long as @Isaac and @bmansurov can integrate it into the tool.

Ok. We'll proceed with the "wikigap" campaign. If a change of name were required, please let us know.

If it's just a question of name standards, I'd ask that you allow this exception. Changing the name at this point would require providing new URLs to the organizers, which would likely cause confusion, and updates to the code (as there is WikiGap-specific filtering that the tools does based on the campaign parameter). Apologies that we were unaware when we chose this particular campaign name. If you can map WikiGapFinder to wikigap on your end, that obviously is completely fine with us.

In T246335#5932801, @Isaac wrote:

If it's just a question of name standards, I'd ask that you allow this exception. Changing the name at this point would require providing new URLs to the organizers, which would likely cause confusion, and updates to the code (as there is WikiGap-specific filtering that the tools does based on the campaign parameter). Apologies that we were unaware when we chose this particular campaign name. If you can map WikiGapFinder to wikigap on your end, that obviously is completely fine with us.

I think it is better to keep the same campaign identifier through the whole chain. Let's use "WikiGapFinder" then.

Thanks @Pginer-WMF !

Awesome all -- thanks for this -- really a cool example of collaboration on a targeted topic like this :)

Change 575974 merged by jenkins-bot:
[operations/mediawiki-config@master] ContentTranslation: Add URL campaign for WikiGapFinder

https://gerrit.wikimedia.org/r/575974

Mentioned in SAL (#wikimedia-operations) [2020-03-03T12:09:09Z] <kartik@deploy1001> Synchronized wmf-config/InitialiseSettings.php: SWAT: [[gerrit|575974|ContentTranslation: Add URL campaign for WikiGapFinder (T246335)]] (duration: 00m 56s)

Mentioned in SAL (#wikimedia-operations) [2020-03-03T12:10:43Z] <kartik@deploy1001> Synchronized wmf-config/InitialiseSettings.php: SWAT: [[gerrit|575974|ContentTranslation: Add URL campaign for WikiGapFinder (T246335)]], take II (duration: 00m 56s)

Testing

1. Disabled CX from Beta Preferences at: https://hi.wikipedia.org/

2. Went to: https://en.wikipedia.org/wiki/Special:ContentTranslation?campaign=WikiGapFinder&page=Universal+Declaration+of+Human+Rights&from=en&to=hi

3. I was able to access CX dashboard even when CX is disabled in Beta.

So, we can resolve this task as it works as expected.

Thanks @Pginer-WMF and @KartikMistry ! One final question: I suspect the answer is no and that's fine, but is there a way to track specific campaigns like WikiGapFinder easily through CX statistics dashboards?

In T246335#5941638, @Isaac wrote:

Thanks @Pginer-WMF and @KartikMistry ! One final question: I suspect the answer is no and that's fine, but is there a way to track specific campaigns like WikiGapFinder easily through CX statistics dashboards?

No, we have not exposed such data yet. There was this Graphana dashboard, but we were told by Analytics hat Graphana is very unreliable to represent the data. So we are querying the database when needed.

Url campaigns can also create an edit tag when the translation is published (but only if that happens in a single session), which allows for external tracking. If that is helpful we can adjust the configuration to do so.

No, we have not exposed such data yet. There was this Graphana dashboard, but we were told by Analytics hat Graphana is very unreliable to represent the data. So we are querying the database when needed.

Good to know -- we can put that question off then until after the campaign. The editors will be tracked under the broader WikiGap campaign so this would be just to get a sense of how many were using this workflow in particular.

Url campaigns can also create an edit tag when the translation is published (but only if that happens in a single session), which allows for external tracking. If that is helpful we can adjust the configuration to do so.

Personally so long as you can track the data on your end, it's okay if the campaign is not passed as an edit tag. From EventLogging associated with the GapFinder tool, I'll be able to say how many users chose to translate an article and then at some point I'll just ask for support in understanding how many of those users completed the content translation workflow. Thanks!