The New Ad Partner Onboarding Checklist: Adding Demand Without Breaking Consent

Why Onboarding Is Where Consent Breaks

Most consent problems in ad stacks do not come from the banner. They come from the Tuesday afternoon when someone adds a new SSP, a new network tag or a new measurement script, and nobody checks what it does before a visitor has chosen. This checklist is meant to be run every time a partner is added or a major integration changes.

Stage 1: Before You Sign

  1. Ask for a data flow description. What does the partner collect, where is it sent, and which sub-vendors receive it?
  2. Check the vendor’s TCF status. If you rely on IAB TCF, find out whether the vendor is registered and which purposes and legal bases it declares.
  3. Check Google requirements. If the partner serves through Google products, confirm what they need from your consent setup.
  4. Review the contract. Look for data processing terms, the roles of each party, and what happens if a visitor withdraws consent.
  5. Decide whether you need this partner in every region. Some partners are only worth enabling where you can lawfully use them.

Stage 2: Before It Goes Live

  1. Add the vendor to your CMP configuration in the same change that adds the tag, so the banner and the tag stay in step.
  2. Map the vendor to purposes in your cookie or vendor documentation so the banner describes it accurately.
  3. Gate the tag. It must not fire, set identifiers or make requests that transmit personal data until the relevant consent exists, where that is required.
  4. Test in staging with a clean browser profile and record network requests before any interaction.
  5. Test every banner choice: accept all, reject all, partial choices, and withdrawing consent afterwards.

Stage 3: On Release

  1. Release to a small share of traffic first if your setup allows it, and watch the consent signals in network requests.
  2. Verify the consent string or signal reaches the partner in the real ad requests, not only in the test page.
  3. Check regional behaviour. Test a visitor from the EEA, a US state with an opt-out law, and a region with no specific rule, as far as your tooling lets you simulate them.
  4. Confirm mobile apps separately. SDK-based partners read consent through their own mechanisms, so web results do not carry over.

Stage 4: After Release

  1. Compare revenue and fill for the affected traffic against the period before, keeping consent state in view.
  2. Look for tags firing that you did not expect. New partners often load their own sub-partners.
  3. Update your privacy notice and any vendor list shown to visitors.
  4. Record the change with a date, an owner and the test evidence.

Red Flags to Escalate

Any one of these is a reason to pause the rollout until you understand it.

Where FlexyConsent Fits

FlexyConsent is a Google-certified CMP (CMP ID 317) and is certified by IAB Europe and IAB Canada. It supports IAB TCF 2.4, IAB GPP v1.1 with the US National section and 16 US state laws, and Google Consent Mode v2, so the signals your partners look for are available in a standard form. Every plan has the same features, with a free plan available.

Key Takeaways

← Blog Read All →