Skip to content
    Back to Tips & Tricks
    Analytics Engineering53

    Digital Marketing Is Now IT Infrastructure

    Written by Viktor KvantSenior Web AnalystMay 30, 20262 min read

    Behavioural tracking now feeds product, data science and compliance, so it belongs in version control and IT governance, not in an ad account.

    For years, digital marketing meant campaign strategy, ad creative and media buying. Tracking was an afterthought: a JavaScript snippet pasted into a CMS to count clicks.

    That has changed. Server-side tracking, tighter cookie restrictions and modern data pipelines have turned campaign measurement into a far larger system. Campaign telemetry and behavioural analytics now sit naturally under information systems and IT.

    Once behavioural tracking is the source of truth for product development, security and financial forecasting, not just ad optimisation, it requires engineering rigour. Managing it through point-and-click interfaces with no audit trail is an organisational liability.

    Every tracking tag, custom event schema and pipeline configuration should live in a version-controlled repository such as GitHub. When a behavioural event changes, product teams, data engineers and compliance officers can see what changed, who approved it and which downstream systems it affects.

    In practice, this infrastructure is increasingly built on cloud platforms such as Google Cloud Platform (GCP). A typical flow streams raw events from a first-party server-side Google Tag Manager container, running on Cloud Run, directly into BigQuery.

    Raw event tables are deeply nested and verbose, so a transformation layer in dbt or GCP's native Dataform flattens, types and cleans the data before anyone consumes it. The output is not only for marketing dashboards: product managers use it to measure feature engagement, data scientists use it to train propensity models, and compliance teams use it to audit data flows. Version-controlling these models gives the organisation one traceable definition of user behaviour.

    That single definition matters because first-party data easily becomes just another silo. When each department collects its own events for its own dashboards, the result optimises departmental KPIs while no team sees the end-to-end customer journey.

    The shift also turns tracking infrastructure into a governance control. Under GDPR, tracking user behaviour requires strict consent management and data minimisation. If tracking lives in a marketing agency's ad account, the organisation cannot guarantee compliance.

    With tracking housed under IT, configuration history kept in Git and transformations documented in BigQuery, an organisation can demonstrate compliance to regulators with an auditable record.

    Digital marketing infrastructure has outgrown its name. It is now the organisation's main source of user behaviour telemetry.

    Author

    Viktor Kvant

    Senior Web Analyst specialising in data ownership, advanced tracking implementations, and translating data into strategic business value.

    Connect on LinkedIn