Analytics Implementation vs Incrementality Testing

Both sit under Analytics & Measurement, and clients regularly ask which of the two they actually want. The short answer is below; the rest of this page is how to tell, what each costs, and the cases where a project needs both.

The difference in one line each

Analytics Implementation

Setting up analytics so the numbers can be trusted: tracking plans, tag management, conversion events and consent handling, checked before anyone reports on them.

Incrementality Testing

Controlled tests that show whether a channel or campaign actually caused extra sales, rather than taking credit for sales that would have happened anyway.

Side by side

Choose Analytics Implementation over Incrementality Testing when

• The job is specifically consent mode configuration, which sits under this one
• The job is specifically event & conversion tracking, which sits under this one
• The job is specifically measurement plan development, which sits under this one

Choose Incrementality Testing over Analytics Implementation when

• The difference here is one of emphasis rather than deliverables — controlled tests that show whether a channel or campaign actually caused extra sales, rather than taking credit for sale...

When a project wants both

More often than the question implies — the same job frequently touches both, and one team covers them, so moving between them is a conversation rather than a second supplier. If you are not sure which your files need, that is what the free trial is for.

The process is the same either way: whichever you pick, the work runs through the same stages and is checked against the same bar. Analytics & Measurement sets that out.

Who this is actually for

This page assumes you have a real decision to make about Analytics Implementation compared with Incrementality Testing — not an academic interest in it. That shapes everything below.

Any of those is a fine reason to be here. What follows covers the whole thing: what the work involves, what it costs in the US, how long it takes, what we need from you, and how to tell whether what comes back is any good. Skip to whichever part you need.

When occasional turns into ongoing

There's usually a moment when digital marketing & CRO stops being something you handle between other things and starts being a job. It tends to look like this:

• The work is landing on someone whose actual job is something else, and their actual job is slipping.
• Volume has stopped being occasional and started being weekly.
• Quality varies depending on who happened to be free that day.
• You are turning down opportunities because production cannot keep up.
• The same fix keeps getting made because nobody wrote down how to do it right.
• You are paying for software seats that get used a few days a month.

If two or three of those are true, the question isn't really whether to get help. It's whether to hire, to use a freelancer, or to work with a studio — and there's a section further down that lays out the trade-offs honestly, including the cases where hiring us is the wrong answer.

How the work actually runs

This is what a digital marketing & CRO project looks like from the inside. Knowing the order matters, because almost every schedule that slips slips at the same two or three points.

1. Make the data trustworthy

Before anything else. If analytics and orders disagree, every decision after this point is built on sand.

2. Find where it leaks

Funnel analysis, session recordings, form analytics. Where people actually leave, not where you assume they do.

3. Find out why

Expert review plus watching real people attempt the task. Quantitative data tells you where; only qualitative tells you why.

4. Prioritize

By expected impact against effort. A ranked list of hypotheses, not a wish list of ideas.

5. Design the test properly

Sample size calculated before it runs, minimum detectable effect agreed, duration set in whole business weeks.

6. Run it without peeking

Checking daily and stopping on a high is how noise gets shipped as a result. The stopping rule is set in advance.

7. Decide and document

Win, lose or inconclusive — all three are results. Write down what you learned, including the losses.

8. Roll out and re-measure

Shipping a winner is not the end. Confirm it holds in production, where the traffic mix is different.

Where does Analytics Implementation compared with Incrementality Testing fit? Usually somewhere in the middle of that sequence, and it inherits every decision made before it. That's the argument for settling scope early: a change at stage two is a conversation, and the same change at stage seven is a rebuild.

The numbers, and where they come from

These are published thresholds, not our opinions. Where a standards body or a platform has stated a figure, that figure is here and the body is credited at the bottom of the page. Where nobody has published one, you won't find a number invented to fill the gap.

What it costs in the US

Straight to the money. These are typical US market ranges for digital marketing & CRO work. They are not a quote, because a quote needs your actual files, but they should tell you whether the number you've been given is in the right postcode.

Those are wide ranges, and they're wide for a reason. Here's what moves a job from one end to the other.

What actually drives the price

Traffic volume

