Marketing Tech Stack Audit: Checklist + 1,000-Site Study

Most marketing tech stack audits start with a spreadsheet of known subscriptions. That is necessary, but it misses tools embedded in forms, checkout flows, chat widgets, analytics containers, ad pixels, and pages owned by agencies or former employees.

We found the size of that blind spot by inspecting 1,000 public websites across four industries. Among 948 normal-status sites, 168 exposed at least one technology signal on a selected secondary page that did not appear on the homepage. A homepage-only review would have missed those signals.

The practical verdict: inspect the customer journey, then reconcile what you find against contracts, administrators, active users, data flows, and business results. The audit should end with a decision register that says what to keep, consolidate, replace, or retire.

If you need the broader architecture before starting, use our B2B tech stack guide. If you want to inspect another company's public footprint, read how to find the tech stacks of companies.

What our marketing tech stack audit found

SoftwareInspect crawled 250 domains in each of four cohorts: DTC/ecommerce, B2B SaaS/software, professional services, and nonprofits/events/education. The crawler checked each homepage and one relevant secondary page when it could find one.

The second page depended on the business model:

• Ecommerce: product, collection, or cart pages
• B2B SaaS: pricing, contact, demo, or signup pages
• Professional services: contact, services, consultation, or booking pages
• Nonprofits, events, and education: donation, event, contact, or newsletter pages

Here is what changed when the audit moved beyond the homepage.

The B2B SaaS cohort had the largest blind spot. Pricing, contact, demo, and signup pages often contained acquisition or conversion tools that were absent from the homepage. Ecommerce showed a similar pattern on product and cart journeys.

That matters during an internal audit. A tag visible only after a form opens or checkout begins can still collect data, affect attribution, create a record, or trigger a campaign. An old script does not become harmless because it is missing from the homepage.

You can inspect the full marketing tools by industry study, open the focused B2B SaaS benchmarks, or download the aggregate CSV.

If the question is how many tools were visible rather than how to audit them, use the separate average martech stack size study. It benchmarks public signal counts by industry without treating them as complete internal inventories.

Why an internal inventory is not enough

Finance, IT, marketing, and the website can each tell a different story about the same stack.

Finance knows which vendors receive payments. IT may know which applications use single sign-on. Marketing operations knows which platforms run campaigns. The website reveals which scripts and forms reach visitors. Individual teams know about free tools, agency accounts, browser extensions, and one-off automations that may not appear in any central system.

None of those sources is complete alone.

A finance export can miss free products and tools bundled into agency retainers. An SSO report can miss shared logins and service accounts. Stakeholder interviews can miss forgotten tags. A public scan cannot see backend integrations, server-side tracking, private applications, contracts, or actual user activity.

The audit needs evidence from all four:

1. Contracts and payments
2. Identity, permissions, and administrators
3. Public pages, tags, forms, and conversion paths
4. The people who operate campaigns and handoffs

This is also why a visible CRM signal should be interpreted carefully. HubSpot forms can appear on a public site while Salesforce remains the internal system of record. Marketo can handle campaign operations without owning sales pipeline data. The public layer gives you a lead to investigate, not a final answer.

Marketing tech stack audit checklist

Use these eight steps to turn scattered evidence into decisions.

1. Define the audit boundary

Write down which systems count before collecting data. A marketing audit will usually include:

• CRM and contact management
• Email and marketing automation
• Forms, landing pages, and conversion tools
• Analytics, tag management, attribution, and consent
• Advertising and audience activation
• Customer data, enrichment, and integrations
• Chat, support, and customer communication
• Content, social, webinar, event, and creative workflow tools

Set the business question too. Reducing spend, fixing attribution, preparing for a CRM migration, tightening permissions, and simplifying campaign work require different evidence.

If the audit prepares the team for software selection, start with the marketing automation requirements checklist or CRM requirements checklist.

2. Build the inventory from four sources

Do not ask one person to remember every tool. Pull records from:

