Page MenuHomePhabricator

Click-tracking in Acoustic
Closed, ResolvedPublicBUG REPORT

Description

Steps to replicate the issue (include links if applicable):

When a fundraising email is sent in Acoustic we are unable to track what specifically is being clicked within the email. This is extraordinarily important in order to determine what in an email is proving to be more effective.

What happens?:

What should have happened instead?:

Software version (skip for WMF-hosted wikis like Wikipedia):

Other information (browser name/version, screenshots, etc.):

Event Timeline

greg subscribed.

I've marked T188561 as a subtask (needs to happen to allow this task to happen).

Does this mean that this particular task is now moving forward? Is there an ETA?

Hey all. Any update on this click tracking. I had hoped this would be fixed before en6C but now that we are in the throes of it it would be best to get it up as soon as possible.

Updates on the ssl cert work are happening on the subtask (T188561), but tl;dr: Acoustic isn't yet meeting our standards, but @EWilfong_WMF is engaging with the Traffic team on specifics (thanks!).

Noting here that I have opened a support case with Acoustic based on the requirements discussed in the subtask (T188561). I will provide specific responses and updates from Acoustic on that task.

Can we include Brian Sisolak with Trilogy on this ticket?

Yes, he is looped in on the Acoustic support case.

Noting on this parent task that Acoustic has confirmed they can meet the requirements detailed in the subtask. More details in my latest comment: https://phabricator.wikimedia.org/T188561#8433505

That's excellent news. Please keep me apprised on how it's proceeding.

Updating this parent task with next steps in order to implement click tracking for Wikimedia on Acoustic because this is not SSL-specific.

To move forward with click tracking, Acoustic needs us to implement several DNS updates (attached). In order to use a custom click tracking subdomain, Acoustic requires a full custom domain setup. The other subdomains are for for reply, open, and bounce handling. These are currently used but at generic domains (ex. bounce.wikimedia.mkt4477.com for bounce handling), these DNS entries will mask them behind a custom domain. This is Trilogy’s recommended setup for all clients.

Here are more details from Acoustic regarding the setup and benefit of the custom domain: https://help.goacoustic.com/hc/en-us/articles/360042763214-Provision-a-custom-domain-for-email-use

So @EWilfong_WMF is this currently proceeding? Who needs to implement these DNS updates we at WMF or Acoustic? Are there specific people assigned these tasks? Is there an ETA for these to occur?

The DNS updates need to be done by WMF as they are updates for the wikimedia.org domain. The rest of your questions need to be answered by WMF.

@greg or @EWilfong_WMF do you recommend I open a separate ticket for the DNS updates to happen? Sorry just trying to figure out how to get this completed.

@DBu-WMF the sub task T188561 is where the right team (Traffic, in the SRE team in Technology) is engaging (notably Vgutierrez).

Click-tracking for the links.email.wikimedia.org subdomain is available now in Acoustic. Thanks for everyone's help in getting this completed!

AKanji-WMF claimed this task.