PPV Campaign Audit: Find Conversion and Quality Problems

When a PPV campaign underperforms, sending another message is only one possible response, and often not the first one to try. The audience may have already bought similar content. The offer may be unclear. The reported conversion rate may use a different denominator from last week's result. A campaign audit separates those problems before you change the workflow.

This guide focuses on diagnosis after an offer has been sent. It complements our PPV follow-up guide, which covers the next-message workflow. Use only data you are authorized to access and only sending methods permitted for the account.

Define the campaign you are actually comparing

Create a short campaign record: creator, offer, audience rule, price, send window, observation window and any exclusions. If the offer changed halfway through, treat the variants separately. If the same fan received multiple reminders, distinguish unique recipients from total messages.

Record what is missing. Some systems may provide delivered counts but not reliable opens. A missing metric is not zero. Do not invent an open rate or silently substitute sent messages for confirmed delivery.

Keep the original campaign unchanged while you review it. Retrospectively changing labels or grouping weak variants with strong ones can make the report cleaner without making the analysis more useful.

Build a funnel with consistent denominators

State the currency and treatment of refunds, fees and taxes. Gross receipts are not profit. If the platform or tool reports a different definition, label it rather than forcing it into the table above.

Our chatter KPI guide helps align definitions across shifts. Keep a small dictionary of formulas so that a change in staff does not change the meaning of conversion.

Work through a numerical example

Imagine a campaign eligible for 250 fans. It reaches 200 unique recipients. Twenty recipients buy a $15 item once during the observation window. Coverage is 200 divided by 250, or 80%. Unlock rate is 20 divided by 200, or 10%. Gross receipts are $300, which is $1.50 per recipient before deductions.

If a second campaign reaches 50 recipients and has eight buyers, its unlock rate is 16%. That does not automatically make it the better creative. The smaller group may contain more repeat buyers, a different traffic source or fans selected for stronger intent. These are illustrative figures, not expected outcomes.

Compare the audience composition and offer before deciding what caused the difference. With small samples, use the result to choose the next test rather than declaring a permanent winner. A single high-value buyer can dominate revenue in a small campaign.

Inspect the audience before rewriting the copy

Take a sample of recipients and ask why each person was eligible. Were they new, returning, inactive or already a buyer of overlapping content? Was an unresolved complaint excluded? Did a tag still reflect the current situation?

The fan segmentation framework can help make groups actionable. Do not use inferred personal vulnerabilities as targeting criteria. Useful segmentation is based on relevant service context, stated interests and authorized account information.

If the campaign reached the wrong people, changing a headline may only hide the underlying problem. Correct the eligibility rule and test again with the same offer before drawing conclusions about the wording.

Review the offer from the fan's perspective

Read the message without assuming knowledge of the creator's catalog. Can you tell what is included, whether it is a separate purchase and whether any material overlaps with a previous offer? Are delivery expectations accurate? Is the urgency real?

Compare the description with the actual approved item. A persuasive message is not a good message if it creates a promise the team cannot meet. Avoid claims of exclusivity, limited availability or personalization unless they are true for that offer.

Then inspect the surrounding conversation. A well-written offer can still be inappropriate if it arrives immediately after a complaint or ignores a question. Copy quality and contextual relevance are different checks; score them separately.

Audit follow-up and stop conditions

Identify what happened after a reply, purchase or decline. Did the pending reminder stop? Did another chatter send a similar offer? Was the fan asked the same question on the next shift?

Define a simple incident log with the relevant campaign reference, issue, cause and corrective action. Do not paste unnecessary private conversation details into a widely shared report. The review should improve the system while limiting data exposure.

For re-engagement, distinguish a campaign to current subscribers from contact with inactive or expired fans. Our reactivation guide provides a separate workflow. Do not combine unlike audiences just to increase the sample size.

Choose one improvement for the next test

Prioritize the first meaningful failure in the chain. If coverage is incomplete, investigate delivery or eligibility. If recipients ask what the offer contains, improve clarity. If buyers receive repeat offers, repair the stop condition. If records lack ownership, fix the handoff.

Write a test statement before sending: “For this defined audience, we will clarify the bundle description while keeping price, send window and follow-up unchanged.” Choose a fixed review window and record both purchases and quality issues. Do not stop the test at the first favorable result.

Where a proper randomized comparison is not practical, say so. A before-and-after comparison can still reveal useful operational problems, but changes in traffic, seasonality and audience intent may explain part of the outcome.

Use Substy as an operating workspace

Substy's CRM and performance views can help your team organize context and review outcomes. Confirm which measures and filters are available for the connected account. Do not assume the product automatically calculates every formula in this guide.

Scripts and fan memory can support consistent execution, but an audit still needs an owner who checks the offer and reviews exceptions. Keep product configuration and platform permission as separate checks.

Close the audit with a decision

Finish with four lines: what was observed, what remains uncertain, what changes next and who owns the change. Archive the original definitions so that the next review can compare like with like. A useful audit ends with one testable action, not a longer list of messages to send.

Frequently asked questions