Cantina campaigns: how we delivered more than 5 million verified views.

The platform and the campaign type

Cantina lets users build AI characters and share conversations with them. Discovery for this category of product happens almost entirely on short-form video, which is why the platform funds clipping campaigns: creators cut platform moments into vertical clips, publish them on TikTok, Instagram Reels and YouTube Shorts, and are paid per 1,000 eligible views under written conditions.

The campaign structure follows the standard Whop Content Rewards model: funded budget, listed rate, content rules, submission links, verification, payout.

Our entry conditions

Reklamatic entered the ecosystem with an operating advantage: an existing production pipeline that publishes daily and an owned network of active accounts. Adapting to a new content universe required three assets built up front: a library of content angles specific to Cantina's characters and conversations, format templates matching the campaign's technical rules, and a submission workflow aligned with Whop's flows.

Setup of this kind typically takes a production team days, not weeks, when the underlying pipeline already exists.

The daily operating loop

The loop ran daily: produce clip variants from approved platform material, publish through suitable accounts, capture evidence including live URLs and publish times, submit into the campaign through automated queueing, and monitor verification status. Automated submission tooling handled queueing, deduplication and status tracking.

Missing a submission window in a funded campaign is a direct revenue loss, so the queue, not a person's memory, owns deadlines.

Reading the rules as a specification

Campaign conditions define which views count: platforms, geographies, content standards, deadlines. We treat the rules document as a production specification.

Every clip is checked against conditions before publishing, because a view that fails eligibility is production cost with no return. Across the Cantina work, rule compliance at the production stage, rather than after rejection, was the single largest efficiency factor.

The delivered result

Reklamatic's Cantina work delivered more than 5 million views inside campaign conditions. The number is a campaign-eligible figure, not raw platform reach; raw reach across published clips is higher, since not every view falls inside a campaign's counting window or geography.

The distinction matters and is worth understanding as a buyer: raw views measure attention, eligible views measure contracted delivery. We report both, and we invoice against the second.

What performed, measurably

Three patterns held across the campaign data. Character-led moments outperformed interface footage: clips opening with an AI character's unexpected reply retained viewers longer than feature explanations.

Variant diversity outperformed repetition: platforms suppress near-duplicates, so ten distinct angles beat thirty re-cuts of one angle. And cadence outperformed bursts: consistent daily publishing produced steadier eligible-view accumulation than sporadic high-volume days.

Verification and settlement

Because submissions ran on Whop rails, every deliverable carried a timestamp, a live URL and a verification status. Rejected submissions were flagged and reviewed; the dominant rejection causes across the market are rule violations and duplicates, both of which are preventable at production time.

Settlement followed the listed campaign rate. No part of the payment process depended on negotiation, which is precisely the property that makes marketplace-based campaigns auditable.

What transfers to a Turkish brand

The identical loop runs for local campaigns: approved source, angle library, variant production, suitable-account publishing, evidence capture, verified delivery, reporting. The difference is authorship of the conditions.

In the Cantina work we operated under rules written by the campaign funder; for Turkish brands, Reklamatic writes the conditions with the brand, which means eligibility geography, content standards and measurement match the brand's actual market instead of being inherited.

Boundaries of this case

This case documents operational capability: production volume, rule compliance, verified delivery above 5 million views, and clean settlement. It does not claim revenue figures for the campaign funder, does not imply endorsement by Cantina, and does not promise identical results for other niches, since rates and audience behavior vary per campaign.

The transferable asset is the machine and its discipline, and both are inspectable through the delivery records.

Key terms used in this case

Eligible view: a view that satisfies the campaign's written counting conditions, including platform, geography and time window. Submission: the act of registering a published post's URL into the campaign for verification.

Verification: the campaign infrastructure's check of a submission against the listed conditions. Settlement: payment of the listed rate against verified eligible views.

Variant: a distinct edit of the same source angle, differing in hook, pacing or caption structure. These definitions matter because every commercial number in this case is denominated in eligible views, not raw platform reach, and confusing the two is the most common measurement error buyers make.

The numbers a buyer should ask any vendor for

Buyers evaluating a similar operation should request five numbers: eligible views delivered inside written conditions, submission acceptance rate, average time from source drop to first published variant, variants produced per approved angle, and the share of deliverables rejected at verification with reasons. These five together describe throughput, compliance and efficiency.

A vendor that can produce them from records is describing an operation; a vendor that cannot is describing an intention. Reklamatic maintains these numbers per campaign and reports them in scope.