The hard constraint. Low traffic means tests take longer or cannot reach significance at all, and no amount of budget changes that.

Number of funnels and markets

Each one is its own research, its own tests and its own sample size problem.

Research depth

Analytics review is days. Moderated user testing with recruitment is weeks and has a participant cost.

Development capacity

Tests have to be built and winners have to be shipped. Without engineering time you get a document.

Media spend under management

Paid work is usually priced as a percentage of spend or as a flat retainer against it.

Measurement complexity

Multiple platforms, offline conversions and consent requirements make attribution genuinely hard and genuinely expensive to get right.

How the money is usually structured

Separately from how much, there's the question of how. Five models cover almost everything in this industry, and the right one depends on how well the job can be described before it starts.

Per unit

A fixed price per image, per minute, per page, per asset. Best when the work is genuinely repeatable and you can describe one unit precisely. It is the easiest model to budget and the easiest to argue about, because everything hinges on whether your idea of one unit matches ours. Settle that on a sample before you settle it on an invoice.

Hourly or day rate

You buy time, and the output is whatever that time produces. Honest when nobody can scope the job yet — a rescue, an unknown archive, an exploratory phase. Ask for a not-to-exceed number anyway. An open hourly arrangement with no ceiling is a budget with no floor.

Fixed project fee

One number for a defined scope, usually with a stated number of revision rounds. The model most clients prefer and the one that punishes a vague brief hardest. The fee is only fixed if the scope is, so expect the scope document to be more specific than feels comfortable. That specificity is what protects you.

Monthly retainer

A set amount of capacity reserved for you every month. Worth it once the work is continuous rather than occasional — a catalog that refreshes, a channel that publishes weekly, a site that keeps changing. Below roughly ten to fifteen hours a month it usually costs more than buying the work as it comes.

Value or outcome based

Pricing tied to a business result rather than to effort. Rare, and rarely as clean as it sounds. It works where the outcome is unambiguous and attributable, and falls apart where it is neither. Treat an outcome-based proposal with the same scrutiny you would give any other claim about attribution.

If you want a real number rather than a range, the fastest route is to send us the actual brief — scope, volume, deadline, and a couple of sample files if you have them. That's usually enough for a fixed price rather than an estimate.

How long it takes

Timelines in this field are mostly predictable, with one exception that catches almost everybody. Here's the usual shape.

One thing worth saying plainly: the most common cause of a late project isn't production. It's waiting — for content, for a decision, for one person to look at something. If you want a project to move quickly, the highest-leverage thing you can do is name one person who can say yes and make sure they're available. That single change is worth more than any amount of chasing.

Rush work is possible and it's genuinely more expensive, because it means real people working real overtime or a job jumping a queue somebody else is in. We'll always tell you what a rush actually costs before you commit to it.

What to send us

Half of the projects that feel slow were slow at the very beginning. A clean handoff is the cheapest speed improvement available to you, and it costs about twenty minutes.

What belongs in the brief

Who it is for

The audience, in one sentence, in your own words. Not a persona document — a sentence.

What it has to do

The action you want someone to take, or the decision you want them to be able to make.

Where it will live

Every placement, at every size. This is the single most common omission, and it is the one that causes reshoots and recrops.

What already exists

Brand guidelines, prior work, the files nobody likes. Especially the files nobody likes, and why.

What is fixed

Colors, typefaces, legal copy, platform requirements, anything that is not up for discussion.

What good looks like

Two or three references, plus one example of something you actively dislike. The dislike is more useful than the likes.

The real deadline

The date something has to be live, not the date you would like to see a draft. Say which one you are giving.

Who signs off

One name. A brief with four approvers and no decider is a brief that will cost you two extra revision rounds.

Two of those deserve emphasis, because they're the ones that cost money when they're missing. Where it will live — every placement, at every size — is the omission that causes reshoots and recrops. And who signs off is the one that quietly adds revision rounds: a project with four approvers and no decider will always cost more than one with a single name on it.

Specific to Analytics Implementation compared with Incrementality Testing

On top of the general brief, this particular job benefits from you having settled the following before anyone starts:

• Choose from the deliverable you need rather than from the service name alone
• Send representative source files before accepting a fixed scope
• Approve a sample before applying the decision across a full batch
• Write down formats, dimensions, naming and acceptance checks

If you've got files ready now, you can send them straight over — they go to private storage rather than to an inbox, and nothing is public. If you'd rather see the standard before committing to anything, try us on a couple of files first. No card, no commitment, and if it's not what you need you've lost nothing but an afternoon.

How to check what comes back

This section is worth reading even if you never hire anybody. Reviewing badly is expensive whoever does the work.

Check it where it will live

Approve a web asset in a browser, a print asset on paper, an audio mix on a phone speaker. Approving a deliverable in the tool that made it is how problems reach the public.

Check the edges, not the middle

The middle is almost always fine. Look at the corners, the smallest size, the longest string, the darkest area, the last ten seconds.

Check one thing at a time

Color, then type, then spacing, then content. A review that tries to see everything at once sees the loudest thing and misses the rest.

Collect feedback before you send it

One consolidated list beats six emails. Contradictions inside your own organization are cheaper to resolve on your side than on ours.

Be specific about what is wrong

"Make it pop" costs a revision round. "The headline is hard to read against the sky, can we darken the area behind it" costs ten minutes.

Say what is right too

Not out of politeness. If you only flag problems, the next round can lose the thing you liked without anyone knowing it mattered.

The bar we hold ourselves to

So you know what you're measuring against, here's what gets checked on our side before anything reaches you. None of it is optional, and none of it is charged as an extra.

• Sample size calculated before a test starts, never watched until it wins
• Tests run for whole business weeks so day-of-week effects cancel out
• Results reconciled against your own order data, not platform-reported conversions alone
• Losses and inconclusive results documented as carefully as wins
• Measurement configured to respect consent rather than to route around it
• No claim of a lift that the sample size could not have detected

Red flags specific to Analytics Implementation compared with Incrementality Testing

If you see any of these in what comes back, say so. They're all fixable, and they're all cheaper to fix now than after it's published.

• Choosing on price before confirming that both quotes include the same deliverables
• Treating related services as interchangeable when they occur at different workflow stages
• Starting production before one person owns approval

You can see how we present finished work — including the before and after — in the portfolio. Anything marked as a sample is our own demonstration piece rather than a client project, and it says so on the item.

Three situations you might recognize

Abstract advice is easy to agree with and hard to use. These are the shapes this kind of problem actually arrives in, and what we'd do about each one.

A test that won and then did not

It was stopped after four days on a 30% lift. Re-run properly with the sample size calculated first, the effect was under 2% and not significant. The first result was a Tuesday.

Analytics and orders that never agreed

The platform reported 40% more conversions than the order system. Duplicate tags, a misconfigured thank-you page and cross-domain tracking that dropped the session. Every optimization decision for a year had been made on the wrong number.

Optimizing a page above a leaking checkout

Months of landing page tests moved almost nothing, because the loss was two steps downstream at an unexplained shipping charge. Research first would have found it in a week.

None of those needed heroics. They needed somebody to look at the right thing early, which is most of what experience buys you in this field.

In house, freelance, studio, or a model?

This is the decision underneath "how much does it cost", and it deserves a straight answer rather than a pitch. There are four ways to get digital marketing & CRO work done, and we're only the right choice for some of them.

Keep it in house

Someone on your payroll does it.

What's good about it: Fastest feedback loop there is, deepest product knowledge, no briefing overhead for small changes.

What's not: You are buying a person, not a job: their vacation, their sick days, their ceiling, and the software. It stops making sense the moment demand is spiky, because you pay for the peak all year.

Hire a freelancer

One specialist, engaged directly.

What's good about it: Cheapest way to buy real expertise, and you get the actual person who does the work.

What's not: One person is one point of failure. No cover, limited throughput, and if they move on mid-project you inherit their files and their conventions.

Use a studio

A team with a process, a review layer and cover.

What's good about it: Handles volume and variety, carries the QC step, and does not disappear when one person is sick.

What's not: More expensive per hour than a freelancer, and you are one client among several. Worth it when consistency across a lot of output matters more than the lowest rate.

