Google Cloud Commercial and Professional Services Chile

Incrementa

Marketing Personalization · Real-time Analytics

Incrementa needed to centralize campaign data from multiple advertising channels, cut the time analysts spent producing insight, and turn raw marketing performance data into strategic recommendations that could scale across all clients.

Analyzes 100% of campaigns with Gemini Enterprise Standard
Reduced insight analysis from one week to 3 hours
Supports 100% of clients with personalized AI agents
increased productivity by more than 40%

Reported impact

Business outcome

Incrementa reduced the time required for marketing analysis, increased agency productivity, and turned campaign data into a repeatable recommendation engine that improves client reach and supports all customers.

  • Productivity Improvement
  • Revenue Growth
  • Speed to Market

Solution

Incrementa built a Google Cloud analytics environment that combines Cloud Run, BigQuery, and Gemini Enterprise Standard to convert multi-channel marketing data into faster strategic insight. Cloud Run extracts campaign-performance information from advertising APIs such as Meta, Google Ads, and TikTok, then loads it into BigQuery as a secure single source of truth. Gemini Enterprise Standard sits on top of that warehouse as the natural-language front end, combining the structured campaign data with unstructured context such as brand manuals and client contracts stored in Microsoft OneDrive. This lets Incrementa analyze complete campaign histories in hours instead of a week and return detailed recommendations instead of just raw metrics. The platform turned campaign analysis from a manual reporting function into a scalable advisory engine that now supports all clients and allows the agency to focus more time on growth.

Data flow

Campaign data is pulled from advertising APIs through Cloud Run into BigQuery, where Gemini Enterprise Standard combines the structured warehouse data with unstructured context from OneDrive to generate analysis and recommendations.

Solution architecture

3 components · 3 layers
  1. Ingest
    • Cloud Run Extracts performance data from external advertising APIs and moves it into Incrementa's analytics stack.
  2. Storage
    • BigQuery Acts as the secure single source of truth for multi-channel campaign and client data.
  3. Serving
    • Gemini Enterprise Standard Lets teams query campaign data and supporting context in natural language to produce strategic recommendations.

Architecture clues

  • BigQuery is the secure single source of truth
  • Cloud Run extracts data from advertising APIs
  • Gemini Enterprise Standard combines warehouse data with unstructured context from OneDrive
  • The platform analyzes up to 1 to 2 million data points across campaign histories

Evidence from the source

Data analysis used to take one week with two people dedicated to it. Today, if you generate a good prompt, that takes 3 hours for an update.
The team uses Gemini Enterprise Standard as the intelligent front end.
The technical architecture relies on Cloud Run to extract campaign performance data from external APIs ... and centralizes it in a BigQuery data warehouse.
This strategic shift has led to a more than 30% improvement in client campaign reach.
increased productivity by more than 40%
Transparency Evidence & methodology 100/100 reference value · 82% confidence · 2 sources

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    5 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence82%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability23/25
    11 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency9/10
    2 source references document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Google Cloud

    Incrementa customer story

    First-party
    https://cloud.google.com/customers/incrementa
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
  2. LinkedIn

    Incrementa | LinkedIn

    Independent secondary
    https://www.linkedin.com/company/incrementa-la/

    The profile markup lists "addressLocality":"Santiago"", "addressCountry":"CL"", and "numberOfEmployees":{..."value":33}.

    Source type
    Structured company profile
    Supports
    • Company size

Date evidence

  • First archived Feb 17, 2026 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified Jan 27, 2026 · Google Cloud · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region. Treat these normalized attributes as lower-confidence until a dedicated source is added.

Related

Similar use cases

See all like this