Skip Navigation
Speak to an expert
  • Speak to an expert
  • Expertise
    • Experience
    • Product
    • Technology
    • Approach
    • Engagement
    • Partners
  • Case Studies
  • Podcast
  • Perspective
    • Latest
    • Videos
    • eGuides
    • Blogs
    • News
  • About
    • Journey
    • Clients
    • Expertise
    • Approach
    • Engagement
    • Partners
    • Awards
    • Careers
  • Careers
    • Culture
    • Open Positions
  • Contact
    • Locations
    • Form
Speak to an expert
icon to learn more about our commitment to customers and employees with disabilities.
  • Sitemap
  • Accessibility
  • Privacy
MobileLIVE Site Logo

© 2022 mobileLIVE inc. All Rights Reserved.

MobileLIVE Site Logo

Structured Native App Data Pipeline Through Insights on Data Leaks

structure native app bannerChallenge

Our client was facing issues with hundreds of defects going into production and as we stepped in, we aimed to reduce those defects by taking control of the Omniture data governance process end to end, which not only helped Bell reduce defects but also made their analytics implementation future-proof.

Inconsistent Tagging was a major challenge as Bell owns three native apps (My Bell, Lucky and Virgin), and inconsistent analytics tagging implementation was found between the apps. There was also a lack of documentation; we found that critical documents were not well organized, like technical specifications, BRD (Business Requirements Document) and SDR (Solution Design Reference). These documents act as a backbone for any analytics implementation. Another issue faced was the gap in technical knowledge; as per Analytics standards, QA wasn’t performed completely, due to which defects were rolling into production.

Solution

The solution to closing the gap of inconsistent tagging between apps was by reviewing the Implementation Guide (IG), making sure IG creators are following Bell’s standards and tags are consistent with historical data. This allows us to have easy reporting at the Omniture and BI level. Critical documentation was carried out, like SDR on the confluence page, so that the mapping of variables can be referred to by anyone in the organizations and provide them insights on the description of the variables and what values to expect in the same. This helps make strategizing analytics for projects easier in advance. Since Adobe Analytics is the source of truth for other data sources, an extra layer of validation was added at QA level to check if Omniture has received the data as expected, whereas before it was only validated via Charles logs, and Omniture reports were ignored.

Success

Consistent Tagging was achieved as a result of our solution. We also significantly reduced the number of defects rolling into production, and our solutions for proper documentation and easy reporting ensured that critical documents were organized and easily accessible. The overall analytics delivery process was streamlined.

Like what you see?

This is only a preview of the project. If you’d like to learn more about it, please fill out this form, and one of our experts will be in touch soon.

Thank You!

We have received your request.

A representative from our team will be in touch with you shortly.

Share

LinkedInFacebookTwitterWhatsAppEmail

More Case Studies

A health professional using a tablet device with a technology overlay

Continuous Testing to Increase Accuracy in Healthcare

Top Talent Placement for Program Design & Delivery

A person using a stylus to point to a graph on a digital interface

Achieving Higher Accuracy of Decisioning through Continuous Testing

An illustration of a typical eCommerce journey

eCommerce Excellence through Proactive Test Automation

icon to learn more about our commitment to customers and employees with disabilities.

© 2022 mobileLIVE Inc. All Rights Reserved.

  • icon to learn more about our commitment to customers and employees with disabilities.
  • Sitemap
  • Accessibility
  • Privacy
MobileLIVE Site Logo

© 2022 mobileLIVE Inc. All Rights Reserved.