Use a model

Generative or automated tooling, with or without a person checking.

What's good about it: Genuinely fast and genuinely cheap on the parts it is good at, and it does not get tired on page four hundred.

What's not: It is confidently wrong in ways that are hard to spot at a glance, and the parts it fails at are the ones a client notices: hands, text, counts, edges, continuity. Nothing should ship without a person having looked at it, which is why our AI work is priced with the review included rather than as a discount.

The short version: if the work is constant and central to what you do, hire. If it's spiky, or it needs a range of skills you can't justify employing, use a studio. If it's one specialist thing and you've found the right specialist, use them. We'd rather tell you that up front than take on a job we're the wrong shape for.

The US rules worth knowing

This isn't legal advice and we're not lawyers. It's a list of the American rules that come up often enough in this kind of work that not knowing about them gets expensive. If any of it applies to you, it's worth twenty minutes with someone who is a lawyer.

CAN-SPAM

US commercial email must carry accurate headers and subject lines, a valid physical postal address, and a working opt-out honored promptly. Penalties are assessed per email, which makes a sloppy list an expensive one.

TCPA and text messaging

The Telephone Consumer Protection Act governs marketing calls and texts in the United States and generally requires prior express written consent for marketing messages. Statutory damages are per message, and TCPA class actions are common.

State privacy law and consent

California, Colorado, Virginia, Connecticut and a growing number of other states give consumers rights over personal data, including opting out of sale or sharing for targeted advertising. Consent configuration is an engineering task with legal consequences, and routing around it is not an option.

And the general commercial stuff

Whatever the discipline, buying professional services in the United States raises the same handful of questions. These are the ones clients ask us most.

Contracts and statements of work

A statement of work that names the deliverables, the number of revision rounds, the ownership terms and the payment schedule is worth the hour it takes to read. Most disputes in this industry are not about quality; they are about two people having understood "done" differently.

Ownership and work made for hire

Under US copyright law, work created by an independent contractor generally belongs to the contractor unless there is a written assignment or it falls into one of the narrow statutory work-made-for-hire categories. That surprises a lot of buyers. Get the assignment in writing; any studio that hesitates is telling you something useful.

Paying an outside supplier

A US business paying a US contractor normally collects a Form W-9 and may need to file a 1099-NEC; paying a non-US supplier usually means a W-8BEN or W-8BEN-E instead. Your accountant will want these before the first invoice, not after the last one.

Sales tax on services

Whether a creative or digital service is taxable varies by state, and several states tax some digital deliverables and not others. It is worth one question to your accountant before a large engagement rather than one letter from a state revenue department after it.

Advertising claims

The Federal Trade Commission holds advertisers responsible for claims made in their marketing, including claims made in images. A retouched product photo that no longer represents the product is an advertising problem before it is a design one, and the liability sits with the advertiser rather than the retoucher.

Accessibility

Title III of the Americans with Disabilities Act has been read by US courts to cover websites in many circumstances, and federal agencies and their contractors are bound by Section 508, which points at WCAG. Accessibility is cheaper designed in than litigated out.

Our own terms are published rather than sent on request: you can read the terms and conditions, the payment terms, the refund policy and the confidentiality and NDA position before you talk to anybody. If something in them doesn't work for you, say so early — most of it is negotiable and all of it is better settled before the work than after it.

Questions to ask anyone quoting for this

Including us. If a supplier gets cagey about any of these, that's the answer to the question you were actually asking.

Who is actually doing the work?

Ask whether it stays with the person you are talking to, moves to a team, or gets subcontracted. None of those is wrong. Not knowing is.

What exactly is a revision?

Ask what counts as a revision versus a new brief, and how many are included. This is the single most common source of a bill you did not expect.

Who owns the output?

Get it in writing, including the working files. "You own the final" and "you own everything" are very different positions, and the second one costs more for a reason.

What happens if it is wrong?

Ask what a redo costs and how fast it happens. A studio with a clear answer has had the conversation before.

Can I see work like mine?

Not a showreel — work in your category, at your volume, with the constraints you have. A beautiful portfolio in another category proves taste, not fit.

