BRAND MONITORING

Review visible brand drift across websites and partners

Capture approved owned, franchise, reseller, or campaign pages on a controlled schedule. Compare them with reviewed references and send visual differences to brand, marketing, legal, or partner teams without relying on manual spot checks.

Approved pages

Owned and partner web presence

Visual evidence

Before, after, diff

Responsive

Review mobile and desktop

Install:curl -X POST https://api.prod.ss.snapshot-site.com/api/v3/compare

Auth:x-snapshotsiteapi-key: YOUR_API_KEY

Get started for free

Brand compliance review

Good fits

Franchise, reseller, affiliate, and partner pages

Campaign landing pages and localized websites

Logo, color, layout, and approved-message review

Dated visual evidence for partner follow-up

Brand monitoring is a review system, not automatic enforcement

A pixel difference can reveal where a page changed, but brand significance depends on context. Use screenshots to find and document candidate issues, then let the appropriate owner confirm the requirement and response.

Define the approved reference

Store the correct page state, campaign revision, viewport, and date rather than comparing every page with one generic brand board.

Monitor authorized surfaces

Maintain an approved list of owned and partner pages with a documented purpose, cadence, owner, and access policy.

Compare stable regions

Control viewport and timing, then hide unrelated rotating content so alerts focus on the brand elements under review.

Escalate with evidence

Attach source, before, after, diff, capture time, and the relevant guideline to a review item before contacting a partner.

Quick start

Monitor one partner campaign page

Confirm the page is in scope and identify the guideline being checked

Approve a baseline for the campaign revision at selected viewports

Schedule a proportionate comparison during the active campaign

Review the diff and document confirmed issues before escalation

Brand page comparison

Visual Diff API

Compare a partner page with its approved campaign state

Use a page-specific baseline and hide unrelated dynamic inventory or recommendation regions.

curl --request POST \
  --url https://api.prod.ss.snapshot-site.com/api/v3/compare \
  --header 'Content-Type: application/json' \
  --header 'x-snapshotsiteapi-key: YOUR_API_KEY' \
  --data '{
    "before": {
      "imageUrl": "https://assets.example.com/baselines/partner-campaign.png"
    },
    "after": {
      "url": "https://partner.example.com/approved-campaign",
      "width": 1440,
      "fullSize": true,
      "hideCookie": true,
      "hide": ".recommendations,.live-stock"
    },
    "threshold": 0.1
  }'

Visual brand monitoring has a narrow, useful role

Brand teams often review many surfaces they do not publish directly: reseller product pages, franchise sites, affiliate campaigns, regional landing pages, event microsites, and partner announcements. Manual spot checks are difficult to repeat and produce little evidence about what changed between reviews.

Scheduled screenshots create a dated record. Visual comparison highlights the regions that differ from an approved page state. Together they make review more focused and make follow-up easier to document.

They do not automatically determine compliance. A changed color may be an approved regional variant. A new disclosure may be required. A different image may be part of a current campaign. Human reviewers need the correct guideline, agreement, and page context.

Define what “approved” means

Use page-specific references

A generic design-system image is not always a valid pixel baseline for a live partner page. Build references around the actual approved campaign, template, locale, and viewport. Store the reference date and the guideline revision it represents.

If the approved state changes, create a new baseline deliberately. Keep the old state with its review history when it supports an open issue or audit record.

Separate required and variable regions

Identify which page regions are expected to match and which may vary. Logo treatment, required disclosure placement, campaign artwork, and approved offer language may be controlled. Local inventory, recommendations, addresses, or editorial content may be intentionally different.

Hide variable regions when they overwhelm the comparison and do not support the review objective. Document exclusions so no one assumes the monitor covers them.

Maintain locale and viewport variants

Translated copy changes line length and can rearrange components. Mobile layouts may use a different navigation, content order, or sticky action. Approve a separate reference for every intentionally different state rather than treating those differences as exceptions.

Build an authorized monitoring inventory

For each page, record the partner or business unit, URL, owner, monitoring purpose, applicable agreement or policy, campaign period, cadence, viewports, hidden regions, and retention class. Remove expired campaign URLs rather than leaving them in an evergreen job.

Review terms, robots directives, contracts, and internal policy before monitoring external pages. A public page is technically reachable, but the program still needs a legitimate scope and proportionate request rate.

Do not attempt to bypass a login, CAPTCHA, or access control. If a partner portal must be reviewed, use a collaboration and access model approved by both sides rather than improvising credentials inside a screenshot job.

Create an actionable review workflow

Trigger around campaigns and changes

