ClickFunnels

• ReactionSaaS account with API key and allowed origins including your live site hostname.
• Permission to add custom JavaScript or HTML in ClickFunnels.
• For ReactifySDK (recorded reactions, threads, widgets): template or thread IDs from the Reactify marketplace when you add that layer.

• Funnel or page Settings → Tracking Code (header/footer) or Custom JavaScript areas, depending on your CF version—this is direct script insertion of sdk.js for ReactionSDK overlays.
• Prefer footer placement so DOM and embed targets exist before init runs.
• Keep the first funnel interactions overlay-only (tap, poll, rating, slider, and CTA on reaction-video). Add ReactifySDK (recorded reactions, threads) on later steps when you want depth.

On reaction-video, set the overlays attribute to a comma-separated list. All five standard types are: tap, poll, rating, slider, and CTA. You can enable one or many (e.g. overlays="tap,poll,rating,slider,cta"). Use interaction-type to choose which overlay is primary for the first interaction (typically tap, poll, rating, or slider).

• tap — Binary or multi-choice tap targets; pair with cta-text / options as in your campaign config.
• poll — Poll row; set poll-question (and campaign options when using the dashboard).
• rating — Star-style rating capture on the video.
• slider — Slider / spectrum input for intensity or preference.
• cta — Dedicated CTA overlay; use cta-text (and destination URL from campaign settings when applicable).

Test every type in the SDK playground — toggle overlays and copy the generated embed.

ClickFunnels + overlays: treat footer or custom JavaScript as direct script insertion for sdk.js. Match the paste_snippet / funnel-script adapter model. Use reaction-video with any combination of tap, poll, rating, slider, and CTA before adding reactify.js for recorded reactions or threads.

The production bundle registers both window.reactionSDK and window.Reactify. Use the snippets in the Code column — they enable all five overlay types for integration testing; in production you can omit any you do not need. ReactionSDK here means tap, poll, rating, slider, and CTA—not visitor-recorded clips. Zero-config path (demo / tests): you may omit init and use only the script tag plus reaction-video with overlay attributes—events use the built-in demo key until you call init with your API key.

ReactifySDK (optional): recorded reactions & threads

Load reactify.js when you need recorded video reactions, reactify-video, reactify-thread, or creator uploads—not for overlay-only engagement (those stay ReactionSDK on reaction-video). See the optional expansion snippet in the Code column.

If the host strips inline scripts or enforces strict CSP, load the SDK via Google Tag Manager and fire init on the appropriate trigger.

1. Open the SDK playground with ClickFunnels context.
2. Confirm the network tab shows sdk.js (and reactify.js only if you added the expansion bundle) without CSP errors.
3. Exercise tap, poll, rating, slider, and CTA in the playground or on your published page; confirm events in your ReactionSaaS dashboard.

• CSP blocks script — Use GTM, ask the host for allowlisting, or move init to a tag the host already permits.
• Double init / duplicate events — Ensure the loader appears once per page (not in header and footer).
• 403 on API — Add the exact published origin (including www vs apex) to allowed domains.

Is there a native ClickFunnels app? No — the supported path is script + custom elements, same as other funnel and CMS hosts.

ReactionSDK vs ReactifySDK? ReactionSDK means on-video overlays (tap, poll, rating, slider, and CTA) on the reaction-video element via sdk.js—it is not viewer-recorded video reactions. ReactifySDK (reactify.js) is for recording reaction videos, threads, split-screen, and thread-style UGC. Use overlays first for low-friction signals; add ReactifySDK when you want camera-based participation or social proof clips.