How do you handle my files?

Where they are stored, who can reach them, how long they are kept, and what happens at the end. If you are sending anything unreleased, get this in the contract.

What do you need from me?

A supplier who cannot answer this has not thought about your side of the job, and you will discover that at the deadline.

One more, and it's the one people are most embarrassed to ask: what would make you turn this job down? A studio that has never turned work away is a studio that takes everything, and that tells you something about how carefully it's going to be handled.

Working with a studio you'll never meet

Most digital marketing & CRO work now happens between people in different places and often different time zones. That's fine — it's been fine for years — but it rewards a few habits and punishes a few others.

Overlap, not coverage

What matters is not whether a supplier is awake at 2pm Eastern, but whether there is a predictable window when you can both talk. Ask for the window and put it in the calendar.

Batch your feedback

Across a time difference, three rounds of one comment cost three days. One round of twelve comments costs one. This is the single biggest lever you have on turnaround.

Send files once, properly

A clean handoff with originals, a written brief and named files saves more time than any amount of chasing. Half of all "slow" projects were slow at the start.

Agree what "urgent" means

Everyone says urgent. Agree in advance what a rush actually triggers — a different queue, a different price, a different set of hands — so the word keeps its meaning.

Keep one thread

A decision made in a direct message is a decision nobody else on either side can find. One channel, one thread per job.

Our hours overlap the US business day, and we'd rather agree a standing window with you than promise round-the-clock availability nobody can actually sustain. If you want to talk it through before committing to anything, get in touch — there's no pitch deck and nobody will chase you.

The words people will use at you

Every field has vocabulary that gets deployed as a shortcut and lands as a barrier. Here's what the common terms in digital marketing & CRO actually mean, in plain English. You shouldn't need this to buy the work, but it makes the conversation shorter.

Conversion rate

The share of sessions that complete the action you care about. Meaningless until you define both terms.

A/B test

Showing two versions to comparable audiences and measuring the difference.

Statistical significance

How confident you can be the difference is not chance. Not the same as the difference being large enough to matter.

Minimum detectable effect

The smallest improvement a test is capable of finding. Agree it first, or you will run a test that cannot answer the question.

Peeking

Checking a running test repeatedly and stopping when it looks good. The most common way noise becomes a shipped decision.

Attribution

Deciding which touchpoint gets credit for a conversion. Every model is wrong; some are useful.

Incrementality

Whether the marketing caused the sale or just happened to be nearby. The question attribution cannot answer.

Funnel

The sequence of steps from arrival to purchase. Useful as a diagnostic, misleading as a description of how people actually behave.

Heatmap

A visual summary of clicks or scroll depth. Good for generating hypotheses, bad as evidence.

Segment

A subset of users with something in common. A flat conversion rate usually hides two very different groups.

There's a fuller reference library if you want to go deeper on any of these, and everything in it is written the same way — plainly, with sources.

Questions we get on this specific choice

Is one of them cheaper?

They start at the same rate, so the choice is about what the job needs rather than about budget. Complexity moves both.

Which is faster?

Much the same, and volume moves the number far more than the choice between these two does.

Can you tell me which one my files need?

Yes, free. Send two or three real files — that judgment is part of the trial rather than something quoted separately.

Can I switch after we start?

Yes. If the files say the other one is the right answer, we re-quote before doing the work rather than after.

Where to go from here

• Analytics Implementation — what it is, in full, with its own pricing
• Incrementality Testing — the same for the alternative
• Analytics & Measurement pricing — both rates side by side with the US market ranges
• Try it free — a free expert review of one funnel, and we will tell you which of the two your files need
• Get a quote if the scope is already clear
• Every rate we publish, on one page

Related guides and services

Use these paths to continue with the closest practical topic, service, or decision guide.

• How to Get Analytics Implementation Right
• A Practical Guide to Campaign Measurement and Incrementality
• How to Get Game Audio Implementation Right
• Dark Mode Implementation: What Actually Works
• Attribution Modeling vs Incrementality Testing
• Dashboard & Reporting Build vs Incrementality Testing
• Analytics Implementation vs Monthly SEO Reporting