13.1 Profile and first impression
5/10The profile carried a genuinely strong brand narrative covering heritage, product range, demographic, international reach, commission structure and the active bonus — enough context for a publisher to write authentically. Against that, the contact section was completely empty and no documents existed, so a publisher who read the profile and wanted to act on it had nowhere to go next.
13.2 Documents and welcome pack
1/10Zero documents had been uploaded. No welcome pack, no bestseller guide, no content guidelines, no seasonal calendar, no brand guidelines, no imagery guide. For the editorial and creator partners the programme most needed, this absence is disqualifying — those partners assess how much work a brand will be before they agree to anything.
13.3 Terms and conditions
6/10A relative strength. Terms had been revised three times since launch across eight tabs covering general policy, PPC, transactions, branding, commission, notice periods, publishers and de-duplication. The PPC tab was fully populated with twelve or more policy definitions covering trademark bidding, direct linking, approved code usage, email marketing compliance and incentivised traffic. The gap was enforcement, not drafting: unregistered codes were live in transactions in direct contradiction of the written policy.
13.4 Welcome email and activation
6/10A welcome triggered communication existed and was active, alongside application-accepted, first-click and first-sale triggers. That is a genuinely well-built activation sequence for a programme at this maturity. The gap is that the sequence pointed nowhere — with no documents and no contact details, a newly activated publisher had nothing to act on beyond the profile text.
13.5 Communication and newsletter
5/10Seven triggered communications covered the lifecycle from welcome through dormancy, including declined-transaction and re-activation triggers that many programmes never build. Against that there was no manual newsletter, no promotional announcement, no seasonal briefing and no segmented outreach. Automation was doing all the work, and automation cannot brief an editorial partner on a seasonal campaign.
13.6 Offers, codes and voucher attribution
3/10Seven active offers including exclusive codes, welcome discounts and free shipping showed active management. But multiple overlapping discount offers at the same value created genuine publisher confusion about which code to promote, and seven codes appeared in transaction data that were not registered at all. No voucher attribution framework was configured, so content and editorial partners had no protection from coupon overwrite at the last click — in a programme where voucher partners already took two thirds of revenue.
13.7 Landing page and conversion
6/10A premium brand site with genuine design quality, shipping internationally. The critical finding was the device gap: mobile carried the overwhelming majority of traffic and converted at roughly a quarter of the desktop rate. That is the largest single revenue lever identified anywhere in this audit. Diagnosing it requires analytics funnel data to separate genuine site friction from the low-intent traffic the arbitrage partners were sending.
13.8 Creative and editorial readiness
4/10Sixty-seven creative assets across standard display sizes and text links is good volume for the programme’s age. Editorial readiness was the gap: no media pack, no editorial brief, no content guidelines, no lookbook assets and no curated product selections. The programme was asking editorial partners to do work it had not made possible.
13.9 Product feed and shopping readiness
1/10Zero products. No feed configured, no source connected, no category mapping, no import scheduled. This locked out comparison, shopping and CSS publishers entirely, prevented product-level creative, and made dynamic advertising impossible. One missing configuration removing an entire publisher category is the highest-leverage single fix in the audit.
13.10 Reporting and benchmarking
4/10Headline dashboard metrics and publisher-level analysis were available and functioning. What was absent was any cadence: no scheduled reporting, no custom reports, no benchmarking usage, and no partner-type mix reporting — which meant the single most important structural problem in the programme was not visible on any report anyone looked at.
13.11 Upper-funnel and attribution
3/10Last-click only, with no assist rules and no voucher attribution. Combined with a mix in which voucher and cashback partners took two thirds of revenue, this meant the partners creating demand were structurally guaranteed to lose credit to the partners intercepting it at checkout. The attribution model was actively producing the mix problem, not merely failing to report it.
13.12 Tracking and technical risk
3/10The most technically serious section. The server-to-server click reference was missing, breaking the attribution chain. The customer-acquisition parameter was hard-returning a single value. No Conversion Protection existed. Auto-validation had been set to one hour. Each of these is individually serious; together they meant the programme could neither measure what it was buying nor prevent what it was being charged for.
13.13 Validation and payment trust
2/10The credit limit was exceeded, average payment time ran at nearly double benchmark, and several hundred commissions sat pending validation representing close to a full month of revenue. On top of that, the approval rate meant partners were losing money on nearly half the sales they generated. Payment trust was the programme’s second-largest structural problem after the partner mix itself.
13.14 Fraud monitoring
2/10Seven unregistered voucher codes, device mismatches across three separate publishers, suspicious referrer domains on the third-largest partner, a conversion rate close to zero on enormous click volume, and zero Conversion Protection rules. There was no automated detection and no manual cadence, meaning the fraud indicators found in this audit had been visible in the data for months without anyone looking.
13.15 Compliance and brand protection
5/10Terms were well drafted and regularly revised, with PPC rules fully populated — genuinely above average. Enforcement was the weakness. Voucher code policy was not enforced, publisher promotional methods were not monitored, and several top partners were operating in ways the terms explicitly prohibited without any consequence.
13.16 Seasonal readiness
3/10No seasonal campaign was visible despite the audit falling immediately before a significant seasonal moment for the category, and no evidence of preparation for any major retail peak. In a sector with thirteen distinct activation moments and editorial lead times of six to eight weeks, the absence of a forward calendar means the programme was structurally unable to participate in its own peaks.
13.17 Multi-platform and attribution dependency
3/10The programme ran on a single network across two markets, with no app tracking configured, so any in-app purchases were untracked entirely. Combined with last-click-only attribution and a broken click reference, the programme had no view of any customer journey that crossed a device or a platform — in a category where browsing on mobile and buying later is the dominant pattern.
13.18 Operating rhythm and management maturity
5/10Genuinely mixed, and better than most programmes at this stage. Deliberate setup was visible in the tiered commission groups, the seven triggered communications and three terms revisions in ten weeks. Against that, several hundred pending validations, an exceeded credit limit, unprocessed applications and unmonitored fraud indicators show the daily cadence was absent. Maturity verdict: early-stage active — built with care, then not operated.
13.19 Network recommendation coverage
4/10Creative volume, terms and triggered communications were working. Profile, offers, reporting and compliance were partially addressed. Entirely unaddressed: the product feed, Conversion Protection, voucher attribution, partner discovery and recruitment, and payment status. The pattern across the programme is consistent — what was configured at launch was configured well; nothing that required ongoing operation was operating.