• Accounts payable, cards, expense claims, and procurement
• SSO, password management, browser extensions, and administrator consoles
• CRM integrations, API keys, webhooks, and automation platforms
• Website source, network requests, forms, consent tools, and tag containers

Then interview the people responsible for acquisition, lifecycle marketing, sales operations, support, analytics, and web development. Ask what they use every week, what they work around, and what would break if a tool disappeared tomorrow.

3. Test complete customer journeys

Our crawl found secondary-only signals on 18% of normal-status sites. Apply that lesson to your own audit by testing journeys, not isolated URLs.

For an ecommerce business, check the homepage, product page, cart, checkout entry, email capture, account creation, and order confirmation. For B2B, check the homepage, pricing page, demo form, content download, webinar registration, signup, and thank-you page. For a nonprofit, include donation and event registration.

Use browser developer tools and vendor-specific diagnostics. Google Tag Assistant can show tags and events as you test each page. Test with the relevant consent choices, because some tools should not load until a visitor grants permission.

Record the page, trigger, vendor, data sent, destination, consent state, and owner for each signal. Do not remove a tag merely because its name looks old. Verify whether campaigns, audiences, reports, or conversion imports still depend on it.

4. Give every tool a job and an owner

Each tool needs one primary job and one accountable owner. "Marketing uses it" is not ownership.

The owner should know:

• Which workflow the tool supports
• Which records or events it creates
• Which systems send data to it
• Which systems receive data from it
• Who can change settings or publish updates
• What the renewal date and notice period are
• What happens if it fails

Access is part of the audit. Google's own Tag Manager guidance recommends at least two active administrators and says the account should be managed by someone inside the organization rather than an external agency. Review the official user and permission guidance and apply the same ownership test to every critical platform.

5. Map records and data flows

A useful data-flow map shows the record that moves, the direction it travels, and which system is authoritative. A diagram containing only vendor logos leaves those details out.

For example:

Demo form → marketing automation → CRM contact and company → owner assignment → sales task → opportunity report

For each handoff, record:

• Source system and destination
• Object or event being sent
• Required identifiers
• Sync direction and frequency
• Field ownership
• Error handling
• Consent and retention rules

The NIST Privacy Framework treats inventory and mapping as a foundation for managing privacy risk. That is a useful standard even for a small marketing team. You cannot make a sound retention, consent, or deletion decision if you do not know where customer data travels.

6. Measure usage and workflow coverage

Login counts are helpful but incomplete. A service account may run an important integration without human logins. A platform may have many users while its core automation features remain unused.

Check three kinds of usage:

Connect usage to a result. A tool should improve a defined workflow, data quality, campaign speed, reporting confidence, revenue, or risk control. "The team likes it" is supporting evidence, not a complete business case.

7. Calculate total cost, not subscription price

Annual license cost is only one line. Include implementation, migration, consultants, paid add-ons, seats, contact tiers, message volume, data storage, API usage, training, administration, and the time spent repairing broken integrations.

Contact-based tools need special attention because stored, inactive, or non-marketing records can change the bill. Use our email contact billing guide when email or automation platforms are in scope. For CRM, build a longer view with the three-year CRM total cost model.

8. Classify every tool

End with one of four decisions:

• Keep: Clear owner, required workflow, acceptable cost, healthy integration, and measurable use
• Consolidate: Another owned platform can cover the job without losing an important capability
• Replace: The job remains necessary, but cost, fit, reliability, security, or usability is unacceptable
• Retire: No defensible workflow, owner, dependency, or outcome remains

Add an evidence level to each decision. Confirmed contracts, usage exports, admin access, live workflow tests, and stakeholder validation are stronger than a script name or an employee's memory.

Marketing tech stack audit template

Use the field guide below or download the blank marketing tech stack audit CSV to start the inventory. The file opens in Excel, Google Sheets, Numbers, and most spreadsheet tools.

Use one row per product. Split separate modules into separate rows when they have different contracts, owners, data, or renewal decisions.

Do not bury uncertain rows. Mark them as "verify" and assign an owner. Unknown ownership is itself an audit finding.

