How it works
A monitoring loop your team can actually sustain
Eight steps, one system. Each stage feeds the next, and everything leaves a record — from the first scan to the verified fix.
Step 1
Add products & brand context
Add your brands and products with names, aliases, and official domains. This context is what lets scans tell your content apart from everyone else's — the foundation product-aware monitoring runs on.
Step 2
Add partners & their sources
Add the affiliates, influencers, and publishers who promote you, then register every source they publish on: blogs, profiles, review sites, newsletters. Import existing lists via CSV.
Step 3
Assign products to sources
Tell GetAffilert which products each source promotes. Assignments sharpen relevance so findings tie to the right product — and off-topic or competitor content is scored as less relevant instead of cluttering your queue.
Step 4
Scan content
Trigger scans on demand or put sources on a schedule. Each scan captures the content as it appears at that moment, resolves the product/brand context, and preserves the capture as the basis for detection and evidence.
Step 5
Detect risky language
Detection runs your rules against every capture: disclosure presence, prohibited claim patterns, disease-claim language, and custom rules scoped org-wide or to a specific brand or product. The same rules run the same way every time.
Step 6
Review findings
Findings land in a severity-ranked queue with the matched text, product/relevance context, and surrounding excerpt. Your reviewers confirm real problems and dismiss false positives — with notes. Automation proposes; people decide.
Step 7
Escalate to issues & evidence
A confirmed finding becomes a tracked issue with an owner, status, tags, and timeline — and the capture, matched text, rule, and every decision are preserved on it. Repeat detections attach to the existing issue, so history stays coherent.
Step 8
Remediate, verify & report
Send correction requests, schedule re-checks, and let verification scans confirm a fix before an issue closes. Then export audit-ready issue and evidence reports for leadership, clients, or counsel as PDF or JSON.
Questions
Working with the loop
How long does setup take?
A workspace with your first partners, sources, and rules is typically a same-day exercise — faster if you import partners via CSV. The getting-started checklist walks you through it.
Do I need to change how my partners work?
No. GetAffilert monitors what partners publish publicly. Partners interact with your existing process — the difference is your team now sees problems systematically and follows up with specifics.
What happens when a partner fixes content?
You schedule a re-check or run a verification scan. The source is re-examined, and the issue closes only when the problem is no longer detected — with the verification recorded on the issue timeline.
Can detection be wrong?
Any automated detection produces false positives — that's why review is a first-class step. Reviewers dismiss false positives with notes, and those decisions become part of the record too.
Help shape the future of affiliate compliance
GetAffilert is being built for teams that need a more reliable way to monitor partner content, review risk, and preserve evidence.
GetAffilert helps teams detect and organize compliance risk. It does not provide legal advice.