Library · Traffic · How to run this
Widget click is not CRM landing
The widget fires a click. The CRM page may never load. Lost share = (widget clicks − CRM landings) ÷ widget clicks × 100.
Pair: Widget-to-CRM drop on Traffic. Content hop sibling: article-to-offer drop. Spend path: CPC vs CRM CPA.
Inputs
Widget clicks — counted presses on the RevContent native unit in the window.
CRM landings — sessions that reach the CRM / checkout URL from that unit.
Lost share = (widget clicks − CRM landings) ÷ widget clicks × 100. When lost share is fat, repair the redirect / lander bridge — leave blank chips alone.
Hard stops
Leave drop % blank until both counts are typed. Do not swap CRM orders for landings. Do not count article pageviews as widget clicks. Slice the worst widget first; skip blended averages that hide the hole.
Related: Traffic, article-to-offer drop, CPC vs CRM CPA, funnel step drop.
Procedure
- Type widget clicks and CRM landings.
- Read drop %.
- Fix the bridge when drop % is material.
Failure modes
- Inventing drop %.
- Mixing CRM orders into landings.
- Treating article pageviews as widget clicks.
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
- Widget-to-CRM drop %
- (Widget clicks − CRM landings) ÷ widget clicks × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this article-to-offer drop?
- Different hop. [Article-to-offer drop](/manuals/outbrain-article-to-offer-drop) counts article clicks vs offer landings. Here the numerator/denominator are widget clicks vs CRM landings.
- Is this CPC vs CRM CPA?
- Dollar path, not hop count. [CPC vs CRM CPA](/manuals/taboola-cpc-vs-crm-cpa) compares platform CPC to CRM CPA. This page only ratios the widget→CRM session hop.
- What drop % should I invent?
- None. Pull widget clicks and CRM landings from one RevContent / CRM window and type them.