Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Standard Operating Procedures

Marketing Tool Onboarding SOP

A standard procedure for onboarding a new marketing tool: approval, data and privacy review, access set-up, integration, tagging, training and adoption.
SOPintermediate7 min readUpdated

Owner, trigger and scope

Marketing operations owns the procedure and the stack record. The tool owner is the person in the team that uses the tool and is accountable for its value; they own configuration and adoption. The data protection lead reviews data handling and must approve before personal data reaches the tool. None of the three can skip the others' steps.

The trigger is a decision to adopt a new tool, a trial that will receive real customer data, or a major upgrade: a new module handling different data, a new integration, a change of hosting region or a move to server-side collection. A trial that uses only dummy data is out of scope until it touches real data. For an AI tool, the guide to evaluating AI tools for a marketing team covers the data, training and admin questions that should be answered before that point.

The scope runs from approval to an adoption review some weeks after launch. How a tool is chosen, compared and justified is covered in the guide to choosing and evaluating tools and happens before this SOP starts. The decision record from that selection, kept in a marketing tool evaluation, supplies the tool owner, the known gaps and the success measures this procedure starts from. Decommissioning an old tool is a separate task, though it often runs alongside this one when a tool is being replaced; the tutorial on retiring a marketing tool sets it out, from finding every dependency to a deletion the vendor confirms in writing. When the tool being replaced is the CRM, the tutorial on moving to a new CRM covers the records themselves: field, owner and stage maps, source and consent history carried intact, and a parallel check before the old system is switched off.

Before you start: inputs and access

InputOwnerNotes
Purchase or trial approvalBudget holderSigned contract or written trial approval
Business case and success measuresTool ownerThe KPI the tool is expected to move
Supplier documentationSupplierData processing terms, security information, integration docs
Current stack mapMarketing operationsWhich systems the tool will connect to
Tag governance policyAnalytics ownerRules for adding any script to the site
User listTool ownerWho needs access and at what level

Have admin access to the new tool, access to the tag manager or a developer who does, and the stack diagram. If the business case has no success measures, ask the tool owner to add them now; the adoption review at the end depends on them.

The procedure

  1. Confirm approval

    Check there is a recorded approval to buy or trial the tool, with a budget holder's name, a contract or trial end date and a named tool owner. Add the tool to the stack record as "onboarding", so others know it is coming. If the approval does not name a tool owner, stop: a tool without an owner becomes a tool nobody maintains, and nobody can answer questions about its data later.

  2. Review data and privacy

    With the data protection lead, list what personal data the tool will receive, from which systems, where it will be processed and stored, and for how long. Check the supplier's data processing terms and whether existing consent or another lawful basis covers the use, as the GDPR requires. The privacy and consent guide covers how consent connects to tags. Record the decision; this review is general direction, not legal advice.

  3. Set up access and roles

    Create accounts using company single sign-on where available, never shared logins. Give each user the least access they need, with admin rights limited to the tool owner and marketing operations. Set up a named deputy admin so the account is not lost when one person leaves. Record the roles in the access register and switch on security features the supplier offers, such as two-factor authentication.

  4. Integrate and tag

    Connect the tool to the systems in the stack map, following the patterns in the data flow and integrations guide. If the tool needs a script on the site, add it through the GTM container under the rules in the tag governance guide, firing only with the right consent. Where the tool receives customer profiles, decide whether it reads from your CDP or source system rather than creating another copy.

  5. Test the data flow

    Send test records through every integration and confirm they arrive complete, in the right fields and without duplication. Confirm consent choices are respected: a visitor who declines should not appear. Check the tool's script does not slow pages noticeably or break existing tags. Compare a small sample of real records between systems once live data begins to flow, and fix mapping errors before users rely on them.

  6. Train users

    The tool owner runs a short training session covering the tasks the team will actually do, the naming and data rules that apply in this tool, and who to ask for help. Write a one-page working guide for the team rather than relying on the supplier's general documentation. Record who attended, and do not grant editing rights to anyone who has not been trained.

  7. Review adoption

    Some weeks after launch, the tool owner and marketing operations review whether the tool is being used as planned, whether the success measures are moving, whether data is still flowing cleanly and whether any user access can be removed. Record the outcome: keep, adjust or plan to exit. Update the stack record from "onboarding" to "live" only after this review.

Illustrative example — not a real result

Onboarding a review collection tool

Penhallow Bikes, an invented bicycle retailer, buys a customer review tool. The data protection review finds the tool's default setting sends order emails to a processing region not covered by the supplier terms; the setting is changed before any data flows. The review widget is added through the tag manager, firing only after consent. Testing shows 2 of 25 test orders arriving without product codes because of a field mapping error, which is fixed. Eight weeks later the adoption review finds 340 reviews collected, 6 trained users and 2 accounts that are no longer needed, which are removed.

QA checks

The data protection lead should see this list completed before the tool is announced to the wider team.

Before the tool is marked live, marketing operations confirms:

  • Approval recorded with a budget holder, a contract or trial end date and a tool owner.
  • Data and privacy review completed and signed off by the data protection lead.
  • Access uses individual accounts, least privilege and a deputy admin.
  • Security features offered by the supplier are switched on.
  • Site scripts are deployed through the tag manager and respect consent.
  • Integrations pass test records completely and without duplicates.
  • Page performance and existing tags are unaffected.
  • Users are trained and the working guide is published.
  • Stack record is updated with owner, data held, integrations and renewal date.

Hand-offs and records

Once live, day-to-day ownership passes to the tool owner, who handles user requests, configuration and the relationship with the supplier. Marketing operations keeps ownership of the integrations and the stack record. The data protection lead receives the final record of what data the tool holds, for the organisation's records of processing. The analytics owner is told about any new tag so it is included in future tracking checks.

The records are the approval, the data and privacy review, the access register, the integration notes, the training attendance and the adoption review. Keep them in one place with the stack record. When the contract approaches renewal, the adoption review is the starting point for deciding whether to keep the tool. The tutorial on reviewing a marketing tool before it renews takes the decision from there, working back from the notice date to a recorded renew, renegotiate, replace or retire.

Common mistakes

Nearly all of them come from treating onboarding as a technical set-up rather than a change to how data moves.

  • Real data in an unreviewed trial. A trial with live customer data needs the full privacy review.
  • Shared logins. Nobody can tell who changed what, and access cannot be removed cleanly.
  • Hard-coding the script. Tags added outside the tag manager bypass consent and governance.
  • Another copy of the customer. Each extra profile store creates a new place for data to go stale.
  • Supplier training only. General training does not explain your rules. Write a short working guide.
  • No adoption review. Unused tools keep renewing and keep holding data.
  • Skipping the upgrade review. A new module can send new data. Major upgrades need the full SOP.

Frequently asked questions

When should the data protection lead be involved in a new tool?

Before any personal data reaches the tool, and ideally before the contract is signed. The review covers what data the tool receives, where it is processed, the contract terms with the supplier and whether consent or another lawful basis covers the use. This is general direction rather than legal advice; your data protection lead decides.

Who should be the tool owner?

The person whose team uses the tool most and who is accountable for its value. They own configuration decisions, user access requests and the adoption review, while marketing operations owns how it connects to the rest of the stack.

What counts as a major upgrade that needs the full SOP?

A new module that handles different data, a change of hosting region, a new integration with another system, or a move from a browser tag to a server-side connection. Routine feature releases from the supplier do not need the full procedure, but they should be noted.

Terms used on this page

Where this page is used

Part of these learning paths

Also related

Sources

  1. Regulation (EU) 2016/679 (GDPR) — EUR-Lex

Related