Line 7: |
Line 7: |
| ==Notes and action items== | | ==Notes and action items== |
| ===Digital Transformation Office (DTO) updates=== | | ===Digital Transformation Office (DTO) updates=== |
− | *Mandate letters for Minister of Citizens’ Services and Minister of Sport and Physical Activity have gone out, make sure you update your institutional information if it should point to these. | + | |
− | *Fall Economic Statement Date announced for Tuesday November 21.
| + | * We have reviewed the Audit of Templates and Patterns and will be bringing it back to this table soon to review before officially decommissioning anything. |
− | **We ask for departments to blackout newsroom releases
| + | |
− | *There’s a new Services slack channel: https://gc-web-comms.slack.com/archives/C065G4Q6KU6
| |
− | *Please check for chatbox that you aren’t using live chat, there’s a security risk.
| |
| ===Roundtable=== | | ===Roundtable=== |
− | PCO | + | '''PCO''' |
− | *Please be sure to verify your information and fix your broken links on cross-departmental pages. | + | *Thanks to the teams that supported updating the canada.ca Media contacts page. We're almost wrapped up. Next review in August. |
− | NRCAN
| + | |
− | *We’re introducing new tax credit incentives and Wah-ila-toos updates | + | |
− | '''Discussion - UTMs'''
| + | |
| + | PowerBI meeting - Fiona Currie - AAFC |
| + | |
| + | * People having difficulties with clients wanting to post PowerBI content on website |
| + | * Some accessibility issues |
| + | * AAACT was not at this meeting, we have discussed inviting them at some point |
| + | * Pressure to make PowerBI results more widely available in some departments |
| + | * Part of the push for open data |
| + | * Even though Microsoft says it’s accessible, there are still issues to work around |
| + | * Action items |
| + | ** We want to get ahead of the game, find workable dashboards, with PowerBI or others |
| + | *** Good example, Public Health made some good Covid-19 dashboards |
| + | ** Next meeting April 15 |
| + | ** Sign up for the meeting: [[/events.teams.microsoft.com/event/da6851d0-d919-4d16-9e45-1f23a285d1ab@9da98bb1-1857-4cc3-8751-9a49e35d24cd|https://events.teams.microsoft.com/event/da6851d0-d919-4d16-9e45-1f23a285d1ab@9da98bb1-1857-4cc3-8751-9a49e35d24cd]] |
| + | ** Google docs link: [[/docs.google.com/document/d/1-xBSVmzKraqTheMuJ5NUcJ8F2DkqxB-0ls2Ls1uPVeI/edit#heading%3Dh.alxcm7d7x5d8|https://docs.google.com/document/d/1-xBSVmzKraqTheMuJ5NUcJ8F2DkqxB-0ls2Ls1uPVeI/edit#heading=h.alxcm7d7x5d8]] |
| + | |
| + | Principal Publisher - UTM campaign report - Andrew Lau |
| + | |
| + | * Concept of report is that it should be “plug and play” for everyone |
| + | * Access by: |
| + | ** Logging into your Adobe Analytics and go to templates |
| + | ** If you don’t have AA, go to our GCPEDIA page, and find Workspace Templates, this version is good if you want a quick overview instead of more details |
| + | |
| + | * In AA, you can find data on users broken down by criteria such as |
| + | ** geographic area |
| + | ** mobile vs desktop |
| + | ** performance of landing page |
| + | ** time users are staying on campaign pages |
| + | * We’ve also tried to make report user friendly by defining terms |
| + | * If you use Page Feedback tool, this is incorporated into your Adobe Analytics data |
| + | * You can reach us for Adobe Analytics questions at: [[Mailto:GC.ANALYTIQUE-ANALYTICS.GC@servicecanada.gc.ca|GC.ANALYTIQUE-ANALYTICS.GC@servicecanada.gc.ca]] or submit a service desk ticket ([[/requestform.portal.gc.ca/tickets.html|http://requestform.portal.gc.ca/tickets.html]]) |
| + | |
| + | Questions |
| + | |
| + | Q: Are there still office hours for any questions about Adobe Analytics? |
| + | |
| + | A: Yes, you can arrange to meet with an AA expert for any questions you have. Here’s the link: [[/www.gcpedia.gc.ca/wiki/Adobe Analytics Office Hours|https://www.gcpedia.gc.ca/wiki/Adobe_Analytics_Office_Hours]] |
| + | |
| + | DTO - Lisa Fast - Alerts |
| + | |
| + | * Study goal was to measure alert styling decisions to create clearer guidance |
| + | * Alert use is inconsistent across GOC websites |
| + | * Testing shows that alerts can distract users and overuse also reduces their value |
| + | * Looked at current guidance |
| + | * Behavioral survey for GC Web community, which showed disagreement on how people would use alerts |
| + | * Next steps: |
| + | ** Update alert guidance with example from study |
| + | ** Add keywords for each style |
| + | ** Add ideas for alternatives to alert styles, so that users have more options |
| + | ** Provide guidance so users can be more consistent |
| + | ** Use more A/B testing to understand impact of changes |
| + | ** Tell web advisors to warn their clients overuse of alerts have negative impact on web users |
| + | |
| + | Comments: |
| + | |
| + | DTO: We should be telling comms advisers how long to keep alerts posted. |
| + | |
| + | Q: ESDC: Clients often ask for alerts, they think it will make content “pop”. What about using a well? |
| + | |
| + | A: Lisa F: Bars are a better solution than wells - we removed the well on topic pages for Most requested, and replaced them with a bar, because eye tracking and analytics showed people weren’t looking at the well. If clients want their info to ‘pop’, it should be redesigned rather than added. |
| + | |
| + | Other ideas: Interactive questions are very effective. |
| + | |
| + | Chat summary |
| + | |
| + | * On the topic of out of date browsers: I wonder if there could be a reusable content snippet with language around browser compatibility that could be shown if certain criteria are met? We piloted this for location detection during COVID on the vaccine page, if I remember correctly. |
| + | |
| + | * For a warning to display for only out of date browsers, would require custom scripting. We requested that DTO/PP create a GCWeb component that could be added to identify out of date browsers based on lacking the functions for the components needed to run them. |
| + | |
| + | * Question to ask your clients when they want an alert: When will this be taken down? Alerts should be time sensitive to prevent overuse |
| + | |
| + | * Another option is to use colour for emphasis. [[/wet-boew.github.io/wet-boew-styleguide/design/colour-en.html#basic|https://wet-boew.github.io/wet-boew-styleguide/design/colour-en.html#basic]] |
| | | |
− | Questions for the community
| + | Anything is better than a paragraph of bolded text. |
− | #Do you work closely with your advertising teams on content design for promoted web pages (unpaid and/or paid)? Do you plan and build analytics reporting on these web pages?
| |
− | #Does your organization have any case studies showing how you analyzed success of promoted web pages, such as tracking of conversions of online goals?
| |
− | #What are the opportunities within your team, organization, interdepartmentally to support maturing this space?
| |
− | '''Discussion from the community'''
| |
− | *More training is needed to let non-web teams understand how UTMs work.
| |
| | | |
− | *Sometimes teams are brought in too late after a campaign starts to work on UTMs. | + | * Comment: “If everything is important, nothing is important” |
− | *Some teams find that they have to regularly inform staff from other teams how UTMs work.
| |
− | *Principal Publisher has a new tool for UTMS- to link your Canada.ca urls in social media through Advanced Analytics. Contact: Celine Singhroy at Principal Publisher
| |
− | *Carousels are not very effective, as shown in this research: https://www.gcpedia.gc.ca/wiki/User_testing_the_Canada.ca_product_design/Round_9-2
| |