Turn audit findings into software decisions

Tool overlap is not automatically waste. Two platforms can share a feature label while serving different operating models. The audit should compare actual workflows before forcing consolidation.

CRM-led or automation-led

A smaller B2B team may choose ActiveCampaign when nurture logic and lifecycle email are central, while HubSpot makes more sense when CRM adoption, sales visibility, service, and reporting need to live together. Use ActiveCampaign vs HubSpot after the audit establishes which system should anchor the process.

One customer platform or enterprise specialists

HubSpot can reduce handoffs for teams that want one CRM-led platform. Marketo fits a different model: mature B2B campaign operations connected to a separate CRM. If both appear in the inventory, do not compare feature counts alone. Map campaign membership, lifecycle stages, lead scoring, routing, attribution, and CRM ownership. Then read HubSpot vs Marketo.

If CRM depth, customization, and enterprise governance are the larger questions, use HubSpot vs Salesforce. If the team mainly needs a focused sales pipeline, Pipedrive vs HubSpot may be the more useful decision.

Ecommerce retention or broad CRM

Ecommerce businesses often need store events, product data, purchase segments, email, and SMS. That can justify Klaviyo even when a broader CRM also exists elsewhere in the company. The ecommerce marketing stack benchmarks show the public pattern, while Klaviyo vs HubSpot explains the operating-model choice.

The audit should not force every tool into one suite. It should reduce unnecessary duplication while preserving the specialist workflows that produce enough value to justify their cost and maintenance.

Actionable takeaways

1. Pull contracts, identity records, integrations, public-page signals, and stakeholder evidence. No single source is complete.
2. Test full conversion paths. Our study found secondary-page-only signals on 168 of 948 normal-status sites.
3. Give every tool a job, owner, backup administrator, renewal date, and measurable outcome.
4. Map records and handoffs before comparing feature lists.
5. Include services, administration, contact tiers, add-ons, and migration risk in total cost.
6. Finish with a named decision and deadline for every row.

Frequently Asked Questions

What is a marketing tech stack audit?

A marketing tech stack audit is a structured review of the software, integrations, data flows, costs, permissions, owners, and workflows used by marketing and connected revenue teams. Its purpose is to decide what to keep, consolidate, replace, or retire.

How often should a martech stack audit be performed?

Run a full audit annually and a lighter review before major renewals, migrations, acquisitions, or operating-model changes. Permissions, failed integrations, public tags, and unowned tools should be reviewed more often when the stack changes frequently.

Which tools should be included in a marketing technology audit?

Include any product that collects customer data, changes a marketing workflow, publishes content, measures activity, activates an audience, creates a CRM record, or influences reporting. Include free tools, agency-managed accounts, service accounts, browser extensions, and backend integrations when they affect the workflow.

Can a website scan identify the complete marketing stack?

No. A public scan can find scripts, network requests, forms, pixels, widgets, and browser-side signals. It cannot prove paid account status, internal usage, backend integrations, server-side tools, contract ownership, or systems of record. Use it as one evidence source in a broader audit.

Why should an audit check more than the homepage?

Different tools load at different stages of the customer journey. In our study, 168 normal-status sites exposed at least one signal on a selected secondary page that was absent from the homepage. Pricing, demo, product, cart, donation, signup, and thank-you pages can reveal important workflow dependencies.

How do you decide whether to consolidate marketing tools?

Consolidate when another owned platform can cover the required workflow, data, permissions, reporting, and service level at a lower total cost and acceptable migration risk. Do not consolidate solely because two products share a feature label.

Next steps

Start with the marketing tools by industry dataset, then create the audit inventory before opening vendor demos. If the audit exposes unclear handoffs, use the B2B tech stack, SaaS marketing stack, and CRM implementation checklist to design the future state.

When the remaining question is platform fit, compare ActiveCampaign vs HubSpot, HubSpot vs Marketo, HubSpot vs Salesforce, and Klaviyo vs HubSpot.