Docs
Completion CTA Goals
Published July 25, 2026
Use completion CTA goal types to classify what each completion action is trying to achieve, then compare outcomes in quiz analytics. Goal types are available for tracked link actions on both the default outcome and conditional outcomes.
What goal type does
- Groups CTA outcomes by intent: You can roll up repeated CTA labels into one reporting key (for example
book_callacross multiple rules). - Preserves rule attribution: Analytics still keep the completion rule index so you can see which rule produced each click.
- Separates click vs lead intent: A CTA can be clicked without being tracked as a lead; goal type still classifies click outcomes.
Where to set it
- Go to Builder > Outcomes.
- Add or edit a completion CTA.
- Set Button action to Open a link.
- Turn on Track click as a lead if you want CTA lead rows in
completion_cta_leads. - Choose Booking, Request call, Purchase, Download, Other, or Unassigned from Goal type. Select Create custom goal... when you need your own reporting key.
Note
Goal type appears in Tracking and behavior after lead tracking is enabled. Lead-form actions are tracked automatically and do not use this link-click goal control.
Custom goal naming pattern
- Use lowercase snake_case keys for consistency.
- Keep keys action-oriented and stable over time.
- Reuse keys across quizzes when you want account-wide comparisons.
- Custom values are normalized to lowercase underscore-separated keys when saved.
Examples:
book_callrequest_demowatch_webinardownload_guidecontact_sales
How analytics use goal type
- Dashboard > Flow insights > Outcomes
- Clicks are grouped by CTA metadata and goal type.
- Lead clicks are counted from
completion_cta_leads. - Rule index remains available for attribution.
- API:
/api/analytics/completion-outcomes- Supports quiz filtering in dashboard context.
- Returns goal-type rollups alongside CTA-level and rule-level groupings.
Default CTA vs conditional CTA behavior
- Default outcome CTAs and conditional-outcome CTAs are tracked the same way.
- If the same goal type is used in both places, outcome totals can be compared as one goal while still splitting by condition and CTA label when needed.
- If different goal types are used, each intent is tracked separately.
Common setups
- Use one goal type across all "Book a call" CTAs even when rules change copy.
- Use separate goal types when two CTAs have different business intent (for example
book_callvswatch_webinar). - Keep
Track click as a leadon only for CTAs you want counted as leads.

