Skip to main content
Use Integrations to connect the tools your marketing stack already depends on. Start with what you need the tool to do, not with the list of credentials in Settings. A Jurni integration usually has one of three jobs:
  1. Track the shopper journey — analytics, pixels, attribution.
  2. Show or collect something on the page — reviews, forms, pop-ups.
  3. Connect a workflow or account — Meta Ads, Slack, Figma, affiliate tools.

I want to track campaigns and conversions

Meta Pixel

Load the website pixel used by your Meta advertising setup and verify events on Jurni pages.

Google Analytics 4

Send supported Jurni page activity to the GA4 property your team uses.

Google Tag Manager

Load your team’s GTM container. Tags and triggers inside the container remain a separate setup.

TikTok Pixel

Connect the website pixel used by your TikTok campaigns.

Northbeam

Include Jurni pages in your existing Northbeam browser-pixel setup.

Polar Analytics

Connect the Shopify store used by your Polar measurement setup.

Triple Whale

Enable Triple Pixel for the connected Shopify shop.

Axon / AppLovin

Connect the browser pixel used by your Axon website campaigns.
Also available: Blotout EdgeTag and Shopify Analytics.

Avoid duplicate tracking

Before adding a direct Meta, GA4, or TikTok integration, check whether the same tag already loads through GTM, Custom Scripts, or the Shopify theme. A second installation can produce duplicate PageViews or conversion events rather than more complete tracking. Tracking setup →

I want Meta ad-account data in Jurni

Connecting Meta Ads is different from connecting Meta Pixel.
  • Meta Pixel = website browser tracking.
  • Meta Ads account = lets Jurni access the selected advertising account and related insight workflows.
If you want to review connected ad-account performance in Jurni, start with Connect Meta Ad Accounts, then use Meta ad account insights.

I want to show product reviews

Connect the provider your brand already uses, then place its review widget on the page.

Okendo

Connect the account and show store, product, or supported review-group content.

Yotpo

Connect the App Key and the specific Yotpo widget you want to show.

Junip

Connect the Store Key and place the relevant review section.

Judge.me

Connect the public token and supported external-page review widgets.

Stamped

Connect the Store Hash and public key and map the intended product.

Trustpilot

Connect the business and chosen TrustBox template.

REVIEWS.io

Connect the Store ID and use the product SKU expected by REVIEWS.io.

Bazaarvoice

Connect the production client and product mapping used by your Bazaarvoice setup.
Connecting the account does not automatically add a review section to every page. Account connection and page placement are two separate steps. How review integrations work →

I want to collect email or SMS

Klaviyo

Use Klaviyo for embedded signup forms and the supported Klaviyo pop-up path. The shop-level Company ID/Site ID connects Klaviyo. An embedded form also needs the Form ID for the specific form you want to display.

Postscript

Use Postscript for the supported SMS signup form and pop-up path. The shop connection and page-level form identifier are separate.

Alia

Use Alia for its supported pop-up script connection, then choose whether the provider should run on the intended experience.

I want to connect my design workflow

Use Figma when Jurni should work from your Figma frames. For the marketer workflow behind that process, use Figma → Jurni.

I want Slack notifications or reports

Connect Slack to the intended workspace, then configure scheduled reports separately. Connecting Slack does not automatically create every notification or report.

I use affiliates or creators

Enable the supported affiliate provider and add the creator’s corresponding reference in Jurni. A creator reference is not the same as a discount code, social handle, or Smart Link.

I need a tool that isn’t listed

Use Custom Scripts only when browser-side installation is appropriate and there is no better native connection. For a custom commerce, server-side, or sensitive integration, work with the Jurni team rather than putting secrets into browser scripts.

The integration workflow

1

Confirm what the tool needs to do

Page tracking? Review widget? Form? Ad-account data? Pop-up? A custom downstream event? This determines which Jurni path you need.
2

Get the value from the correct brand account

Follow the provider-specific guide. Jurni may ask for a public ID, public token, URL, OAuth authorization, or an enable switch—not necessarily an API key.
3

Connect it in Jurni

Save the shop-level connection. If the tool appears on the page, complete its separate page/widget configuration too.
4

Test the published page

Open the real destination and perform the action: submit the form, load the review widget, trigger the event, or open the account report.
5

Verify in the third-party tool

A Jurni setting saying “connected” is not enough. Confirm the expected subscriber, widget, event, or account data in the system that owns it.

Shopify Pages need a separate check

A native Shopify Page runs in your Shopify theme environment. Many brands already load Klaviyo, review apps, GTM, pixels, or cart scripts through the theme. Before adding a second installation, test the final /pages/ URL and check what the theme already provides.

Headless and non-Shopify stores

Account-level integrations can still be relevant, but product identifiers, checkout events, and tracking paths can differ from Shopify Online Store. Confirm the full storefront/cart/checkout measurement path with the Jurni team rather than assuming a Shopify-specific mapping applies unchanged.

Need the exact ID or token location?

Use Connection details for a quick directory, or open the provider-specific guide above. For complete campaign workflows instead of setup documentation, browse Jurni Academy.