Services

From specification
to implementation.

Bring the technical request. We’ll agree on the scope, put the tracking in place, and verify it before handoff.

01

Ad Tags & Pixels

Conversion, remarketing and audience tags for advertising platforms, networks and DSPs. Implementation through a tag manager or agreed direct-code installation, with the event parameters, values and identifiers the platform requires.

Typical requests

  • Install a new advertising network’s site pixel.
  • Configure conversion and audience events from supplied partner specifications.
  • Map event values and identifiers across a lead or purchase journey.

What you receive

  • Implemented tags and agreed event mapping
  • Validation evidence from the scoped test journeys
  • Configuration and handoff notes
To scope the workPlatform and account, vendor specifications, website technology, relevant journeys, tag-manager access and a developer contact where needed.
Discuss this implementation
02

Floodlight & Campaign Tracking

Floodlight activities with the appropriate counting behavior, conversion values, transaction identifiers and custom variables. Campaign tracking can include impression and click trackers, URL parameters, macros and scoped verification integrations.

Typical requests

  • Implement Floodlight activities for a campaign launch.
  • Map custom variables and transaction values to the right activities.
  • Check a tracker chain between an ad server and media partner.
  • QA supplied third-party verification tags.

What you receive

  • An activity and parameter implementation map
  • Configured tags and campaign tracking
  • Relevant firing, request and destination evidence
  • Documented limitations and handoff notes
To scope the workAdvertiser access, activity definitions, counting and value requirements, placement or vendor documentation, site access and a test environment.
Discuss this implementation
03

GA4 & GTM Implementation

Property and container configuration, event tracking, custom dimensions, data-layer specifications and cross-domain measurement. The measurement plan follows the actual lead-generation or ecommerce journey.

Typical requests

  • Track a successful form submission or booking.
  • Rebuild measurement after a website redesign.
  • Connect a journey that crosses more than one domain.

What you receive

  • An agreed event and parameter plan
  • Property, container and data-layer implementation
  • Documented test journeys and results
  • A practical configuration handoff

Ecommerce, from product to purchase.

Product views, cart changes, checkout and purchase events, with transaction identifiers and values checked across the agreed test flow.

To scope the workProperties and containers, domains, website stack, key business actions, developer dependencies and approved consent requirements.
Discuss this implementation
04

Server-side & Offline Conversions

Supported conversion APIs, server-side tagging, browser and server deduplication, and CRM or offline conversion feeds. We agree on the source, destination and exact integration before implementation.

Typical requests

  • Send a qualified-lead milestone back from a CRM.
  • Deliver transaction signals from a backend.
  • Coordinate browser and server events without counting the same action twice.

What you receive

  • Source-to-destination field mapping
  • The configured integration
  • Field, delivery and deduplication tests
  • Deployment, ownership and operating instructions
To scope the workSource and destination, event definitions, consent requirements, identifiers, hosting ownership, API access and existing integrations.

Ongoing hosting and subscription costs are separate from the implementation fee. Ongoing monitoring is not included in the project.

Discuss this implementation
05

Tracking Audits & Repairs

Investigation of missing or duplicate conversions, unexpected values, broken triggers, tag conflicts and implementation discrepancies. Start with reproducible findings so the next step is clear.

Typical requests

  • Diagnose conversions that stopped after a website change.
  • Review a setup inherited from another agency.
  • Resolve conflicting tags or incorrectly populated values.

What you receive

  • Reproducible findings and prioritized recommendations
  • A defined repair scope
  • Agreed fixes and retesting when included
To scope the workObserved symptoms, affected platforms, expected behavior, dates of changes, account access and available evidence.

An audit can end with findings and a repair scope. A combined project can include the agreed repairs.

Discuss this implementation

The details are part of the scope.

Consent configuration follows your approved requirements, with tag behavior tested accordingly. Verification integrations and any necessary API or script work are agreed within the relevant implementation.

Projects cover technical implementation and handoff. Media buying, campaign optimization, daily ad operations and open-ended support are outside the standard offer.

A few practical questions.

Can you work alongside our agency or developer?

Yes. We agree on technical ownership, developer dependencies and communication before implementation starts.

Can you work behind the scenes for our client?

Agency collaboration and client communication can be agreed during scoping.

Do you manage campaigns after implementation?

The engagement ends after the agreed implementation, verification and handoff. Media buying, bidding, pacing, creative rotation and daily campaign operations are outside the standard scope.

How is the work priced?

Projects are scoped and quoted based on the implementation. The quote reflects the agreed deliverables, dependencies and test scope.

What access will you need?

It depends on the project. Usually this means scoped account permissions, tag specifications, test journeys and a technical contact. Access is arranged after the scope is agreed.

How do you confirm that it works?

We agree on the test scenarios and success criteria in advance. I check behavior, event parameters and the available destination evidence, and document any processing delays or limitations.

What if the website changes later?

Later changes can be quoted as new work. Defect correction follows the agreed project terms.

Can you diagnose the issue before quoting a repair?

Yes. A diagnostic audit can produce findings and a defined repair scope before you commit to implementation.

Have an implementation to get off your list?

Request a project