Capture before a campaign begins, shortly after launch, after planned revisions, and when it ends. Add a recurring check during the active period only if the risk and response plan justify it. Evergreen partner pages may need a much lower cadence.

Use the Screenshot Scheduler patterns for external timing, overlap protection, and retries. The schedule should have an owner and an expiry date for temporary campaigns.

Attach the full evidence packet

A review item should include the partner and campaign identifier, source URL, capture time, viewport, approved baseline, current image, diff image, mismatch percentage, hidden-region list, and related guideline. This lets a reviewer confirm the issue without reproducing the job.

Classify the item as pending review, expected variation, confirmed issue, resolved, or baseline update. Do not email a partner directly from an automated mismatch threshold.

Confirm before escalation

Open the source page and capture it again when the issue matters. Temporary asset failures, A/B tests, regional delivery, or consent state can produce a transient difference. Preserve the first image if the intermittent behavior is itself relevant.

Once confirmed, communicate the exact guideline and visible evidence. A diff image is clearer than a vague statement that a page “looks off.”

Brand monitoring use cases

Partner and reseller pages

Check approved product names, current campaign assets, disclosure placement, and visual presentation. Keep catalog or inventory validation in structured systems; use screenshots for the rendered customer-facing state.

Franchise and regional sites

Maintain region-specific references and allow approved local content. Focus comparisons on controlled global components and campaign periods. Route issues to the regional owner before central escalation.

Affiliate and creator campaigns

Capture pages that are explicitly included in the partner program and retain evidence for the campaign period. Social platforms, private profiles, and dynamic feeds require different tools and permissions; this page concerns reachable web pages.

Owned multi-site portfolios

Brand teams operating several domains can monitor navigation, footers, campaign modules, and legal copy across the portfolio. Shared-template pages can use representative coverage; unique flagship pages may justify dedicated baselines.

Security, privacy, and retention

Keep the API key in a backend or workflow secret manager. Restrict target administration and archive access. Avoid capturing pages containing personal information, private partner data, or account-specific content unless the program has an explicit approved need.

Define how long routine captures, confirmed issues, and resolved evidence are retained. Brand review does not require indefinite storage of every unchanged image. Record who reviewed an issue and which guideline was applied.

Measure program quality

Track monitored pages, differences found, reviews completed, confirmed issues, average resolution time, and noisy targets removed or reconfigured. A system that produces many alerts but few confirmed issues needs better baselines or scope, not more pages.

Review the watch list when campaigns end, partnerships change, or guidelines are revised. Monitoring quality comes from current ownership and references.

Brand monitoring checklist

Define the guideline and business purpose for each page.
Confirm monitoring scope, permission, cadence, and retention.
Approve page-, locale-, and viewport-specific references.
Document variable regions excluded from comparison.
Attach complete visual and policy context to review items.
Require human confirmation before escalation.
Update baselines deliberately after approved changes.
Retire expired campaigns and noisy targets.

Brand monitoring FAQ

What can visual brand monitoring check?

It can help reviewers find changes in visible logo treatment, colors, layout, imagery, campaign messaging, disclosures, and responsive presentation on approved pages.

Can an API decide whether a page violates brand guidelines?

Not reliably from pixels alone. Visual comparison identifies changed regions; a reviewer applies the correct guideline and business context.

Which pages should be included?

Use owned pages and partner, franchise, reseller, or affiliate pages that are authorized and relevant to a documented brand or campaign program.

How often should partner pages be captured?

Match cadence to campaign duration, change risk, agreement, and review capacity. Tight intervals are rarely necessary for stable evergreen pages.

How do I handle localized page differences?

Create locale-specific approved references and capture settings. Do not compare a localized page with a baseline that intentionally uses different copy or layout.

Can screenshots replace legal or compliance review?

No. They provide dated visual evidence for review. Legal interpretation, contractual compliance, and remediation decisions remain with authorized people.

How do I reduce false alerts?

Use page-specific baselines, fix the viewport and timing, control consent state, and hide dynamic regions unrelated to the brand requirement.

How should brand monitoring evidence be stored?

Store the source URL, capture time, configuration, approved reference, diff, reviewer status, and related guideline under an access and retention policy.

Related resources

Snapshot Site Home Website Monitoring Visual Diff API Screenshot Scheduler Competitor Monitoring Ecommerce Monitoring PHP SDK Playwright Screenshot Guide API Documentation Pricing

Turn one brand guideline into a reviewable check

Choose a single authorized page and approved reference, prove that the diff is useful, then expand the program by guideline and owner.

Get started for free Read the API docs