Skip to content
ASIP Mentor guide
Software platforms and applicationsB08Partner brief3 of 14 in SW

Communications Analytics Dashboard

Centre for Wildlife Studies

Website, social, email and payment data sit in eight places and never form one picture.

Skills
  • Third-party APIs and their limits
  • Scheduled jobs
  • Data modelling
  • Dashboard design
Domains
Environment

Who you work with#

The Centre for Wildlife Studies is a Bengaluru research and conservation organisation, working for around four decades on wildlife research, conservation, policy and education. Its programmes include Wild Seve, Wild Shaale, Wild Surakshe and a doctoral programme. Wild Seve alone has filed over 35,000 compensation claims for more than 17,000 families in over 4,000 settlements since 2015.

This problem comes from the Media and Outreach team, and CWS ranked it their first priority.

The situation#

CWS communicates and fundraises through a website, Google Analytics, Google Search Console, Instagram, LinkedIn, YouTube, Flodesk for email, Razorpay for payments, and campaign activity on top. Each holds a piece of the picture. None of them talk to each other.

What is going wrong#

Somebody logs into eight systems every month, copies numbers into a spreadsheet, and builds a report. It takes hours, it happens late, and it produces figures nobody can act on quickly enough to change a campaign that is failing.

Why it is not fixed yet#

The platforms make it hard on purpose. Instagram and LinkedIn restrict their data access, YouTube and GA4 have their own models and quotas, and Flodesk and Razorpay are small enough that their access options are limited. Some of these have no usable interface for automated access at all, which means part of this job is not integration but designing an honest manual step that does not rot.

Skills and Expertise#

  • Branch — CS, IT.
  • Technical skills — Working with third-party interfaces and their limits, scheduled jobs, data modelling, dashboard and chart design, credential handling.
  • Other skills — Defining metrics unambiguously, writing documentation someone else can follow, designing for handover.