> ## Documentation Index > Fetch the complete documentation index at: https://docs.coverbase.com/llms.txt > Use this file to discover all available pages before exploring further. # Marketing compliance > Review the marketing your fintech partners publish under your bank's name before it goes live, watch what is live every day, and hand an examiner the inventory, decisions, captures and rule versions for any program and period. For AI agents: a documentation index is available at [https://docs.coverbase.com/llms.txt](https://docs.coverbase.com/llms.txt). This page is also available in markdown by appending .md to the URL. > [!NOTE] > > Marketing compliance is an optional module. If you do not see **Marketing** in the left navigation, ask your Coverbase account team to turn it on. A sponsor bank is responsible for every landing page, app store listing, email, text message, paid ad and creator post its fintech partners publish about the products the bank sponsors. Marketing compliance puts that work on the records you already keep: the partner is a vendor, each partner product is a **program**, a confirmed problem is a finding, live monitoring runs through Radar, and the partner works through the supplier portal. ## What it does > [card] Pre-publication review > > The partner or your team submits a URL or pasted copy. Coverbase captures it as an immutable version, runs the program's rules, and opens a review whose flags quote the exact passage, cite the rule and suggest a fix. A reviewer confirms or dismisses each flag and decides. > [card] Approval codes > > An approval hands out a code such as `MKT-2026-0418`, valid for 365 days and tied to the version that was captured. The partner keeps it with the asset. Any change needs a new version. > [card] Checked against the web > > When a submission arrives, Coverbase searches the public web for the same copy and lists where it is already live, how closely each page matches and what differs. A page found this way becomes a live asset and is watched from then on. > [card] Daily sweeps of what is live > > Each program names the websites and app listings to watch. A daily sweep crawls them, files what it finds as live assets, and says whether each one matches what was approved, drifted from it, or was never approved. > [card] A shipped rulebook library > > FDIC Part 328 Subpart B, Reg DD, Reg Z, Reg E, Visa and Mastercard brand standards, endorsement and email and SMS rules, and UDAAP. Each rule carries a citation, a severity and a pattern check, an AI check or both. Fork a rulebook to edit it, and test a rule against sample text. > [card] Findings, Radar and the exam packet > > A confirmed flag can raise a finding on the partner. A confirmed flag on a live asset also raises a Radar alert, so the alert queue and residual risk see it. **Reports** exports an exam packet per program and period as a zip. ![The Marketing Overview tab with five tiles reading Waiting for Review, Past SLA, Live Assets with Open Flags, Live and Never Approved and Programs Monitored, the New submission and Sweep now buttons, a Needs a Decision list of open reviews with their flag counts and due dates, a Live Assets Needing Attention list, a Programs card and a Recent Activity card.](https://mintcdn.com/coverbase/ASfsL9ARZRU6mOkd/images/user-guides/marketing-compliance-overview.png?fit=max\&auto=format\&n=ASfsL9ARZRU6mOkd\&q=85\&s=d84eca03292d2632bc09a01fbda945f1) Marketing in the left navigation: what is waiting for a decision, what is live and needs attention, and the programs being monitored. ## Key concepts Six terms, in the order you meet them. | Term | What it is | Where you see it | | - | - | - | | **Program** | One partner product under your sponsorship: the partner vendor, the product types, the card network, the channels, the approved language, the rulebooks that apply, the reviewers, the SLA and the properties to watch. | **Marketing → Programs** | | **Asset** | One piece of marketing: a page, a listing, an email, a post. It belongs to a program and a channel, and it has versions. It is either submitted for review or found by a sweep. | **Reviews** for submitted assets, **Live Assets** for what is live | | **Version** | An immutable capture of the asset: the text, a rendered copy and a screenshot of the live page, with a content hash. A resubmission or a changed live page is a new version. | The **Versions** tab on a review, and **Capture History** on a live asset | | **Review** | The decision on one version: the checks that ran, the flags, the reviewer, the SLA clock, the decision and the approval code. | **Marketing → Reviews** | | **Flag** | One rule's hit on one version: the quoted passage, the citation, the reasoning, a suggested fix, a severity and a confidence. A reviewer confirms or dismisses it. | On the review, and under **Flags on This Capture** on a live asset | | **Rulebook** | A set of rules for one regulation or standard. Library rulebooks ship with Coverbase and are read-only. Your fork is yours to edit, and every save is a new version. | **Marketing → Rulebook** | A confirmed flag can become a **finding** on the partner vendor, with the source **Marketing flag**. From there it is an ordinary finding; see [Findings Manager](https://docs.coverbase.com/products/findings-manager.md). ## Where to go next > [card] [Marketing compliance guide](https://docs.coverbase.com/user-guides/marketing-compliance.md) > > Set up a program, work a review, read the screenshot view, run sweeps, and export the exam packet. > [card] [The marketing rule library](https://docs.coverbase.com/user-guides/marketing-rule-library.md) > > Every shipped rulebook, what each rule checks, pattern and AI checks, forking and versions, and testing a rule. > [card] [The partner portal, for partners](https://docs.coverbase.com/user-guides/marketing-partner-portal.md) > > What a fintech partner sees: submitting, the quick check, the approval code, messages and live issues. Share it with your partners. > [card] [Supplier Radar](https://docs.coverbase.com/products/supplier-radar.md) > > Where a confirmed flag on a live asset shows up as an alert on the partner. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.