SaaS Ranking

impact.com

impact.com · Affiliate and partner marketing · checked 2026-09-04

Not enough data: 8 of 12 criteria measured, so no transparency score

We measured 8 of 12 criteria for impact.com on 2026-09-04. We found 6 with a source and did not find 2 at the addresses we checked; 4 we could not measure at all. Below our threshold there is no score and no rank, and that is a statement about our measurement.

Overview

Transparency labelsaas-ranking.com

impact.com

impact.com · Affiliate and partner marketing

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
Not enough data8 of 12 measured, no score

Published commitments4 of 5 found, 4 not measured

Measured behaviour2 of 3 found

Checked 2026-09-04. Every line links the page we found it on. A cross means we found nothing at the addresses we checked, not that the vendor has no such document. A transparency score, not a product rating.

The evidence pack carries every criterion with its source, the addresses we checked, the date and the data snapshot id – the four things a procurement file needs and a screenshot loses. We do not issue badges: a badge is the first step towards a paid placement, and there is none here.

The label is the whole measurement in one object: every criterion with its weight, the band, and the date. Public transparency score, not a product or security rating. We could measure 8 of 12 criteria, which is below our threshold, so there is no rank. That is a statement about our measurement, not about impact.com.

Every line in it links the page we found the result on, or lists the addresses we checked. A cross means we found nothing there, not that impact.com has no such document.

What they state

The exact figures and names we read off the pages linked below, with the sentence they stand in. This is what they publish, not what we verified about their systems.

Gaps, heaviest first

No third-party tracking before consent

weight 2 of 3

No consent-free first load found.

Checked 1 address on 2026-09-04.

Show the 1 address we checked
  1. https://impact.com/ – third-party requests before any interaction: app-ab19.marketo.com, app.leandata.com, app.qualified.com, browser.sentry-cdn.com, cdn.speedcurve.com, cmp.osano.com, d21y75miwcfqoq.cloudfront.net, dev.visualwebsiteoptimizer.com, js.qualified.com, js.sentry-cdn.com, o4507056912203776.ingest.us.sentry.io, pagead2.googlesyndication.com, region1.google-analytics.com, tracking.g2crowd.com, ws.zoominfo.com, www.googletagmanager.com

Is this wrong? Send us the URL

Certifications named

weight 1 of 3

We found this behind a sign-in, so it is not published openly.

Seen at https://trust.impact.com/ · checked 2026-09-04

Show the 6 addresses we checked
  1. https://impact.com/security – reached, no match (HTTP 404)
  2. https://impact.com/trust – reached, no match (HTTP 404)
  3. https://impact.com/trust-center – reached, no match (HTTP 404)
  4. https://impact.com/compliance – reached, no match (HTTP 404)
  5. https://impact.com/legal/security – excluded by robots.txt
  6. https://trust.impact.com/ – found, but behind a sign-in

Is this wrong? Send us the URL

Evidence

The full source lists sit behind these two groups, so that the answer above stays readable.

Published, with a source 6

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

  • Locations named next to the hosting wording European Economic Area, United States.
    Show the 2 exact wordings

    Our servers are located in data centers within the United States and other jurisdictions where we conduct business. Impact utilizes the EEA’s Standard Contractual Clauses for the purposes of transfers...

    Read at https://impact.com/privacy-policy/

    Our servers are located in data centers within the United States and other jurisdictions where we conduct business.

    Read at https://impact.com/privacy-policy/

Source: https://impact.com/privacy-policy/ · checked 2026-09-04

Status page with history

weight 2 of 3

A public status page with incident history.

Source: https://status.impact.com/ · checked 2026-09-04

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://impact.com/ · checked 2026-09-04

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

  • HSTS max-age 31536000 seconds (365 days).
    Show the exact wording

    max-age=31536000; includeSubDomains; preload

    Read at https://impact.com/
  • HSTS options includeSubDomains, preload.
    Show the 2 exact wordings

    max-age=31536000; includeSubDomains; preload

    Read at https://impact.com/

    max-age=31536000; includeSubDomains; preload

    Read at https://impact.com/

Source: https://impact.com/ · checked 2026-09-04

security.txt (RFC 9116)

weight 1 of 3

Served at /.well-known/security.txt.

Source: https://impact.com/.well-known/security.txt · checked 2026-09-04

Named privacy contact

weight 1 of 3

A data protection officer or a dedicated privacy address is named.

Source: https://impact.com/privacy-policy/ · checked 2026-09-04

Not measured by us 4

Data processing agreement

weight 3 of 3

Not measured. The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured.

Show the 8 addresses we checked
  1. https://impact.com/legal/dpa – excluded by robots.txt
  2. https://impact.com/dpa – reached, no match (HTTP 404)
  3. https://impact.com/legal/data-processing-agreement – excluded by robots.txt
  4. https://impact.com/data-processing-agreement – reached, no match (HTTP 404)
  5. https://impact.com/legal/data-processing-addendum – excluded by robots.txt
  6. https://impact.com/legal/gdpr – excluded by robots.txt
  7. https://impact.com/trust/dpa – reached, no match (HTTP 404)
  8. https://impact.com/privacy/dpa – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Subprocessor list

weight 3 of 3

Not measured. The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured.

Show the 7 addresses we checked
  1. https://impact.com/legal/subprocessors – excluded by robots.txt
  2. https://impact.com/subprocessors – reached, no match (HTTP 404)
  3. https://impact.com/sub-processors – reached, no match (HTTP 404)
  4. https://impact.com/legal/sub-processors – excluded by robots.txt
  5. https://impact.com/trust/subprocessors – reached, no match (HTTP 404)
  6. https://impact.com/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://impact.com/legal/subprocessor-list – excluded by robots.txt

Is this wrong? Send us the URL

Notice before subprocessors change

weight 2 of 3

Not measured. The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured.

Show the 8 addresses we checked
  1. https://impact.com/legal/subprocessors – excluded by robots.txt
  2. https://impact.com/subprocessors – reached, no match (HTTP 404)
  3. https://impact.com/sub-processors – reached, no match (HTTP 404)
  4. https://impact.com/legal/dpa – excluded by robots.txt
  5. https://impact.com/dpa – reached, no match (HTTP 404)
  6. https://impact.com/legal/data-processing-agreement – excluded by robots.txt
  7. https://impact.com/trust/subprocessors – reached, no match (HTTP 404)
  8. https://impact.com/legal/sub-processors – excluded by robots.txt

Is this wrong? Send us the URL

Uptime SLA with a figure

weight 1 of 3

Not measured. The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured.

Show the 6 addresses we checked
  1. https://impact.com/legal/sla – excluded by robots.txt
  2. https://impact.com/sla – reached, no match (HTTP 404)
  3. https://impact.com/legal/service-level-agreement – excluded by robots.txt
  4. https://impact.com/trust/sla – reached, no match (HTTP 200)
  5. https://impact.com/uptime – reached, no match (HTTP 404)
  6. https://impact.com/legal/uptime-sla – excluded by robots.txt

Is this wrong? Send us the URL

History

Not enough completed runs yet to draw a line. The next runs fill this in.

Compare

A shortlist holds up to six vendors across categories and lives entirely in the address of its page: share the link, bookmark it, put it in a ticket. Nothing is stored, so we do not know it exists.