Image credits

The photos on this site come from photographers on Unsplash and are used under the Unsplash License. Every diagram and chart is our own. Here is who took each photo and where we use it.

  • 19 photographers credited
  • Unsplash License
  • Our own diagrams and icons

Who took the photos on this site?

Each photographer's name links to the original photo on Unsplash.

Photos still being confirmed

  • Example ad creatives (skincare serum, headphones, running scenes) on MadLens. Unsplash photos from an earlier build; photographer not recorded.
  • Living room with a streaming app on the TV; case-study card photos on DV360 access (the Artarium painting is also on YouTube & DV360, and the Shoebacca sneakers on Google Ads & Meta Ads). Unsplash photos; photographer not recorded.

Whose logos and badges are shown?

Partner badges

The partner badges belong to Google LLC and to Meta Platforms. Each badge links to the directory that lists AnalyticsLiv.

Client logos

Client logos belong to their owners. We show them only for brands we have worked with, as listed in our case studies and testimonials.

Tool logos

The “Which tools do we work with?” walls on Google Analytics 4 & GTM and Data Analytics, BigQuery & Looker Studio name tools those pages say we use. The marks belong to their owners and are shown as white silhouettes. Sources: Simple Icons (CC0) for Google Analytics, Google Tag Manager, BigQuery, Looker Studio (the Data Studio mark), Google Cloud, Google Ads, Meta, TikTok, LinkedIn, Shopify, Firebase, Mixpanel and dbt; Wikimedia Commons for Amplitude (CC BY-SA 4.0), AppsFlyer (public domain) and MoEngage (CC BY-SA 4.0).

Product screens

Screens of DV360 and our own products are captured from our accounts. Any example figures on them are marked as examples. The product photos on the MadLens page (runner, serum, headphones, watch and coffee) are AnalyticsLiv’s own. The same photos appear in the YouTube ad format pictures on YouTube & DV360.

Spotted a photo without a credit, or one of your photos used wrongly? Email [email protected] and we will fix it.