Integrate Bannify with your website

1. Open your container and create a new tag.
2. Choose Custom HTML.
3. Paste the Bannify script.
4. Trigger it on all pages or selected pages.
5. Publish the container.

1. Open the template that contains your gtag code.
2. Paste the Bannify script after your analytics snippet.
3. Deploy and verify that both scripts load.

1. Open your theme footer or a trusted custom-code plugin.
2. Paste the Bannify script before the closing body tag.
3. Save and refresh your site.

1. Open Page Settings or Project Settings.
2. Paste the Bannify script in Footer Code.
3. Publish your Webflow project.

1. Open Online Store and edit your theme code.
2. Paste the Bannify script before the closing body tag in theme.liquid.
3. Save and test your storefront.

1. Settings → Custom Code → Body – end
2. Paste your banner’s embed code once in the location shown. Replace the example UUID with your banner UUID.
3. Publish your website, then check the installation on a public page.

1. Code Injection → Footer
2. Paste your banner’s embed code once in the location shown. Replace the example UUID with your banner UUID.
3. Publish your website, then check the installation on a public page.

1. Site Settings → Custom Code
2. Paste your banner’s embed code once in the location shown. Replace the example UUID with your banner UUID.
3. Publish your website, then check the installation on a public page.

1. Additional code snippets → Footer HTML
2. Paste your banner’s embed code once in the location shown. Replace the example UUID with your banner UUID.
3. Publish your website, then check the installation on a public page.

1. Install once using: wp_enqueue_scripts → wp_enqueue_script.
2. Copy the generated script URL from the banner editor. Use the platform’s supported external-script field or embed the complete script tag.
3. Publish or rebuild, clear the platform cache and test on the published page. Check display, dismissal and form delivery.

1. Install once using: *.libraries.yml → type: external → #attached.
2. Copy the generated script URL from the banner editor. Use the platform’s supported external-script field or embed the complete script tag.
3. Publish or rebuild, clear the platform cache and test on the published page. Check display, dismissal and form delivery.

1. Install once using: WebAssetManager → registerAndUseScript.
2. Copy the generated script URL from the banner editor. Use the platform’s supported external-script field or embed the complete script tag.
3. Publish or rebuild, clear the platform cache and test on the published page. Check display, dismissal and form delivery.

1. Install once using: Code Injection → Site Footer.
2. Copy the generated script URL from the banner editor. Use the platform’s supported external-script field or embed the complete script tag.
3. Publish or rebuild, clear the platform cache and test on the published page. Check display, dismissal and form delivery.

1. Install once using: Storefront → Script Manager.
2. Copy the generated script URL from the banner editor. Use the platform’s supported external-script field or embed the complete script tag.
3. Publish or rebuild, clear the platform cache and test on the published page. Check display, dismissal and form delivery.

1. Install once using: Custom theme → default_head_blocks.xml → script src_type="url".
2. Copy the generated script URL from the banner editor. Use the platform’s supported external-script field or embed the complete script tag.
3. Publish or rebuild, clear the platform cache and test on the published page. Check display, dismissal and form delivery.

1. Install once using: FrontController → registerJavascript → server: remote.
2. Copy the generated script URL from the banner editor. Use the platform’s supported external-script field or embed the complete script tag.
3. Publish or rebuild, clear the platform cache and test on the published page. Check display, dismissal and form delivery.

1. Install once using: T123 HTML.
2. Copy the generated script URL from the banner editor. Use the platform’s supported external-script field or embed the complete script tag.
3. Publish or rebuild, clear the platform cache and test on the published page. Check display, dismissal and form delivery.

1. Open your public HTML shell.
2. Paste the Bannify script before the closing body tag.
3. Rebuild or redeploy your app.

1. Open your index.html template.
2. Paste the Bannify script before the closing body tag.
3. Restart or redeploy your app.

1. Open your main Blade layout.
2. Paste the Bannify script before @stack('scripts') or before the closing body tag.
3. Deploy and verify on a public page.

1. app/layout.tsx → next/script
2. Publish your website, then check the installation on a public page.

import Script from "next/script";

<Script src="https://bannify.me/api/{UUID}/generated" strategy="afterInteractive" />

1. Install once using: Shared layout → script is:inline.
2. Copy the generated script URL from the banner editor. Use the platform’s supported external-script field or embed the complete script tag.
3. Publish or rebuild, clear the platform cache and test on the published page. Check display, dismissal and form delivery.

1. Install once using: app.vue → useHead → script.
2. Copy the generated script URL from the banner editor. Use the platform’s supported external-script field or embed the complete script tag.
3. Publish or rebuild, clear the platform cache and test on the published page. Check display, dismissal and form delivery.

1. Install once using: src/app.html → body.
2. Copy the generated script URL from the banner editor. Use the platform’s supported external-script field or embed the complete script tag.
3. Publish or rebuild, clear the platform cache and test on the published page. Check display, dismissal and form delivery.

1. Install once using: src/index.html → body.
2. Copy the generated script URL from the banner editor. Use the platform’s supported external-script field or embed the complete script tag.
3. Publish or rebuild, clear the platform cache and test on the published page. Check display, dismissal and form delivery.

1. Map email and optional contact fields. Use a private-app token with contact-write permission.
2. Choose the matching connector profile and approve the exact HTTPS endpoint for your account. Keep credentials on the server.
3. Send an authorized test and inspect delivery history before using real visitor data.

1. Use an audience endpoint and API key. Explicit consent is required; new members enter pending confirmation.
2. Choose the matching connector profile and approve the exact HTTPS endpoint for your account. Keep credentials on the server.
3. Send an authorized test and inspect delivery history before using real visitor data.

1. Supply the API key, list IDs, confirmation template and redirect URL. Explicit consent starts double opt-in.
2. Choose the matching connector profile and approve the exact HTTPS endpoint for your account. Keep credentials on the server.
3. Send an authorized test and inspect delivery history before using real visitor data.

1. Create a Webhooks by Zapier Catch Hook and enable the Zap. The connector sends JSON.
2. Choose the matching connector profile and approve the exact HTTPS endpoint for your account. Keep credentials on the server.
3. Send an authorized test and inspect delivery history before using real visitor data.

1. Create a Custom webhook and enable the scenario. The connector sends JSON.
2. Choose the matching connector profile and approve the exact HTTPS endpoint for your account. Keep credentials on the server.
3. Send an authorized test and inspect delivery history before using real visitor data.

1. Use an active POST Webhook production URL. The connector sends JSON; optional bearer authentication stays on the server.
2. Choose the matching connector profile and approve the exact HTTPS endpoint for your account. Keep credentials on the server.
3. Send an authorized test and inspect delivery history before using real visitor data.