Library · Traffic · How to run this
TUNE offer-count cap hit is not Affise partner-cap hit
TN offer-count % = offers at cap ÷ active offers × 100 on one TUNE offer-count roster.
Pair: Offer-cap hit share on Traffic. Affise twin: partner-cap. Exhaust twin: offer-cap exhaust.
What you type
Offers at cap — TUNE offers currently sitting on a daily or lifetime ceiling.
Active offers — Live TUNE offers in that same roster cut.
A fat TN offer-count % usually means the offer ceiling is starving traffic — raise the ceiling or move traffic; never invent a TN offer-count chip.
What not to do
Do not invent TN offer-count %. Do not paste an Affise partner roster or TUNE offer-day exhaust file into TUNE offer-count fields. Do not fold paused offers into the at-cap count. Do not average every TUNE account when one offer seat owns the ceiling pile.
Related: Traffic, Affise partner-cap, offer-cap exhaust, offer-pause.
Procedure
- Type offers at cap and active offers.
- Read TN offer-count %.
- Raise caps / shift traffic when TN offer-count % is material.
Failure modes
- Inventing TN offer-count %.
- Dumping an Affise partner-cap or TUNE offer-day exhaust file into TUNE offer-count fields.
- Folding TUNE offer-pause into offer-count hits.
Worked example
None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.
Glossary
- TN offer-count %
- Offers at cap ÷ Active offers × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Affise offer-cap hit share?
- Different affiliate grain. [Offer-cap hit share](/manuals/affise-offer-cap-hit-share) is Affise partner ceilings. Here you only count TUNE offers at cap.
- Is this TUNE offer-cap exhaust share?
- Day grain, not offer count. [Offer-cap exhaust share](/manuals/tune-offer-cap-exhaust-share) is cap-exhausted offer-days ÷ offer-days. This page is offers at cap ÷ active offers.
- What TN offer-count % should I invent?
- None. Count offers at cap and active offers from the same TUNE offer-count roster.